wordpress/agent-skills · Official

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.

All-time #3494 Trending #3633 First seen Feb 1, 2026
8-week activity · all time api

Installation

$ npx skills add wordpress/agent-skills --skill wp-project-triage

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from wordpress/agent-skills · top by installs.

npx skills add wordpress/agent-skills

Browse all from wordpress/agent-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 2.1K
License LICENSE
Default branch trunk
Open issues 25
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

CompatibilityTargets WordPress 7.0+ (PHP 7.4.0+). Filesystem-based agent with bash + node. Some workflows require WP-CLI.

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,484 B
  • docs SUMMARY.md 253 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 3,942 installs

SKILL.md

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

  1. Run the detector (prints JSON to stdout):

- node skills/wp-project-triage/scripts/detectwpproject.mjs

  1. If you need the exact output contract, read:

- skills/wp-project-triage/references/triage.schema.json

  1. Use the report to select workflow guardrails:

- project kind(s) - PHP/Node tooling present - tests present - version hints and sources

  1. 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.