CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

recipe-implement

Orchestrate the complete implementation lifecycle from requirements to deployment

Quality

56%

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/recipe-implement/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 lean, highly actionable orchestration recipe with a well-sequenced workflow, explicit status-based validation checkpoints, and error-recovery feedback loops. Its main weaknesses are the repeated, scattered invocations of the external subagents-orchestration-guide dependency and ambiguous references to file paths that belong to other skills' bundles rather than this one.

Suggestions

Disambiguate cross-skill references by always qualifying the owning skill (e.g., 'references/review-resolution.md in the subagents-orchestration-guide skill bundle') or add a short 'Dependencies' section listing the external skills and their referenced files in one place.

Consolidate the repeated subagents-orchestration-guide execution rules (invoked in at least five separate sections) into a single early section, keeping later steps to step-specific instructions only.

Clarify that this skill has no local reference files (or add one for the field/status vocabulary, e.g., the meaning of observable_verification, mutationEvidence, and each status value) so readers do not hunt for a local references/ directory that does not exist.

DimensionReasoningScore

Conciseness

The body is dense and imperative with essentially no padding or explanation of concepts Claude already knows — every line is directive (e.g., "Record the current HEAD as diffBase", "Commit only after quality-fixer returns pass or verification_incomplete"). It falls short of anchor 5 only through repeated restatements of the subagents-orchestration-guide dependency across sections, which could be consolidated.

4 / 5

Actionability

For an instruction-only skill the guidance is highly concrete: exact subagent types ("dev-workflows:task-executor", "dev-workflows:code-reviewer"), specific fields to pass (task_file, diffBase, governing_sources, target_paths, observable_verification, changedTestFiles, mutationEvidence), and explicit status-based routing (stub_detected, verification_incomplete, needs_revision). It stays at anchor 4 rather than 5 because much of the executable detail is deferred to external skills whose content is not shown, leaving minor gaps a reader must resolve elsewhere.

4 / 5

Workflow Clarity

The multi-step process is clearly sequenced (situation assessment, scale binding, 4-step per-task cycle, post-implementation review, final cleanup) with explicit validation checkpoints ([Stop] markers, Review Resolution Gate, status checks at each cycle step) and genuine feedback loops (needs_revision and stub_detected return to step 1; retained verification limitations are retried). The destructive task-file deletion even has failure handling, but the density and heavy reliance on the external orchestration guide leave minor gaps that keep it below anchor 5.

4 / 5

Progressive Disclosure

The skill has no bundle files of its own, yet the body cites paths like "references/review-resolution.md" and "references/criteria.md" without clearly signaling that these live inside other skills' bundles (subagents-orchestration-guide, requirement-convergence) — the references are effectively buried and ambiguous. Section structure within the 145-line body is reasonable, placing this at anchor 3 ('some structure but references not clearly signaled') rather than 4.

3 / 5

Total

15

/

20

Passed

Description

25%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 single vague clause: it names a broad domain but gives no concrete actions, no natural trigger terms, and no usage conditions. As a result it is hard to distinguish from general development-workflow skills and unlikely to be reliably surfaced for the right task.

Suggestions

Add an explicit 'Use when...' clause naming the situations that should trigger this skill (e.g., 'Use when the user asks to implement a feature end-to-end, from requirements analysis through design, implementation, QA, and deployment').

List the concrete lifecycle stages the skill orchestrates (requirements analysis, design doc, work plan, per-task implementation with quality verification, post-implementation code/security review, cleanup) instead of the single verb 'Orchestrate'.

Include natural trigger phrases and synonyms users would actually say (e.g., 'full-cycle implementation', 'take this feature from spec to deployment', 'run the implementation workflow') to improve both trigger quality and distinctiveness.

DimensionReasoningScore

Specificity

The description names its domain ("implementation lifecycle", "from requirements to deployment") but offers only the single generic action "Orchestrate" with no concrete capabilities, matching the anchor 'names the domain but actions are minimal or generic'. It does not reach anchor 3 because no specific concrete action (analogous to 'extracts content') is stated.

2 / 5

Completeness

There is a vague 'what' ("Orchestrate the complete implementation lifecycle") and no 'when' guidance at all, matching anchor 2 ('has a vague what and no when'). Even the anchor-3 bar of a clear 'what' is not met, and the missing 'Use when...' clause independently caps completeness at 3.

2 / 5

Trigger Term Quality

Only "implementation lifecycle", "requirements", and "deployment" appear — domain jargon rather than phrases a user would naturally say to invoke this skill. It sits at anchor 2 ('one or two generic keywords; missing the natural phrases users say') rather than 3, since no common variations or synonyms are present.

2 / 5

Distinctiveness Conflict Risk

"Complete implementation lifecycle from requirements to deployment" claims an extremely broad scope that overlaps with virtually any development-workflow or planning skill, matching anchor 2 ('very broad; high overlap risk with many similar skills'). It is not entirely generic (anchor 1) because the domain is at least named.

2 / 5

Total

8

/

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

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

15

/

16

Passed

Repository

shinpr/claude-code-workflows

Path

skills/recipe-implement/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.