WP Project Triage
94TrustedShips scriptsAutomated inspection of WordPress directory structures to identify standards and tooling.
What it does
Wp Project Triage shifts the assistant from guessing about a directory structure to operating with an accurate map. By scanning the root of a project, the assistant generates a structured JSON report that categorizes the codebase and identifies existing build configurations, testing frameworks, and version requirements.
Installing this skill provides the assistant with a reliable diagnostic tool to determine project type and technical requirements. Instead of browsing individual files manually to find configuration hints, the assistant executes a check that informs how it should interact with your specific WordPress codebase.
When it earns its place
Reach for it when…
Apply this when you inherit a new WordPress codebase and need to identify if it is a block theme, a plugin, or core development. It is essential when you need to confirm which testing suites or build tools are active before performing maintenance or introducing new code.
Look elsewhere when…
Do not use this to debug live site issues, performance bottlenecks, or database queries. This tool is limited to local file system discovery and configuration parsing, meaning it cannot analyze runtime environments or identify errors in production hosting setups.
What to say to use it
You never invoke a skill directly — the assistant picks it up when your request matches what it covers. These are the kinds of things that do that.
- What kind of WordPress project is this directory?
- Detect the build tools and standards in this repo.
- Tell me what testing frameworks are active in this plugin.
- Identify if this is a block theme or a classic theme.
Install it
Install for all your projects
Copy the skill directory into your personal skills folder. Claude picks it up on its own the next time your request matches what it does — there is nothing to enable.
git clone --depth 1 --branch trunk https://github.com/WordPress/agent-skills.git /tmp/agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills/skills/wp-project-triage ~/.claude/skills/wp-project-triageInstall for one project only
Put it in the project's own skills folder instead, so it can be committed and shared with everyone working on that repository.
cp -r /tmp/agent-skills/skills/wp-project-triage .claude/skills/wp-project-triageIf a skill of the same name exists in both places, the personal one wins.
Installing on Claude.ai or through the API instead? The full guide covers every surface.