CtrlK
BlogDocsLog inGet started
Tessl Logo

recipe-build

Execute materialized task files in autonomous execution mode

50

Quality

55%

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-build/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, well-sequenced orchestrator recipe with concrete agent invocations, explicit validation checkpoints, and strong feedback loops. It practices progressive disclosure by leaning on other named skills for detail rather than inlining it.

DimensionReasoningScore

Conciseness

The body is terse procedural routing with no concept-explaining padding (it assumes Claude knows git, commits, agents); the only trimmable excess is repeated cross-references to subagents-orchestration-guide, keeping it just above the mostly-efficient anchor at 3.

4 / 5

Actionability

It names concrete subagent_types ("dev-workflows:task-decomposer", "dev-workflows:task-executor", "dev-workflows:code-verifier", "dev-workflows:security-reviewer") with specific parameters (task_file, diffBase, mutationEvidence, qualityCommand) and status routing, leaving only minor gaps in exact prompt text for some calls.

4 / 5

Workflow Clarity

Phases are explicitly sequenced (Prerequisites → Materialization → Checklist → 4-step Execution Cycle → Post-Implementation Verification → Final Cleanup → Completion Report) with a Pre-execution Checklist and explicit feedback loops (needs_revision returns to step 1; quality-fixer runs before every commit), matching the clear-sequence-with-validation-and-feedback anchor.

5 / 5

Progressive Disclosure

The skill acts as a well-sectioned overview that offloads detail to clearly signaled external skills ("Execute Skill: subagents-orchestration-guide", "read references/review-resolution.md") rather than duplicating it; the only gap is the absence of its own bundle files, leaving it just below the ideal one-level-deep-references anchor.

4 / 5

Total

17

/

20

Passed

Description

30%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 specific about its niche but reads as internal jargon rather than user-facing trigger language and omits any explicit "when to use" guidance. It is distinguishable but minimal in both action coverage and natural trigger terms.

Suggestions

Add an explicit "Use when…" clause stating when Claude should invoke this skill (e.g., "Use when the user asks to run a batch of materialized task files autonomously").

Rewrite using natural trigger terms a user would actually say — "run task files", "execute the task batch", "autonomously work through task files" — instead of "materialized task files in autonomous execution mode".

List 1-2 more concrete actions (e.g., decompose, execute, quality-fix, verify, commit) to lift specificity above a single generic verb.

DimensionReasoningScore

Specificity

"Execute materialized task files in autonomous execution mode" names the domain and a single action (execute); the qualifiers "materialized" and "autonomous execution mode" describe the domain rather than adding distinct concrete actions, so it sits below the 1-2-actions anchor at 3.

2 / 5

Completeness

It states a clear "what" (execute task files autonomously) but provides no "Use when…" trigger guidance; per the rubric a missing explicit trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

The phrasing is technical jargon ("materialized task files", "autonomous execution mode") that a user would not naturally say when requesting this skill, matching the no-natural-keywords anchor.

1 / 5

Distinctiveness Conflict Risk

"Execute task files" is somewhat specific to this orchestrator niche but broad enough to overlap with other task-execution skills, matching the somewhat-specific-but-overlapping anchor.

3 / 5

Total

9

/

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.