CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

72

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

100%Weight 40%Scale 1-5

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

An exemplary lean skill body: a single executable command, explicit verification, error-recovery guidance, and well-signaled one-level references to real bundle files, with no wasted tokens.

DimensionReasoningScore

Conciseness

The body is lean and well-sectioned with no over-explanation of concepts Claude already knows; every line (procedure, verification, failure modes) earns its place.

5 / 5

Actionability

Provides a fully executable, copy-paste-ready command ("node skills/wp-project-triage/scripts/detect_wp_project.mjs") plus concrete verification criteria and re-run guidance covering the single common case.

5 / 5

Workflow Clarity

Clear numbered procedure with an explicit Verification checkpoint and a Failure modes/debugging section providing error-recovery feedback loops; the read-only nature means no destructive-operation cap applies.

5 / 5

Progressive Disclosure

A concise overview that points one level deep to real, clearly signaled bundle files (references/triage.schema.json, scripts/detect_wp_project.mjs), both verified to exist, with no nesting.

5 / 5

Total

20

/

20

Passed

Description

78%Weight 40%Scale 1-5

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 strong, domain-specific description that answers both what and when with concrete WordPress project kinds. It is held back from the top band only by a slightly circular when-clause and the absence of file-extension trigger terms.

DimensionReasoningScore

Specificity

Names the domain comprehensively ("plugin/theme/block theme/WP core/Gutenberg/full site") plus what is inspected ("tooling/tests/version hints") and the output ("structured JSON report"), but the concrete actions themselves are limited to inspect + report, so it stops short of comprehensive multi-action coverage.

4 / 5

Completeness

Explicitly answers both what (deterministic inspection + structured JSON report) and when ("Use when you need a deterministic inspection of a WordPress repository"), but the when-clause is slightly circular rather than naming independent trigger phrases.

4 / 5

Trigger Term Quality

Strong natural keyword coverage including synonyms ("WordPress"/"WP core") and concrete repo types users would name, but no file extensions or a few common phrasings are absent, so it is not fully comprehensive.

4 / 5

Distinctiveness Conflict Risk

It carves a clear niche (WordPress repo triage) with distinctive enumerated triggers and minimal overlap risk with other skills.

5 / 5

Total

17

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
WordPress/agent-skills
Reviewed

Table of Contents

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.