CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

recipe-front-build

Execute materialized frontend task files in autonomous execution mode

Quality

73%

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 ./dev-workflows-frontend/skills/recipe-front-build/SKILL.md

The canonical home for this skill is recipe-front-build in shinpr/claude-code-workflows

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.

This is a well-engineered orchestration skill: the workflow is explicitly sequenced with validation gates, checklists, and error-recovery loops, and routing guidance is highly concrete (exact subagent types, fields, and file patterns). Its main weaknesses are minor — some duplicated rules, non-templated invocation prompts, and delegation of key procedures to external skills by name rather than path.

DimensionReasoningScore

Conciseness

The body is dense, instruction-only prose that assumes competence and delegates background to other skills (e.g., "Execute Skill: subagents-orchestration-guide") with no concept explanations. Minor duplication exists — the CRITICAL commit rule restates step 4's rule, and the Consumed Task Set pattern is re-explained — matching anchor 4 ("efficient; minor instances of over-explanation that could be trimmed") rather than anchor 5's every-token-earns-its-place.

4 / 5

Actionability

Guidance is concrete and executable: exact subagent_type values ("dev-workflows-frontend:task-decomposer", "dev-workflows-frontend:task-executor-frontend"), exact file patterns ("{plan-name}-task-*.md"), named response fields (requiresTestReview, mutationEvidence, incompleteImplementations), and a decision table. Minor gaps keep it below anchor 5: invocation prompts are only templated for task-decomposer, and key procedures (Specialist Result Acceptance, Review Resolution) are delegated by name to an external skill rather than specified here.

4 / 5

Workflow Clarity

The multi-phase sequence (prerequisites → conditional materialization → 4-step per-task cycle → post-implementation review → cleanup → report) is explicitly ordered ("in this order", "Advance only when the current phase's stated transition condition is satisfied") with a pre-execution checklist, validation gates (quality-fixer pass/verification_incomplete before commit, consumed-set recompute after generation), and explicit error-recovery feedback loops (stub_detected → step 1, needs_revision → rerouted corrections → re-review convergence, verification-limitation retry). This matches anchor 5 ("clear sequence with explicit validation steps; feedback loops for error recovery; checklists"), and the batch-operation validation cap does not apply because validation is present throughout.

5 / 5

Progressive Disclosure

The body is well-sectioned with clear headers and appropriately keeps its orchestration logic inline at ~130 lines; the single reference ("read `references/review-resolution.md` from the loaded subagents-orchestration-guide skill") is clearly signaled and one level deep. It is not anchor 5 because there are no in-bundle reference files organizing detail further, and the one reference points into another skill's bundle, which is mildly confusing; it is above anchor 3 because structure is good and nothing that belongs in a separate file is inlined.

4 / 5

Total

17

/

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 terse and identifies a distinct niche (autonomous frontend task execution), but it names only a single action, leans on internal jargon ("materialized"), and provides no explicit "Use when..." trigger guidance. It communicates a clear "what" while leaving the "when" almost entirely implicit.

Suggestions

Add an explicit trigger clause, e.g., "Use when the user provides a work plan or asks to run frontend task files autonomously/batch-mode," to satisfy the 'when' half of completeness.

Enumerate the concrete actions the skill performs (materialize plan tasks, run per-task quality gates, commit each task, review the implementation, clean up task files) instead of the single verb "execute".

Replace pipeline jargon like "materialized" with natural user vocabulary ("run", "build", "implement") so the description matches phrases users would actually say when invoking the skill.

DimensionReasoningScore

Specificity

Quotes: "Execute materialized frontend task files" and "in autonomous execution mode". It names the domain (frontend task files) and one concrete action (execute) qualified by an execution mode, matching anchor 3 ("names domain and 1-2 concrete actions, but not comprehensive"). It is more informative than anchor 2's bare "Processes PDF files" but does not list several actions, so it is not anchor 4.

3 / 5

Completeness

The description gives a clear "what" ("Execute materialized frontend task files") but no "Use when..." clause; "in autonomous execution mode" is a mode descriptor, not explicit trigger guidance, so the guideline capping completeness at 3 applies. This matches anchor 3 ("clear 'what' but 'when' missing or only weakly implied") and cannot be anchor 4, which requires both what and when.

3 / 5

Trigger Term Quality

Keywords like "frontend", "task files", and "autonomous execution" are somewhat natural, but "materialized" is internal pipeline jargon and common user phrasings like "run", "build", or "implement tasks" are absent — anchor 3 ("some relevant keywords but missing common variations or synonyms"). It is above anchor 2 because several genuinely relevant terms are present, but below anchor 4's "good keyword coverage".

3 / 5

Distinctiveness Conflict Risk

The combination "materialized frontend task files" + "autonomous execution mode" carves a distinct niche with explicit differentiators (frontend vs. other stacks, autonomous batch execution), leaving only minor overlap risk with closely related workflow skills — anchor 4 ("mostly distinct; minor overlap risk"). It is not anchor 5 because the description lacks distinct trigger phrases that would fully separate it from sibling dev-workflow recipes.

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

dev-workflows-frontend/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.