recipe-front-review

Design Doc compliance and security validation with optional auto-fixes

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

92%

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 written, highly actionable orchestration workflow with clear sequencing and validation feedback loops. Its main weakness is progressive disclosure: everything is packed into a single monolithic SKILL.md with no reference files split out.

Suggestions

Move the large report-format templates (Steps 4 and 11) and the route-recommendation table into a reference file (e.g., references/report-templates.md) and link to it, keeping SKILL.md as an overview.

Extract the auto-fixable / non-fixable / design-side-trigger lists into a separate reference so the core flow stays scannable.

Dimension	Reasoning	Score
Conciseness	The body is lean and operational — it assumes Claude's competence, references subagents by name, and avoids explaining concepts Claude already knows; every section earns its place.	3 / 3
Actionability	It provides concrete subagent_type values, copy-paste-ready prompts, explicit bash commands, and exact file paths rather than vague direction.	3 / 3
Workflow Clarity	Steps 1–11 are explicitly sequenced with validation checkpoints (blocked-stop verdict, re-validation in Steps 9–10) and feedback loops for fix→quality-check→re-validate recovery.	3 / 3
Progressive Disclosure	No bundle/reference files exist and all content lives inline in one ~226-line file; sections are well-organized but report templates and routing tables that could be split out are inline, so it is not a clean one-level-deep reference structure.	2 / 3
	Total	11 / 12 Passed

Description

50%

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 third-person and identifies a clear domain, but it is a single clause with no explicit use-trigger and only a couple of named actions. It reads as a terse label rather than a discoverable, self-triggering description.

Suggestions

Add an explicit 'Use when...' trigger clause (e.g., 'Use when validating a React/TypeScript frontend against its Design Doc after implementation').

Expand the action list with concrete behaviors (e.g., 'runs compliance and security reviews, routes findings to code-side fixes or Design-Doc updates') to lift specificity.

Include natural user-facing terms such as 'review', 'audit', and 'fix' to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain and a couple of actions ("compliance and security validation", "auto-fixes") but does not enumerate multiple specific concrete actions, so it stops at the 'names domain and some actions' anchor.	2 / 3
Completeness	It states what the skill does but lacks any "Use when..." clause or equivalent explicit trigger guidance, so completeness is capped at 2 per the rubric guideline.	2 / 3
Trigger Term Quality	Relevant terms like "Design Doc", "compliance", and "security validation" appear, but common natural variations a user would say (e.g. "review", "check", "audit") are missing.	2 / 3
Distinctiveness Conflict Risk	The Design-Doc-compliance niche is somewhat specific, but "compliance and security validation" could still overlap with generic code-review or security-review skills.	2 / 3
	Total	8 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: shinpr/claude-code-workflows
Commit: 66e3b29

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.