Name: wp-project-triage
Author: wordpress

Imported from wordpress/agent-skills (skills/wp-project-triage/SKILL.md) via skills.sh. Install upstream with npx skills add wordpress/agent-skills --skill wp-project-triage. Copyright stays with 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.

# after Install: the listing is in your workspace's routing pool - a plan picks it for its slot curl -s -X POST https://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'

Install wp-project-triage and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "ocm": "1", "id": "wordpress-agent-skills-wp-project-triage", "kind": "skill", "name": "wp-project-triage", "description": "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.", "publisher": "wordpress", "version": "1.0.0", "capabilities": { "domains": [ "coding" ], "tags": [ "skill-md", "skills-sh" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "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." ], "primary": false, "metadata": { "source": { "provider": "skills.sh", "repository": "https://github.com/wordpress/agent-skills", "path": "skills/wp-project-triage/SKILL.md", "ref": "HEAD", "url": "https://www.skills.sh/wordpress/agent-skills/wp-project-triage", "key": "wordpress/agent-skills/skills/wp-project-triage/SKILL.md" }, "compatibility": "Targets WordPress 7.0+ (PHP 7.4.0+). Filesystem-based agent with bash + node. Some workflows require WP-CLI." }, "instructions": "# WP Project Triage\n\n## When to use\n\nUse this skill to quickly understand what kind of WordPress repo you’re in and what commands/conventions to follow before making changes.\n\n## Inputs required\n\n- Repo root (current working directory).\n\n## Procedure\n\n1. Run the detector (prints JSON to stdout):\n - `node skills/wp-project-triage/scripts/detect_wp_project.mjs`\n2. If you need the exact output contract, read:\n - `skills/wp-project-triage/references/triage.schema.json`\n3. Use the report to select workflow guardrails:\n - project kind(s)\n - PHP/Node tooling present\n - tests present\n - ve", "cost": { "context_tokens": 269 } }

wp-project-triage

About