skilld
All skills
automattic avatar

/wp-project-triage

@95e374f official
by automatticautomattic/agent-skills211 stars
37

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.

Ask your Agent

Use this Skill: https://skilld.dev/gh/automattic/agent-skills/wp-project-triage

This session only. Nothing lands on disk.

SKILL.md

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

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

Third-party checks

1 warning17d4 checks · Risk SAFE
  • Gen Agent Trust Hub17d

    The skill is a diagnostic tool for WordPress repositories that identifies project types, tooling, and configurations by scanning the local filesystem. The primary security risk is indirect prompt injection, where a malicious repository could contain poisoned metadata or script definitions that influence the agent's recommended actions and executed commands.

  • Socket17d

    No alerts

  • Snyk17d

    Risk: LOW · No issues

  • Runlayer7mo

    3/3 files flagged

Provenance

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

Last checked against GitHub 5 months ago.

Dormantupdated 9 months ago

Capability

Other metadata
compatibility
Targets WordPress 6.9+ (PHP 7.2.24+). Filesystem-based agent with bash + node. Some workflows require WP-CLI.

Topics

  • wordpress
  • plugin
  • theme
  • detection
  • php
  • node
  • gutenberg
  • wp-cli
  • schema

README badge

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

What it does

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

Generated from the current SKILL.md.

Frequently asked

What WordPress versions does this skill support?
It targets WordPress 6.9+ and PHP 7.2.24+. The detector runs as a Node script and works on any filesystem-based repository.
What does the detector output?
A structured JSON report containing project.kind (plugin/theme/block theme/WP core/Gutenberg/full site), detected tooling, test presence, and version hints to guide workflow selection.
Do I need WP-CLI installed?
Not always. The detector runs with bash and Node. Some workflows that follow the triage report may require WP-CLI, depending on the project type.
What should I do if the detector reports 'unknown'?
Verify the repo root is correct and points to an actual WordPress project. If signals are missing after that, update the detector script itself rather than guessing.
When should I re-run the detector?
After changes that affect project 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.