Project Validator
Check a Node project for the setup failures that surface later as confusing runtime errors — malformed package.json, uninstalled node_modules, missing .env, uninitialized git — and scaffold the missing pieces. Use when onboarding to an unfamiliar repo, bootstrapping a new project, or diagnosing "it works on my machine".
Install
/plugin marketplace add tomada1114/tomada-claude-pluginsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add tomada1114/tomada-claude-plugins --skill project-validatorgit clone --depth 1 https://github.com/tomada1114/tomada-claude-plugins.git /tmp/tomada-claude-plugins
mkdir -p ~/.claude/skills
cp -r /tmp/tomada-claude-plugins/tomada-kit/skills/creating-agent-skills/examples/project-validator ~/.claude/skills/project-validatorPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Project Validator
Demonstrates bundling `scripts/`. The checks are deterministic, so they live in code: the source never enters the context window, only the output does.
## Validate an existing project
```bash
python3 ${CLAUDE_SKILL_DIR}/scripts/validate.py
```
Run it from the project root; every path it checks is relative to the working directory. It exits non-zero when a required check fails, and its report already names the fix for each failure — relay those, and run the commands the user asks for. Do not re-derive the checks by reading files yourself.
## Bootstrap a new project
```bash
bash ${CLAUDE_SKILL_DIR}/scripts/setup.sh
```
Idempotent: it initializes git, writes a `.gitignore` and `README.md`, derives `.env.example` from an existing `.env`, and installs dependencies — each step skipped if already satisfied. Safe to re-run on a partially set-up repo.
## Path form
Scripts are invoked through `${CLAUDE_SKILL_DIR}`, which expands to an absolute path before the model sees it. A hardcoded `~/.claude/skills/...` breaks on plugin install and project checkout, and runs the wrong copy when both exist.Details
- Skill name
project-validator- Repository
- tomada1114/tomada-claude-plugins
- Path
tomada-kit/skills/creating-agent-skills/examples/project-validator/SKILL.md- Repo updated
- 12 November 2026
FAQ
What does the Project Validator skill do?
Check a Node project for the setup failures that surface later as confusing runtime errors — malformed package.json, uninstalled node_modules, missing .env, uninitialized git — and scaffold the missing pieces. Use when onboarding to an unfamiliar repo, bootstrapping a new project, or diagnosing "it works on my machine".
How do I install the Project Validator skill?
Claude Code plugin: /plugin marketplace add tomada1114/tomada-claude-plugins. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Project Validator popular?
It lives in tomada1114/tomada-claude-plugins, which has 5 GitHub stars and 0 forks.
Related skills
Auditing Prompt Docs
5tomada1114/tomada-claude-plugins
Audit and fix prompt-bearing documents — SKILL.md, CLAUDE.md, AGENTS.md, agent and command definitions, reference files, whole repositories — against Anthropic's published prompting guidance for current Claude models, proposing edits for approval before writing anything. Also answers how to prompt a specific model: holds the per- model guidance for Claude Fable 5.2, Claude Opus 5.5, Claude Sonnet 5.5, and Claude Haiku 5.5 alongside the cross-model practices. Use when reviewing or slimming an instruction file, when instructions are ignored or fire too often, when migrating a prompt to a newer m
Auditing Repositories
5tomada1114/tomada-claude-plugins
Audit the repository you are in, often a template or an app cut from one, for technical debt and room to improve in four areas: architecture and design patterns; tests; file structure and code quality; and tooling, CI, dependencies and the agent harness. Design a safe, test-first fix for every evidenced finding, and file the findings as GitHub issues that follow the repository's own issue conventions (triaging-issues, issue forms, past issues). A finding inherited from the template is also filed in the template repository. Cheap read-only sub-agents collect the evidence and high-effort analyst
Authoring Goal Prompts
5tomada1114/tomada-claude-plugins
Author a self-contained prompt for Claude Code's /goal command, run unattended in a separate session — a lead-to-staff handoff where this session researches, designs, and decides with full context, and a fresh executor session (Opus 5.5 or Fable 5.2, with none of that context) implements. Drafts a goal with measurable done-criteria, transcript-verifiable checks, scope + anti-cheat constraints, and stop rules; packages design intent, code examples, research findings, checklists, and pre-answered decisions as support files in a per-goal state directory whenever the executor would otherwise re-de
Review PR Codex
5Magnus-Gille/claude-skills
Review a requested pull request or branch diff read-only in this Codex session. Use when the user asks for review-pr-codex or a Codex PR review.
Issues
5Magnus-Gille/claude-skills
Inspect current-repository tickets in Plane (via the tickets MCP tools, else the tix CLI) or prepare a specifically requested routed ticket. Use when the user asks to list, view, filter, search, or create an issue or ticket.
Architecture Diagram
9Lord1Egypt/RA-Skills
Dark-themed SVG architecture/cloud/infra diagrams as HTML.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.