CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

recipe-front-plan

Create frontend work plan from design document and obtain plan approval

Quality

77%

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

92%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 written orchestration recipe: every step is executable with exact agent types, fields, and templates, and the workflow includes explicit review-resolution and user-feedback loops. The only weakness is minor token overhead from cross-skill bookkeeping and a few redundant framing lines.

DimensionReasoningScore

Conciseness

The body is dense procedural instruction that assumes competence, with only minor trimmable overhead such as 'Dedicated to the frontend planning phase', repeated citations of subagents-orchestration-guide, and the opaque 'HC-06' cross-reference.

4 / 5

Actionability

Every step gives fully executable guidance: exact subagent_type strings, field-by-field prompt construction rules, explicit parameter conditions, and a copy-paste completion response template. Per the code_vs_instruction note, absence of code is not penalized for an instruction-only skill with this level of concreteness.

5 / 5

Workflow Clarity

A five-step sequence with explicit validation checkpoints and feedback loops: the mandatory Review Resolution Gate with correction re-review through convergence, re-invoking work-planner verbatim on user change requests, and defined fallback conditions. This matches the anchor for clear sequence with explicit validation and error-recovery loops.

5 / 5

Progressive Disclosure

No bundle files exist, and none are needed: the ~90-line body is appropriately self-contained with well-organized sections and a single clearly signaled one-level reference (references/review-resolution.md from the loaded subagents-orchestration-guide skill). Nothing is inlined that belongs in a separate file.

5 / 5

Total

19

/

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 short, third-person, and states two concrete actions in a distinct niche, but it omits any 'when to use' trigger guidance and misses natural keyword variations. As written it reads more as a phase label than a complete trigger description, though disable-model-invocation limits the practical impact.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to plan frontend implementation from an approved design document' (disable-model-invocation means it is user-invoked, but explicit guidance still helps the user pick the right command).

Enumerate the concrete deliverables to lift specificity, e.g. 'Create a frontend work plan from a design document, generate acceptance-test skeletons, and obtain plan approval'.

Include natural keyword variations such as 'design doc', 'frontend planning', and 'work plan review' to improve trigger term coverage.

DimensionReasoningScore

Specificity

Names the frontend planning domain plus two concrete actions ('Create frontend work plan from design document and obtain plan approval'), but coverage stops at two actions rather than the several listed at anchor 4.

3 / 5

Completeness

The 'what' is clear (create a work plan from a design document, obtain approval), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

'frontend', 'work plan', 'design document', and 'plan approval' are relevant keywords, but common natural variations (e.g. 'design doc', 'planning phase') are missing, matching the some-keywords-but-gaps anchor.

3 / 5

Distinctiveness Conflict Risk

'frontend work plan from design document' carves a mostly distinct niche with minor overlap risk against sibling planning/review skills; it lacks the distinct trigger phrases needed for anchor 5.

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

skills/recipe-front-plan/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.