CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

recipe-front-review

Reviews completed frontend implementation for governing-source compliance, scope economy, repository quality, and security, then applies user-approved React corrections.

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-review/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

73%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 recipe: a fully sequenced 9-step workflow with explicit gates, validation loops, concrete subagent invocation specs, and report templates. Its main weaknesses are legalistic, hard-to-parse prose that could be tightened and one dangling reference ("Requirement Change Detection") plus dependence on procedures defined only in external skills.

Suggestions

Define or inline the 'Requirement Change Detection' step referenced in Step 4, since no such step or section exists in this skill.

Break up the long compound sentences (e.g. the Step 1 implementationFiles derivation) into short declarative rules or a bulleted inclusion list to cut tokens and improve parseability.

Consider moving the report templates and the finding-routing table into a references/ file to keep SKILL.md as a lean overview.

DimensionReasoningScore

Conciseness

The body teaches no concepts Claude already knows and is instruction-dense throughout, but many passages are legalistic and could be meaningfully tightened — e.g. the 90-word single sentence defining `implementationFiles` in Step 1 and phrasings like "Advance through each review, correction, and re-validation transition only at its declared convergence condition". This fits "mostly efficient but could be tightened" rather than the minor-trim level of a 4.

3 / 5

Actionability

The guidance is largely copy-paste executable: exact `subagent_type` strings, literal Agent prompt templates with declared substitution placeholders, a finding-to-route table, quality-gate result routing (pass / stub_detected / verification_incomplete / blocked), and report templates. It is not a 5 because Step 4 instructs "return to Requirement Change Detection", which is never defined or introduced anywhere in the body, and several procedures ("shared Re-run rule", "Specialist Result Acceptance") resolve only outside this document.

4 / 5

Workflow Clarity

Steps 1-9 are clearly sequenced with explicit activation conditions, convergence conditions for every transition, validation checkpoints (document review, quality gate, re-validation, reconciliation), and feedback loops for error recovery (stub_detected returns to Step 6, limitations get a retry, findings are reconciled by ID). This matches the anchor's checklist-and-feedback-loop profile exactly.

5 / 5

Progressive Disclosure

No bundle files exist (no references/, scripts/, or assets/ directories), so the body is a single self-contained document — the one file it cites, `references/review-resolution.md`, explicitly belongs to the separately loaded subagents-orchestration-guide skill, not a nested reference here. Sections are well organized (Orchestrator Definition, Execution Method, Execution Flow) and content is appropriately inline for a control-flow recipe; it is not a 5 because the ~180-line body is well over the simple-skill threshold and the routing table / report templates could arguably live in separate reference files.

4 / 5

Total

16

/

20

Passed

Description

55%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 communicates a clear, multi-faceted capability in third person with a concrete what, but it omits any when-to-use trigger guidance (capping completeness) and leans on internal jargon ("governing-source compliance", "scope economy") that weakens natural trigger terms and distinctiveness. Overall a serviceable but sub-par description for discovery purposes.

Suggestions

Add an explicit 'Use when...' clause with concrete trigger phrases, e.g. 'Use after completing a React/TypeScript frontend implementation, when the user asks to review, QA, or audit completed frontend work against its Design Doc.'

Replace or gloss the internal jargon ('governing-source compliance', 'scope economy') with natural user-facing terms such as 'Design Doc compliance', 'scope creep', and 'code quality'.

Add natural trigger synonyms (code review, QA, post-implementation check, audit) to reduce overlap ambiguity with generic code-review and security-review skills.

DimensionReasoningScore

Specificity

The description enumerates several concrete actions — "Reviews completed frontend implementation for governing-source compliance, scope economy, repository quality, and security, then applies user-approved React corrections" — naming four review dimensions plus correction application. It falls short of a 5 because "governing-source compliance" and "scope economy" are project-internal jargon rather than concrete user-recognizable actions, but it clearly exceeds the 1-2-action level of a 3.

4 / 5

Completeness

The "what" is clear (review completed frontend implementation across four dimensions, then apply approved corrections) but there is no "Use when..." clause or equivalent explicit trigger guidance — the rubric explicitly caps completeness at 3 in that case. It is not a 2 because the "what" half is concrete and specific, not vague.

3 / 5

Trigger Term Quality

Some natural terms are present ("frontend", "React", "review", "security", "corrections") but common variations users would actually say — "code review", "QA", "audit", "post-implementation check", "check my code" — are missing, and phrases like "governing-source compliance" and "scope economy" are jargon no user would naturally utter. Not a 4 because the natural-term coverage has real gaps and the jargon dilutes it.

3 / 5

Distinctiveness Conflict Risk

The post-implementation framing ("completed frontend implementation", "user-approved React corrections") gives it a niche, but generic "review" + "security" language creates overlap risk with broadly available code-review and security-review skills, and the absence of a distinguishing "when" clause makes mis-triggering more likely. It is not a 4 because the overlap with closely related review skills is more than minor.

3 / 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-review/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.