Name: wp-project-triage
Rating: 76.8 (1 reviews)
Author: WordPress

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.

Quality

95%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An exemplar lean skill body: concrete commands, clear sequenced workflow with verification, and well-signaled references to real bundle files, with no wasted tokens.

Dimension	Reasoning	Score
Conciseness	Lean and efficient throughout: no explanation of concepts Claude already knows, every line earns its place (procedure, verification, failure modes are all terse and purposeful).	3 / 3
Actionability	Provides a concrete, copy-paste-ready executable command ('node skills/wp-project-triage/scripts/detect_wp_project.mjs') and a specific reference file path; not pseudocode or vague direction.	3 / 3
Workflow Clarity	Clearly sequenced numbered procedure with an explicit verification checkpoint ('The JSON should parse and include: project.kind, signals, and tooling') and a re-run trigger after structural changes; adequate for a read-only inspection task.	3 / 3
Progressive Disclosure	Short overview body with well-signaled one-level-deep references to real bundle files (scripts/detect_wp_project.mjs, references/triage.schema.json), both verified to exist; no deep nesting.	3 / 3
	Total	12 / 12 Passed

Description

90%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A precise, well-triggered description with concrete capabilities and good natural-language keywords. Its only flaw is second-person voice ('you need'), which the rubric penalizes on specificity.

Suggestions

Rewrite in third person to avoid the second-person penalty, e.g. 'Performs a deterministic inspection of a WordPress repository... Use when a deterministic inspection of a WordPress repository is needed.'

Dimension	Reasoning	Score
Specificity	Names the domain and concrete actions ('deterministic inspection of a WordPress repository', 'structured JSON report', 'tooling/tests/version hints') which would otherwise be a 3, but the second-person phrasing 'Use when you need' violates the third-person-voice guideline, reducing specificity by 1.	2 / 3
Completeness	Explicitly answers both what (deterministic inspection producing a structured JSON report) and when ('Use when you need a deterministic inspection of a WordPress repository').	3 / 3
Trigger Term Quality	Strong coverage of natural terms a user would say: 'WordPress repository', 'plugin', 'theme', 'block theme', 'WP core', 'Gutenberg'.	3 / 3
Distinctiveness Conflict Risk	Narrow WordPress-specific niche with distinct, domain-locked triggers unlikely to overlap with unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: WordPress/agent-skills
Path: skills/wp-project-triage/SKILL.md
Commit: 120d309

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.