dev

Extreme lightweight end-to-end development workflow with requirements clarification, intelligent backend selection, parallel codeagent execution, and mandatory 90% test coverage

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./skills/dev/SKILL.md

Quality

Content

77%

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

The skill body delivers a clearly sequenced, actionable workflow with strong executable templates and validation checkpoints, but it is verbose from constraint repetition and monolithic with no progressive disclosure into reference files.

Suggestions

Remove the duplicated CRITICAL CONSTRAINTS rules that are already stated in each step, or keep them only in the per-step context, to cut redundant tokens.

Move the detailed analysis-output structure and the --parallel config template into reference files under references/ and link to them one level deep.

Trim the 'What the AI backend does in Analysis Mode' section, which describes exploration Claude already knows how to perform.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient procedural instruction, but the CRITICAL CONSTRAINTS block repeats rules that reappear verbatim inside each step (e.g. 'NEVER use Edit/Write', 'MUST use AskUserQuestion'), and the 'What the AI backend does in Analysis Mode' section restates exploration Claude already knows how to do.	2 / 3
Actionability	It provides concrete, executable bash invocations for codeagent-wrapper analysis and a complete --parallel task-submission template with ---TASK---/---CONTENT--- structure, routing rules, and deliverables, making the guidance copy-paste ready once per-task fields are filled.	3 / 3
Workflow Clarity	The 7-step sequence (Step 0-6) is clearly ordered with explicit validation checkpoints: mandatory user confirmation in Step 3, coverage validation with a max-2-round retry loop in Step 5, and a dedicated error-handling section with feedback loops.	3 / 3
Progressive Disclosure	The document is well-sectioned with headers but is a monolithic ~210-line file with no bundle files in references/scripts/assets; content that could be split out (the analysis output template, backend routing table, parallel config format) is inline rather than one level deep in referenced files.	2 / 3
	Total	10 / 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 communicates a concrete multi-stage development workflow but relies on buzzword padding and omits any explicit 'Use when' trigger guidance, leaving the 'when' half of completeness unaddressed.

Suggestions

Drop fluff like 'Extreme lightweight end-to-end' and 'intelligent' and lead with concrete actions only.

Add an explicit trigger clause, e.g. 'Use when the user asks to implement a feature end-to-end with tests, or requests a structured development workflow with coverage validation.'

Include natural user phrasings such as 'build a feature', 'implement with tests', or 'develop with coverage' to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	It lists several concrete workflow stages ('requirements clarification', 'backend selection', 'parallel codeagent execution', '90% test coverage'), but pads them with fluff ('Extreme lightweight end-to-end', 'intelligent backend selection') and an abstract qualifier that keeps it below the clean multi-action anchor.	2 / 3
Completeness	It states what the skill does (the staged workflow) but contains no 'Use when...' clause or equivalent explicit trigger guidance, which per the rubric caps completeness at 2.	2 / 3
Trigger Term Quality	It includes a few relevant terms ('development workflow', 'test coverage'), but 'codeagent execution' is jargon and common natural variations a user would say (e.g. 'implement a feature', 'build with tests') are missing.	2 / 3
Distinctiveness Conflict Risk	The codeagent-wrapper/90% coverage niche is fairly specific, but with no explicit triggers and broad 'end-to-end development' framing it could still overlap with general development-planning 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: stellarlinkco/myclaude
Path: skills/dev/SKILL.md
Commit: f2e75c1

Reviewed: about 9 hours 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.