CtrlK
BlogDocsLog inGet started
Tessl Logo

recipe-fullstack-implement

Orchestrate full-cycle implementation across backend and frontend layers

56

Quality

63%

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

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 dense, highly actionable orchestration recipe with clear workflows and validation loops, though it depends heavily on external-skill references rather than self-contained bundled materials.

Suggestions

Bundle the referenced monorepo-flow.md under references/ so the skill is self-contained rather than depending on an external skill's files.

Add a brief inline fallback summary of the Fullstack Flow steps so the orchestrator can proceed even if the external reference is unavailable.

Confirm the referenced subagents-orchestration-guide and llm-friendly-context skills are declared dependencies so missing references fail fast with a clear message.

DimensionReasoningScore

Conciseness

The body is lean and directive with no concept explanations Claude already knows; every line is an actionable instruction that earns its place.

3 / 3

Actionability

It provides concrete executable guidance: filename-pattern routing rules, exact subagent_type values, status fields to check, and a specific command ('git diff --name-only main...HEAD').

3 / 3

Workflow Clarity

Sequenced decision flow, mandatory checklists, explicit stop points, and validation feedback loops (quality-fixer before commit; verification fix-cycle repeated until pass or blocked) with clear escalation paths.

3 / 3

Progressive Disclosure

Content is well-organized into sections and signals external references (monorepo-flow.md, subagents-orchestration-guide), but those reference files are not present in this skill's bundle, so navigation is not self-contained.

2 / 3

Total

11

/

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 communicates the skill's high-level purpose but lacks concrete actions, natural trigger terms, and any 'when to use' guidance, making it a generic orchestrator label rather than a precise invocation signal.

Suggestions

Add concrete actions the skill performs, e.g. '...requirements analysis, design, planning, implementation, and QA across backend and frontend layers'.

Append a 'Use when...' clause with natural user phrasing such as 'Use when the user asks to implement a fullstack feature spanning backend and frontend'.

Include natural trigger terms users would say (e.g. 'fullstack feature', 'backend and frontend implementation') to improve distinctiveness.

DimensionReasoningScore

Specificity

Names the fullstack domain and the high-level action 'Orchestrate full-cycle implementation across backend and frontend layers', but lists no concrete discrete actions, sitting between vague and comprehensive.

2 / 3

Completeness

It states what the skill does but provides no 'when to use it' trigger guidance, capping completeness at 2 per the judging guidelines.

2 / 3

Trigger Term Quality

The description contains only generic technical terms ('orchestrate', 'implementation', 'backend and frontend') with no natural phrases a user would actually say to invoke this skill.

1 / 3

Distinctiveness Conflict Risk

The wording is somewhat specific to fullstack orchestration but the generic orchestrator framing could still overlap with other orchestration skills.

2 / 3

Total

7

/

12

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.

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