CtrlK
BlogDocsLog inGet started
Tessl Logo

recipe-design

Execute from codebase-scoped analysis through optional ADR decisions to complete Design Doc approval

54

Quality

61%

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-design/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 content is a tightly written, highly actionable orchestration recipe with explicit sequencing, validation checkpoints, and feedback loops. Its main gap is a few justificatory sentences that could be trimmed for peak token efficiency.

DimensionReasoningScore

Conciseness

The body is dense and assumes competence without explaining what an ADR or Design Doc is; a few rationale sentences (e.g., 'This independent discovery keeps scope ... grounded in repository evidence') could be trimmed, keeping it just below a 5.

4 / 5

Actionability

As an instruction-only orchestration skill it provides exact field names, ordering, and conditions for each subagent invocation (e.g., `document_to_create: ADRBatch`, `decision_points` ordering), which is highly actionable with only minor template-slot gaps.

4 / 5

Workflow Clarity

Seven steps are clearly sequenced with explicit `[Stop]` checkpoints, Review Resolution feedback loops, rerun-after-correction loops, and a Completion Criteria checklist, matching the anchor for clear sequence with validation and error-recovery loops.

5 / 5

Progressive Disclosure

No bundle files exist for this skill, but the body is well-organized into clearly signaled sections (Flow, Steps 1-7, Completion Criteria); the one cross-skill reference is explicitly attributed to another skill's bundle.

4 / 5

Total

17

/

20

Passed

Description

42%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 conveys a clear purpose and domain but is abstract and jargon-heavy, with no explicit trigger ('Use when...') guidance. It is distinguishable but risks overlap within its skill family.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers (e.g., 'Use when the user asks to produce or approve a Design Doc, decide ADRs, or run a codebase-scoped design phase').

Replace jargon like 'codebase-scoped analysis' with phrases users actually say (e.g., 'analyze the codebase', 'design doc', 'architecture decision records') and include synonyms.

List 1-2 more concrete actions (e.g., '...qualify ADR decision points and route reviewer findings') to lift specificity toward comprehensive coverage.

DimensionReasoningScore

Specificity

Names the domain ('codebase-scoped analysis', 'ADR decisions', 'Design Doc approval') with a couple of concrete actions, but 'Execute from ... through ... to complete' describes a flow abstractly rather than comprehensively listing actions.

3 / 5

Completeness

It gives a clear 'what' (the analysis-to-approval flow) but no 'when'/'Use when...' clause, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

Terms like 'codebase-scoped analysis' and 'ADR decisions' are technical jargon; while 'Design Doc' is a term a domain user might say, the natural trigger phrases a user would actually speak are largely missing.

2 / 5

Distinctiveness Conflict Risk

The design-doc/ADR approval niche is somewhat specific, but as one of a family of dev-workflows orchestration skills it could still overlap with closely related sibling skills.

3 / 5

Total

11

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Repository
shinpr/claude-code-workflows
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.