CtrlK
BlogDocsLog inGet started
Tessl Logo

wp-interactivity-api

Use when building or debugging WordPress Interactivity API features (data-wp-* directives, @wordpress/interactivity store/state/actions, block viewScriptModule integration, wp_interactivity_*()) including performance, hydration, and directive behavior.

70

Quality

86%

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

SKILL.md
Quality
Evals
Security

Quality

Content

72%

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

A well-structured, actionable skill body with good progressive disclosure to real reference files. It loses points on conciseness (some redundancy with references and restated basics) and workflow clarity (missing explicit validation feedback loops for risky directive edits).

Suggestions

Trim the inline server-side-rendering explanation and derived-state PHP examples, deferring them to references/server-side-rendering.md to reduce duplication and token cost.

Add an explicit validate -> fix -> re-validate feedback loop in the 'Implement or change directives safely' and 'Debug common failure modes' steps for risky store/directive changes.

Avoid restating well-known concepts (e.g. SEO/perceived-load benefits of SSR) that Claude already understands.

DimensionReasoningScore

Conciseness

Mostly efficient with executable code and tight sections, but it restates some Interactivity API concepts Claude already knows (e.g. explaining server-side rendering benefits like 'no layout shift', 'SEO benefits') and includes inline PHP/derived-state detail that duplicates the dedicated references/server-side-rendering.md.

2 / 3

Actionability

Provides concrete, executable PHP snippets (wp_interactivity_state, wp_interactivity_data_wp_context, block.json supports.interactivity), specific search anchors (data-wp-interactive, viewScriptModule), and copy-paste-ready examples.

3 / 3

Workflow Clarity

A clear six-step procedure with numbered sections, but the debug/verification steps lack explicit validation feedback loops (validate -> fix -> retry) for risky directive/store changes; the 'Verification' section is a checklist without re-validation on failure.

2 / 3

Progressive Disclosure

Well-organized body with one-level-deep references to real bundle files (references/server-side-rendering.md, directives-quickref.md, debugging.md), each clearly signaled where relevant; content is appropriately split rather than nested.

3 / 3

Total

10

/

12

Passed

Description

100%

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, specific description with concrete capabilities, explicit 'Use when' trigger guidance, and natural keywords. It is in third person and clearly distinguishable from other skills.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities: building/debugging 'data-wp-* directives', '@wordpress/interactivity store/state/actions', 'block viewScriptModule integration', and 'wp_interactivity_*()' functions.

3 / 3

Completeness

Explicit 'Use when...' clause states what it does (build/debug Interactivity API features) and when to invoke it (performance, hydration, directive behavior).

3 / 3

Trigger Term Quality

Includes natural terms users would say ('Interactivity API', 'data-wp-* directives', 'hydration', 'directives don't fire') alongside technical identifiers, giving strong coverage.

3 / 3

Distinctiveness Conflict Risk

The WordPress Interactivity API niche with its specific directive/store terms is clearly distinct and unlikely to trigger for unrelated skills.

3 / 3

Total

12

/

12

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.