CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

recipe-front-build

Execute materialized frontend task files in autonomous execution mode

Quality

70%

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

75%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 dense, highly structured orchestration recipe: concrete subagent invocations, explicit decision tables, gated commits, and feedback loops for error recovery. Its main weaknesses are repetitive gate restatements and heavy reliance on external skills to define several named procedures, which leave minor gaps in actionability and workflow clarity.

DimensionReasoningScore

Conciseness

The body is dense procedural instruction with no explanation of concepts Claude already knows, but has minor redundancy — the Review Resolution Gate and 'Consumed Task Set' are restated several times and MANDATORY emphases repeat — so it fits 'efficient; minor instances that could be trimmed' rather than the every-token-earns-its-place anchor.

4 / 5

Actionability

Guidance is mostly executable: exact subagent_type strings ("dev-workflows-frontend:task-decomposer", "dev-workflows-frontend:code-reviewer"), a prompt template, restricted glob patterns, a decision table, and status-field routing. The gap keeping it from 5 is that key operations like 'Apply Specialist Result Acceptance' and Review Resolution resolve only in the external subagents-orchestration-guide skill.

4 / 5

Workflow Clarity

The phased sequence (prerequisites → materialization → checklist → 4-step cycle → post-implementation review → cleanup → report) is explicit, with a pre-execution checklist, quality gates before every commit, and feedback loops (needs_revision → rerouted corrections → re-review convergence; verification-limitation retries). It falls short of anchor 5 because several validation checkpoints delegate their actual semantics to the external orchestration-guide skill rather than stating them.

4 / 5

Progressive Disclosure

Good single-file structure with clear section headers; the sole file reference (references/review-resolution.md) is clearly signaled and attributed to the loaded subagents-orchestration-guide skill, and bulk detail is delegated to named external skills. There is no local bundle to split, so organization is appropriate, though the inlined branching detail is dense enough that anchor 5's 'easy navigation' is not fully met.

4 / 5

Total

16

/

20

Passed

Description

53%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 short, third-person, and names a specific niche, but it is thin: one generic verb ('execute'), jargon-heavy terms ('materialized', 'autonomous execution mode'), and no 'Use when...' trigger guidance. It communicates the domain but not the scope of actions or the invocation context.

Suggestions

Add an explicit trigger clause, e.g., "Use when the user provides a frontend work plan or materialized task files and requests autonomous batch execution" — the missing 'when' currently caps completeness at 3.

Enumerate the concrete actions the recipe performs (materialize tasks from a work plan, execute with per-task quality gates, run post-implementation code and security reviews, commit, and clean up consumed task files) instead of the single generic 'execute' verb.

Include natural user phrasings and synonyms such as "run the frontend tasks", "execute the work plan", or "frontend build" alongside the current jargon to improve trigger-term coverage.

DimensionReasoningScore

Specificity

"Execute materialized frontend task files in autonomous execution mode" names the domain and one concrete action but omits the recipe's other concrete operations (task materialization, quality gating, post-implementation review, commits, cleanup), matching the '1-2 concrete actions, not comprehensive' anchor rather than the several-specific-actions anchor at 4.

3 / 5

Completeness

The description gives a clear 'what' ("Execute materialized frontend task files") but contains no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines; 'autonomous execution mode' only weakly implies 'when'.

3 / 5

Trigger Term Quality

"frontend", "task files", and "autonomous execution" are relevant keywords, but "materialized" and "autonomous execution mode" are internal jargon and natural user phrasings like "run the frontend tasks" or "execute the work plan" are missing, so coverage falls short of anchor 4 while exceeding the generic-only anchors.

3 / 5

Distinctiveness Conflict Risk

"materialized frontend task files" plus "autonomous execution mode" carves a mostly distinct niche with only minor overlap risk against sibling recipes (e.g., a backend/fullstack variant), fitting anchor 4; anchor 5 would require explicit distinct trigger phrases, which are absent.

4 / 5

Total

13

/

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: 1 missing

Warning

Total

15

/

16

Passed

Repository

shinpr/claude-code-workflows

Path

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