CtrlK
BlogDocsLog inGet started
Tessl Logo

check-impl-against-spec

Compare a pull request's implementation against spec context in spec_context.md and feed any material mismatches into review.json. Use during PR review when approved or repository spec context is available.

67

Quality

80%

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

86%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 a tight, well-structured instruction-only skill with concrete file references and clear enumerated mismatch criteria. It excels on conciseness and organization; actionability and workflow clarity are just short of the top anchor due to the absence of a concrete example finding and a validation loop.

Suggestions

Add one short example of a material-mismatch finding as it should appear in review.json to lift actionability.

Add an explicit verify step (e.g., re-confirm each flagged mismatch against the cited spec commitment before writing it) to strengthen workflow_clarity.

Optionally show the mapping from a spec commitment type to where its finding lands (inline comment vs review summary) to reduce ambiguity in the Outputs section.

DimensionReasoningScore

Conciseness

The body is lean and well-sectioned (Goal, Inputs, Process, Outputs, Boundaries) with no padding and no explanation of concepts Claude already knows; every line earns its place. Not below 5 because there is no over-explanation to trim.

5 / 5

Actionability

Concrete, file-specific guidance (spec_context.md, pr_diff.txt, pr_description.md, review.json) with an enumerated list of what counts as a 'material' mismatch. Not a 5 because, as an instruction-only skill, it lacks a concrete example of what a folded finding in review.json should look like.

4 / 5

Workflow Clarity

A clear four-step numbered sequence with an explicit decision checkpoint (material vs harmless differences) in step 3. Not a 5 because there is no explicit validation/verification loop, though the read-only nature of the task means one is less critical.

4 / 5

Progressive Disclosure

Under 50 lines with no need for external references, and the content is well-organized into clear sections, satisfying the simple-skill exception for a top score. No bundle files exist, so there is nothing to over- or under-reference.

5 / 5

Total

18

/

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 concise, third-person, and clearly states both the action and trigger conditions with concrete file references. It is strong across all dimensions but stops short of the top anchor due to narrower action coverage and situation- rather than phrase-based triggers.

Suggestions

Broaden the action list slightly (e.g., 'extract spec commitments, compare against the diff, surface material drift') to push specificity toward comprehensive coverage.

Add explicit user-facing trigger phrases (e.g., 'when the user asks to check the PR against the spec' or mentions 'spec drift') to strengthen completeness and trigger term quality.

Mention 'specification' or 'design doc' as synonyms of 'spec context' to reduce reliance on a single term.

DimensionReasoningScore

Specificity

Names the domain and concrete, file-specific actions ('Compare a pull request's implementation against spec context in spec_context.md', 'feed any material mismatches into review.json') rather than vague verbs. Not a 5 because coverage is limited to two actions rather than a comprehensive set.

4 / 5

Completeness

Explicitly answers both what (compare implementation vs spec, feed mismatches into review.json) and when ('Use during PR review when approved or repository spec context is available'). Not a 5 because the when clause is situation-conditional rather than enumerating concrete user-facing trigger phrases.

4 / 5

Trigger Term Quality

Includes natural terms a user would say ('PR review', 'pull request', 'spec context', 'approved', 'spec_context.md') with good coverage. Not a 5 because common synonyms like 'specification' or 'design doc' are absent.

4 / 5

Distinctiveness Conflict Risk

Clear niche (spec-alignment check during PR review) with distinct triggers tied to specific files, low overlap risk. Not a 5 because it sits adjacent to general code-review skills and could marginally overlap.

4 / 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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
warpdotdev/common-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.