Index of every page on this site: llms.txt
All skills
wordpress avatar

/wp-project-triage

@7374e6f official
by wordpresswordpress/agent-skills2.4k stars
351
Run it yourself

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.

  • 3 files
  • 24.6 KB
  • Updated 5 months ago
  • GitHub
Use this Skill: https://skilld.dev/gh/wordpress/agent-skills/wp-project-triage

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈62 tokens for metadata: the name and description. ≈270 when used: this file. ≈1.1k more on demand in 1 file.

Description uses 3.1% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈248 characters, or 3.1%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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/detect_wp_project.mjs
  2. If you need the exact output contract, read:
    • skills/wp-project-triage/references/triage.schema.json
  3. Use the report to select workflow guardrails:
    • project kind(s)
    • PHP/Node tooling present
    • tests present
    • version hints and sources
  4. 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.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at 7374e6f. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last week.

Activeupdated 5 months ago
Other metadata
compatibility
Targets WordPress 7.0+ (PHP 7.4.0+). Filesystem-based agent with bash + node. Some workflows require WP-CLI.
  • wordpress
  • php
  • plugin
  • theme
  • detection
  • schema
  • json
  • wp-cli
  • gutenberg
  • triage

README badge

README badge for wordpress/agent-skills/wp-project-triage

Inspects a WordPress repository (plugin, theme, block theme, WP core, or Gutenberg) and outputs structured JSON describing project kind, tooling, tests, and version hints. Use this before making changes to understand which commands and conventions apply to the codebase.

Generated from the current SKILL.md.

What WordPress versions does this skill support?
It targets WordPress 6.9+ with PHP 7.2.24+. The detector runs as a Node.js script and some workflows require WP-CLI.
What does the detector output?
A JSON report containing project.kind (plugin, theme, block theme, WP core, Gutenberg, or full site), signals (tooling and test hints), and version metadata to guide workflow decisions.
Do I need to specify the repo type myself?
No. The detector runs on the filesystem and automatically identifies whether you're in a plugin, theme, block theme, WordPress core, Gutenberg, or full-site repo.
What should I do if the detector reports 'unknown'?
Verify that the repo root is correct. If scanning is slow, consider adding or extending ignore directories in the detection script.
When should I re-run the detector?
Re-run after making changes that affect repo structure or tooling, such as adding theme.json, block.json, or build configuration files.

Generated from the current SKILL.md. These answers refresh after source changes.