CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

intended-vs-implemented

Moved to phuryn/product-engineering, where it is maintained in the ai-shipping plugin; this copy says where it went and how to install it. Use when asked to find where the code does something other than its docs say.

Quality

87%

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

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

The body is an exemplary redirect notice: lean, unambiguous conditional branches, and copy-paste install commands that cover the common cases. The only minor gap is that the instruction to turn off `pm-ai-shipping` does not specify how to do so.

DimensionReasoningScore

Conciseness

Every sentence earns its place: relocation pointer, why the copy exists, two-branch guidance, copy-paste install commands, and a cleanup note, with no padding or explanations of concepts Claude already knows. This matches anchor 5; it is not 4 because there is no over-explanation to trim.

5 / 5

Actionability

The main path is fully executable with copy-paste commands ("claude plugin marketplace add phuryn/product-engineering", "claude plugin install ai-shipping@product-engineering") and clear conditional branches, but "turn off `pm-ai-shipping` here" gives no specific mechanism — a minor gap matching anchor 4. It is not 5 because of that gap, and not 3 because the guidance is executable rather than pseudocode or vague hints.

4 / 5

Workflow Clarity

This is a single-purpose redirect skill and the single action is unambiguous: if installed use the other skill, otherwise tell the user it moved, give install commands, and help anyway. No destructive or batch operations are involved, so the simple-skill exception applies and it matches anchor 5; it is not 4 because there is no ambiguity or missing checkpoint.

5 / 5

Progressive Disclosure

The body is under 50 lines with no need for external references, and content is well organized with clearly signaled one-level-deep external links (the GitHub repo and README), matching anchor 5 per the under-50-lines guideline. It is not 4 because nothing is inlined that belongs in a separate file.

5 / 5

Total

19

/

20

Passed

Description

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

The description is a well-constructed tombstone notice: it answers both what this copy does and when it should fire, in third person, with a highly distinct trigger. Its weaknesses are narrow trigger-term coverage (a single phrasing with no synonyms) and thin capability specificity, since it describes the redirect mechanics rather than the skill's actual function.

Suggestions

Broaden the 'Use when' clause with natural variations users would say, e.g. "Use when the docs don't match the code, the implementation differs from the spec, or you're asked to compare intent vs implementation".

Briefly state what the underlying skill does (compares intended behavior from docs/specs against the actual implementation) so the description conveys concrete capability, not just the relocation notice.

DimensionReasoningScore

Specificity

"this copy says where it went and how to install it" names the domain plus 1-2 concrete actions (stating the relocation, giving install guidance), matching anchor 3. It is not 4 because it does not list several specific actions, and not 2 because the actions it names are concrete rather than generic.

3 / 5

Completeness

It explicitly answers both what ("this copy says where it went and how to install it") and when ("Use when asked to find where the code does something other than its docs say") with a concrete trigger phrase, matching anchor 5. It is not 4 because the when-clause is already explicit and concrete, not merely improvable. Voice is third person, so no penalty applies.

5 / 5

Trigger Term Quality

The trigger "Use when asked to find where the code does something other than its docs say" is a natural, relevant phrase, but it is the only variation — common synonyms like "docs don't match the code", "spec vs implementation", or "implementation drift" are missing, matching anchor 3. It is not 4 because more than a few natural terms are missing, and not 2 because the phrase is specific rather than generic.

3 / 5

Distinctiveness Conflict Risk

"find where the code does something other than its docs say" carves out a clear niche trigger with minimal conflict risk against other skills, matching anchor 5. It is not 4 because there is no meaningful overlap even with closely related skills.

5 / 5

Total

16

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

phuryn/pm-skills

Path

pm-ai-shipping/skills/intended-vs-implemented/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.