CtrlK
BlogDocsLog inGet started
Tessl Logo

review-spec

Deep adversarial specification review using the 8-lens review constitution. Evaluates design documents, plans, and specs for ambiguity, completeness, feasibility, security, and MockServer-specific concerns. Loaded by review-cheap and review-final agents.

60

Quality

70%

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 ./.opencode/skills/review-spec/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.

The body is a well-sequenced, actionable adversarial review methodology with strong workflow checkpoints and clear output templates. Its main weakness is mild redundancy between inlined lens-priority detail and the referenced constitution file.

Suggestions

Reduce the inlined per-lens principle-ID lists now that the constitution file is read in full, keeping only lens-level guidance and pointing to the constitution for the ID catalog.

Consider moving the lens-priority and structure-expection detail into a referenced file so SKILL.md stays a lean overview.

Add a one-line pointer near the top summarizing the expected output artifact so the workflow's end state is immediately clear.

DimensionReasoningScore

Conciseness

The body is efficient and avoids explaining concepts Claude already knows, but the per-lens principle ID listings partly duplicate content already promised by the referenced constitution file, so minor trimming is possible.

4 / 5

Actionability

Concrete, executable guidance is provided via a mandatory finding format template, a verdict rule, and an exact output structure; as an instruction-only skill this is highly actionable with only minor gaps.

4 / 5

Workflow Clarity

The eight steps are clearly sequenced with explicit validation checkpoints (Step 5's representative-sample verification and Step 7's pre-verdict completeness checklist) and feedback loops for error recovery.

5 / 5

Progressive Disclosure

Structure is well organized with clearly signaled one-level-deep references to external rule/template files, but some inlined principle-ID detail overlaps the referenced constitution, leaving a minor organization gap.

4 / 5

Total

17

/

20

Passed

Description

58%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 clearly conveys what the skill does and establishes a distinct niche, but lacks an explicit 'Use when...' trigger clause and richer natural trigger terms. It is solid but leaves the activation condition implicit.

Suggestions

Add an explicit 'Use when ...' clause naming the natural trigger phrases (e.g., 'Use when reviewing a spec, design doc, or plan for defects').

Include user-natural synonyms and concrete triggers like 'spec review', 'design document review', or 'find defects in a spec'.

Clarify the 'when' beyond who loads it ('Loaded by review-cheap and review-final agents') to describe the situations that call for this skill.

DimensionReasoningScore

Specificity

Names the domain (specification review) and several concrete actions — 'Evaluates design documents, plans, and specs for ambiguity, completeness, feasibility, security' — but coverage is slightly less comprehensive than a full action list.

4 / 5

Completeness

The 'what' is clear (deep adversarial review evaluating specs across multiple quality dimensions), but there is no explicit 'Use when...' clause; the 'when' is only weakly implied, which caps completeness at 3 per the guidelines.

3 / 5

Trigger Term Quality

Relevant keywords ('specification review', 'design documents', 'plans', 'specs') are present, but common variations/synonyms and explicit trigger phrasing users would naturally say are missing.

3 / 5

Distinctiveness Conflict Risk

The '8-lens review constitution' and 'MockServer-specific concerns' framing carves a clear niche with mostly distinct triggers, with only minor overlap risk against general review skills.

4 / 5

Total

14

/

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
mock-server/mockserver-monorepo
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.