CtrlK
BlogDocsLog inGet started
Tessl Logo

recipe-front-build

Execute materialized frontend task files in autonomous execution mode

56

Quality

63%

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-front-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 body is a tightly-structured autonomous-execution orchestration recipe with concrete Agent invocations, an explicit 4-step cycle, validation gates, feedback loops, and a checklist. It is efficient and clearly navigable, with only minor redundancy and a few details deferred to external skills.

DimensionReasoningScore

Conciseness

Dense procedural content that assumes Claude's competence with only minor redundancy (the Consumed Task Set pattern and Review Resolution are restated several times); not a 5 because some trimming is possible.

4 / 5

Actionability

Concrete Agent invocations with explicit subagent_type values, named parameters (task_file, diffBase, mutationEvidence), and explicit status-routing fields give mostly executable guidance; not a 5 because several details are deferred to external skills.

4 / 5

Workflow Clarity

The explicit 4-step cycle (execute, branch, quality-fix, commit) with numbered steps, branch logic, validation gates, feedback loops (needs_revision/stub_detected return to step 1), and a pre-execution checklist matches 'Clear sequence with explicit validation steps; feedback loops for error recovery; checklists'.

5 / 5

Progressive Disclosure

Well-sectioned single file with clear headers and no nested references, but the detailed decision-flow table and status routing could arguably be split into reference files for this complex recipe; matches 'Good structure; most content appropriately placed; minor organization gaps'.

4 / 5

Total

17

/

20

Passed

Description

46%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 states a clear, narrowly-scoped 'what' but omits any 'when to use' trigger guidance and leans on technical jargon ('materialized', 'autonomous execution mode') rather than natural user phrasing. It is distinct as a niche but under-serves discoverability.

Suggestions

Add a 'Use when...' clause naming the natural trigger, e.g. 'Use when the user wants to run a batch of prepared frontend task files end-to-end without per-task confirmation.'

Replace jargon with natural terms users would say ('prepared frontend task files', 'run frontend tasks automatically') and include synonyms like 'frontend tasks', 'task files', 'batch execution'.

Expand the 'what' with the concrete phases the recipe runs (materialize tasks, execute per-task commit cycle, verify, cleanup) to lift specificity toward several distinct actions.

DimensionReasoningScore

Specificity

Names the domain (frontend task files) and one concrete action (execute in autonomous mode), matching 'Names domain and 1-2 concrete actions, but not comprehensive'; it does not list several actions to warrant a 4.

3 / 5

Completeness

A clear 'what' is stated but no 'Use when...' trigger guidance exists, so per the rubric completeness is capped at 3.

3 / 5

Trigger Term Quality

Terms like 'materialized' and 'autonomous execution mode' are technical jargon, and only 'frontend task files' is semi-natural; it misses the natural phrases and synonyms a user would actually say.

2 / 5

Distinctiveness Conflict Risk

The phrase carves a specific frontend task-execution niche with only minor overlap risk against sibling recipe skills, matching 'Mostly distinct; minor overlap risk'.

4 / 5

Total

12

/

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.