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

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/recipe-implement/SKILL.md

Quality

Content

77%

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

The content is highly actionable with clear sequenced workflows and validation loops for an orchestrator skill. Its main weakness is progressive disclosure: it leans heavily on an external skill referenced by name with no bundled files or clearly signaled navigation.

Suggestions

Either bundle the subagents-orchestration-guide flow excerpts as reference files or add clearly signaled one-level-deep links instead of relying on skill-name references.

Tighten the repeated 'MANDATORY subagents-orchestration-guide' compliance reminders into a single consolidated checkpoint list.

Consider moving the detailed per-task execution cycle and post-implementation verification into a reference file while keeping the body an overview.

Dimension	Reasoning	Score
Conciseness	The body is dense and largely instructional rather than explaining known concepts, but it repeats the same orchestration-guide compliance themes across multiple sections (e.g. repeated 'MANDATORY subagents-orchestration-guide skill reference') and could be tightened.	2 / 3
Actionability	It gives concrete, executable guidance: specific subagent_type values, exact status field checks, commands like 'git diff --name-only main...HEAD', and explicit file-glob patterns for cleanup, making it copy-paste ready.	3 / 3
Workflow Clarity	Multi-step processes are clearly sequenced with explicit checkpoints, [Stop] markers, parallel verification, and a fix-cycle loop that repeats 'until all pass or blocked', providing strong feedback loops for batch/verification operations.	3 / 3
Progressive Disclosure	No bundle files exist (references/, scripts/, assets/ are absent) and the body repeatedly points to an external 'subagents-orchestration-guide' skill by name rather than navigable file paths, so the disclosure structure is implicit rather than clearly signaled and organized.	2 / 3
	Total	10 / 12 Passed

Description

35%

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 conveys a high-level purpose but lacks the natural trigger terms and explicit 'Use when' guidance that would make it discoverable and distinctive. It reads as a label rather than an activation statement.

Suggestions

Add an explicit trigger clause, e.g. 'Use when implementing a feature or fix end-to-end, from requirements analysis through deployment.'

Replace or supplement 'Orchestrate' with concrete verbs a user would actually say (e.g. 'implement', 'plan', 'build', 'deploy').

Tie the description more tightly to a distinct niche so it does not overlap with general dev-workflow skills.

Dimension	Reasoning	Score
Specificity	Names the domain ('implementation lifecycle') and two endpoint phases ('requirements' and 'deployment') but lists only a single abstract action ('Orchestrate') rather than multiple concrete actions.	2 / 3
Completeness	It states what the skill does but offers no 'Use when...' clause or equivalent trigger guidance, so the 'when' is only implied; per the guidelines this caps completeness at 2.	2 / 3
Trigger Term Quality	The only verb is 'Orchestrate', an abstract term a user would rarely say; no natural trigger phrases like 'implement a feature' or 'deploy' are present.	1 / 3
Distinctiveness Conflict Risk	'Implementation lifecycle from requirements to deployment' has a recognizable niche but is broad enough to overlap with many dev-workflow and planning skills, and the trigger is generic.	2 / 3
	Total	7 / 12 Passed

Validation

100%

Warnings & errors only

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: shinpr/claude-code-workflows
Path: skills/recipe-implement/SKILL.md
Commit: 56ab6c1

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.