CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

wp-ability-development

Use when designing, updating, or reviewing the schemas or behavior of a WordPress ability.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/wp-ability-development/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

81%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.

A lean, highly actionable design guide with a complete lifecycle workflow, explicit verification checkpoints, and debugging recovery paths. Its main structural limitation is that all depth lives inline in SKILL.md with only unverifiable cross-skill references, which is acceptable at this size but leaves no room to grow.

DimensionReasoningScore

Conciseness

Dense, opinionated guidance with one-line examples ("take a product ID and quantity and calculate the price") that assumes competence — no re-explanation of JSON Schema, WP_Error, or hooks. A few sentences could be tightened ("The information available to each caller helps you choose the inputs the ability should support"), so it sits at efficient-with-minor-trimming rather than every-token-earns-its-place.

4 / 5

Actionability

Concrete, executable patterns throughout: `additionalProperties: false`, a `selector` object using `oneOf`, `content.raw`/`content.rendered`, `{object}-{action}` naming, `meta.annotations` values, and a fully specified `errors` array shape. Per the instruction-only scoring note absent code is not penalized, but a few rules remain abstract ("Choose a stable result type and structure"), keeping it below fully-executable.

4 / 5

Workflow Clarity

The procedure flows from caller analysis through input design, result shape, errors, CRUD consistency, annotations, and permissions, backed by an explicit Verification section (zero/one/many matches, invalid input, denied access, partial-update field checks) and a Failure modes section with symptom-to-diagnosis recovery paths. This matches the anchor with explicit validation steps and error-recovery feedback loops.

5 / 5

Progressive Disclosure

Well-organized sections with clearly signaled, purpose-stated outbound references ("For registration, exposure, and client usage, see [wp-abilities-api]..."), but those references point outside the bundle and could not be verified to resolve, and the ~100-line body exceeds the under-50-line simple-skill exception for scoring structure alone.

4 / 5

Total

17

/

20

Passed

Description

66%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 concise, distinctive trigger-only description with a strong explicit "when" clause, but it never states what the skill does when invoked, leaving the value proposition implied. Verb coverage is good though free of synonyms.

Suggestions

State the 'what' alongside the 'when': e.g., "Provides conventions for ability inputs, results, errors, permissions, and annotations. Use when designing, updating, or reviewing the schemas or behavior of a WordPress ability."

Add one or two natural synonyms for discoverability, such as "MCP tool" or "tool schema", since callers may not use the term "ability" verbatim.

Consider naming the key deliverables (input/output schemas, error codes, CRUD naming, annotations) so the description previews the skill's concrete scope.

DimensionReasoningScore

Specificity

Names the domain ("WordPress ability") and three specific actions ("designing, updating, or reviewing") on concrete targets ("the schemas or behavior"), matching the several-specific-actions anchor rather than the comprehensive 5, which would enumerate sub-capabilities like input design, error modeling, and annotations.

4 / 5

Completeness

Has an explicit and concrete "Use when" clause, but the "what" — what the skill actually provides (design conventions and guidance) — is never stated and only implied by the trigger clause. This mirrors anchor 3 (one component clear, the other only implied) rather than 2, whose example lacks this concreteness.

3 / 5

Trigger Term Quality

Includes natural trigger terms "WordPress ability", "schemas", "designing", "updating", "reviewing" with good verb coverage. Not 5 because it lacks synonyms or variations users might say (e.g., "tool", "endpoint") and "ability" is ecosystem jargon.

4 / 5

Distinctiveness Conflict Risk

"WordPress ability" is a distinct niche with clear triggers and minimal conflict risk; the only overlap is with closely related sibling skills (registration/API exposure, verification), matching the mostly-distinct anchor 4.

4 / 5

Total

15

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 2 suspicious

Warning

Total

15

/

16

Passed

Repository

WordPress/agent-skills

Path

skills/wp-ability-development/SKILL.md

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.