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

72%

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

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

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.

The body is a tightly engineered orchestration recipe with an unambiguous 9-step flow, concrete subagent invocation specs, and strong validation feedback loops. Its weaknesses are moderate verbosity in the prerequisite definitions and gate restatements, plus one dangling reference to an undeclared serialization format.

Suggestions

State the prompt serialization format once (e.g., a short field-format spec) so the "apply only the declared serialization" instruction in the Execution Method is actually resolvable.

Compress Step 1's implementationFiles inclusion rule to its decision principle and delegate the path-category enumeration to a reference file or the code-reviewer contract.

DimensionReasoningScore

Conciseness

The body is almost entirely procedural with no explanations of concepts Claude already knows, but it could be tightened: Step 1's implementationFiles definition is a single ~60-word sentence enumerating obvious path categories, and the Review Resolution Gate mandate is restated in Steps 4, 5, and 8 rather than stated once.

3 / 5

Actionability

Guidance is largely executable — exact subagent_type values, literal description and prompt strings, a routing table, and copy-ready report templates — but "apply only the declared serialization" references a serialization format that is never declared anywhere in this file, leaving a minor gap between the prompts and their assembly.

4 / 5

Workflow Clarity

Steps 1-9 are explicitly sequenced with per-step activation conditions and convergence criteria, and validation is thorough: a quality gate with routed outcomes (pass / stub_detected / verification_incomplete / blocked) including a fix-retry loop, re-validation of corrected findings, diff-hunk-to-approved-finding mapping, a retry-once rule for retained limitations, and a final reconciliation report — matching the anchor with explicit validation steps and error-recovery feedback loops.

5 / 5

Progressive Disclosure

The skill bundle contains no reference, script, or asset files, and the body's single file reference (references/review-resolution.md) is one level deep and clearly attributed to the externally loaded subagents-orchestration-guide skill; sections are well organized, with only minor gaps such as the inline report templates that could live in a reference file.

4 / 5

Total

16

/

20

Passed

Description

58%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 clearly states what the skill does with a specific frontend/React review-and-correction scope, but it lacks any explicit "when to use" trigger and leans on internal jargon ("governing-source compliance", "scope economy") that users would not naturally say. It is serviceable but below the quality of the good examples, which pair concrete actions with natural trigger phrases.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to review, verify, or QA a finished React/TypeScript frontend implementation before merge or handoff."

Replace internal jargon ("governing-source compliance", "scope economy") with natural user-facing phrasing such as "Design Doc compliance" and "scope creep" so the description matches what users actually say.

Include one or two common synonyms ("code review", "PR review", "pre-merge check") to improve trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain and several distinct actions ("Reviews completed frontend implementation", "applies user-approved React corrections") across four review areas, but "governing-source compliance" and "scope economy" remain abstract rather than concrete, so it falls short of the comprehensive, fully concrete anchor 5.

4 / 5

Completeness

The "what" is clear (review completed frontend implementation across four areas, then apply approved corrections), but there is no "Use when..." clause or equivalent explicit trigger guidance; "completed frontend implementation" only weakly implies timing, so the missing-when cap of 3 applies.

3 / 5

Trigger Term Quality

"frontend", "React", and "security" are natural user terms, but "governing-source compliance", "scope economy", and "repository quality" are internal jargon, and common variations users would actually say ("code review", "pull request", "QA") are missing — matching anchor 3 (some relevant keywords, missing common variations).

3 / 5

Distinctiveness Conflict Risk

The post-implementation review plus user-approved correction-routing niche is mostly distinct with specific triggers, though it could minorly overlap with generic code-review or security-review skills.

4 / 5

Total

14

/

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-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.