mcpbeat

Wp Project Triage

automattic/wp-project-triage

Use when you need a deterministic inspection of a WordPress repository (plugin/theme/block theme/WP core/Gutenberg/full site) including tooling/tests/version hints, and a structured JSON report to guide workflows and guardrails.

6k tokens
context cost
the whole folder, loaded on every use
3
files
ships runnable scripts
1
copies elsewhere
how many repositories repackaged it
209
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/Automattic/agent-skills --skill wp-project-triage

The instruction itself

6 sections, as written by the author

WP Project Triage

When to use

Use this skill to quickly understand what kind of WordPress repo you’re in and what commands/conventions to follow before making changes.

Inputs required

  • Repo root (current working directory).

Procedure

  • Run the detector (prints JSON to stdout):
  • node skills/wp-project-triage/scripts/detect_wp_project.mjs
  • If you need the exact output contract, read:
  • skills/wp-project-triage/references/triage.schema.json
  • Use the report to select workflow guardrails:
  • project kind(s)
  • PHP/Node tooling present
  • tests present
  • version hints and sources
  • If the report is missing signals you need, update the detector rather than guessing.

Verification

  • The JSON should parse and include: project.kind, signals, and tooling.
  • Re-run after changes that affect structure/tooling (adding theme.json, block.json, build config).

Failure modes / debugging

  • If it reports unknown, check whether the repo root is correct.
  • If scanning is slow, add/extend ignore directories in the script.

Repackaged in 1 other repositories

same content, different owner
ComeOnOliver/skillshub open on GitHub →

How to use it

Copy the folder

Take automattic/wp-project-triage from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.