CtrlK
BlogDocsLog inGet started
Tessl Logo

recipe-front-plan

Create frontend work plan from design document and obtain plan approval

59

Quality

67%

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

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is an efficient, highly actionable orchestrator skill with a clearly sequenced five-step workflow, explicit review/revision feedback loops, and well-signaled single-level references to companion skills. It respects token budget while remaining concrete.

DimensionReasoningScore

Conciseness

The body is lean and directive throughout, assuming Claude's competence and avoiding explanations of concepts Claude already knows; nearly every line is an actionable instruction that earns its place.

3 / 3

Actionability

It provides concrete, copy-paste-ready orchestration guidance — explicit subagent_type values, exact prompt strings, and precise branching rules for lane status — leaving no ambiguity about what to invoke and how.

3 / 3

Workflow Clarity

A clear five-step sequence is given with explicit validation checkpoints and a real feedback loop in Step 4 (re-invoke work-planner on needs_revision until approved, with escalation on repeated blocking findings or rejection).

3 / 3

Progressive Disclosure

The skill is self-contained with well-organized sections and only one-level-deep, clearly signaled references to companion skills (e.g., "see subagents-orchestration-guide skill"); no nested multi-level reference chain exists.

3 / 3

Total

12

/

12

Passed

Description

35%

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 two concrete actions but lacks any natural trigger terms or an explicit "when to use" clause, capping completeness and trigger-term quality. It reads as procedural jargon rather than user-facing language.

Suggestions

Add an explicit "Use when..." clause naming natural user triggers (e.g., "Use when planning frontend implementation from a design doc, creating a frontend work plan, or when a design document needs to be turned into an approved implementation plan").

Include common user-facing phrasings like "frontend plan", "design doc", or "implementation plan" instead of only procedural artifacts like "plan approval".

Sharpen the niche phrasing to distinguish it from general or backend work-planning skills.

DimensionReasoningScore

Specificity

Names two concrete actions tied to a domain ("Create frontend work plan from design document" and "obtain plan approval"), but does not list multiple specific concrete actions to reach the comprehensive bar.

2 / 3

Completeness

It states what the skill does but provides no "when" guidance; per the judging guidelines a missing "Use when..." clause caps completeness at 2.

2 / 3

Trigger Term Quality

The phrasing uses procedural jargon ("work plan", "design document", "plan approval") rather than natural keywords a user would actually say, and includes no common variations or trigger phrasings.

1 / 3

Distinctiveness Conflict Risk

The frontend-planning niche is reasonably specific, but "work plan" / "plan approval" terminology could overlap with general or backend planning skills, so it is not a fully distinct trigger set.

2 / 3

Total

7

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
shinpr/claude-code-workflows
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.