CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

recipe-fullstack-build

Execute materialized fullstack task files with layer-aware agent routing

Quality

68%

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

Quality

Content

70%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 strongly actionable orchestration recipe with an exceptionally clear, validated workflow: explicit sequencing, status-based branching, feedback loops, and a completion report contract. Its weaknesses are redundancy (routing and cycle rules stated twice) and a monolithic structure with no bundle files, relying on another skill's references for detail.

Suggestions

Remove the duplicated routing table and 4-step cycle statements — keep one authoritative Agent Routing Table section and have the Execution Protocol reference it, trimming roughly 10-15 lines.

Move the Task Generation Decision Flow and Completion Report Contract details into a reference file within this skill's bundle so SKILL.md stays a lean overview with one-level-deep, in-bundle references.

DimensionReasoningScore

Conciseness

The body is dense and imperative with no explanations of known concepts, but duplicates material: the agent routing table appears in both the Execution Protocol and the Agent Routing Table section, the 4-step cycle is stated twice, and the autonomous-mode batch-approval rule and Consumed Task Set pattern are each restated. This fits anchor 3 (mostly efficient but could be tightened) rather than 4, where only minor instances of over-explanation would remain.

3 / 5

Actionability

The guidance is largely executable: exact subagent_type values, a verbatim task-decomposer prompt, explicit field contracts (task_file, diffBase, mutationEvidence, qualityCommand), filename patterns, and a decision table. It falls short of anchor 5 because only the task-decomposer prompt is given verbatim — executor, reviewer, and quality-fixer prompts are described but not specified, and key detail is deferred to external skills.

4 / 5

Workflow Clarity

The multi-phase process is explicitly sequenced with transition conditions, a pre-execution checklist, a 4-step cycle branching on canonical status values, and thorough feedback loops (stub_detected returns to step 1, needs_revision routes corrections back, generation is re-verified, retained limitations get a final retry, deletion failure is handled). This matches anchor 5: clear sequence, explicit validation, error-recovery loops, and checklists; the batch-operation cap does not apply since validation is extensive.

5 / 5

Progressive Disclosure

Sections are well-organized and reads are clearly signaled, but the bundle contains no files at all — both referenced paths (references/monorepo-flow.md, references/review-resolution.md) belong to an external skill — and routing tables plus decision-flow detail that could live in a reference file are inlined in a ~150-line body. This fits anchor 3 (some structure, but content that should be separate is inline and references do not resolve within this bundle) rather than 4.

3 / 5

Total

15

/

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 states a concrete, niche capability but is a single terse clause: it lists only two actions, uses internal jargon ("materialized", "layer-aware") instead of natural user vocabulary, and entirely omits when the skill should be used. It is distinguishable from unrelated skills but under-communicates both scope and triggers.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to execute, run, or build a materialized work plan or backend/frontend task files under docs/plans/".

Enumerate the main actions so the scope is comprehensive: execute tasks, route backend/frontend executors and quality-fixers, run post-implementation code and security review, and report results.

Replace internal jargon ("materialized", "layer-aware") with natural phrasing users would actually say, such as "generated task files" and "backend/frontend agent routing".

DimensionReasoningScore

Specificity

"Execute materialized fullstack task files with layer-aware agent routing" names the domain and two actions (execute, route agents), but omits the quality-fix, commit, review, and cleanup activities the skill actually performs, matching the '1-2 concrete actions, not comprehensive' anchor. It is not score 2 because the actions are more concrete than generic domain naming, and not score 4 because several specific actions are not listed.

3 / 5

Completeness

The 'what' is clear (execute fullstack task files with layer-aware routing) but there is no 'Use when...' clause or any trigger guidance, capping completeness at 3 per the rubric guideline. It is not 4 because the 'when' is entirely absent rather than just imprecise, and not 2 because the 'what' is concrete.

3 / 5

Trigger Term Quality

"Execute", "fullstack", and "task files" are semi-natural terms, but "materialized" and "layer-aware agent routing" are internal jargon no user would say, and natural variations like "run tasks" or "work plan" are absent. This fits anchor 3 (some relevant keywords, missing common variations) rather than 4 (no good coverage of natural phrasing) or 2 (keywords are domain-relevant, not purely generic).

3 / 5

Distinctiveness Conflict Risk

"Materialized fullstack task files" defines a narrow niche unlikely to trigger unrelated skills, fitting anchor 4 (mostly distinct, minor overlap risk with closely related skills such as sibling dev-workflows recipes). It is not 5 because the description states no distinct trigger phrases that would fully separate it from related orchestration recipes.

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: 2 missing

Warning

Total

15

/

16

Passed

Repository

shinpr/claude-code-workflows

Path

skills/recipe-fullstack-build/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.