CtrlK
BlogDocsLog inGet started
Tessl Logo

subagent-driven-development

Use when executing implementation plans with independent tasks in the current session

53

Quality

59%

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/subagent-driven-development/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 content excels at workflow clarity with explicit checkpoints, feedback loops, and a concrete example, and is largely actionable. The main weaknesses are moderate verbosity in the Advantages/Red Flags sections and broken references to missing prompt-template bundle files.

Suggestions

Add the three referenced prompt-template files (implementer-prompt.md, spec-reviewer-prompt.md, code-quality-reviewer-prompt.md) to a bundle directory so the signaled references resolve.

Trim the Advantages section, which restates the core principle and process steps already covered above.

Condense the Red Flags list by merging near-duplicate entries (e.g. the repeated review-loop guidance).

DimensionReasoningScore

Conciseness

The body is mostly efficient and free of explanations of concepts Claude already knows, but the Advantages and Red Flags sections restate points from the process and the example workflow is lengthy, so it could be tightened.

3 / 5

Actionability

Concrete guidance abounds — explicit resume instructions ("resume: <agent-id>"), a full dialogue example, and named prompt templates — but the executable prompt templates themselves live in external files rather than inline.

4 / 5

Workflow Clarity

Two dot graphs sequence the full process with explicit validation checkpoints (spec review then quality review) and feedback loops ("Repeat until approved", "Don't skip the re-review"), plus a Red Flags checklist for error recovery.

5 / 5

Progressive Disclosure

The body is well sectioned and the three prompt-template references are clearly signaled one level deep, but the referenced files (implementer-prompt.md, spec-reviewer-prompt.md, code-quality-reviewer-prompt.md) do not exist in any bundle directory, breaking navigation.

3 / 5

Total

15

/

20

Passed

Description

48%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 has a clear trigger clause and is reasonably distinct, but it is vague on what the skill actually does — the subagent-driven, two-stage-review mechanism is entirely absent. Specificity and completeness are the weakest dimensions.

Suggestions

Add the distinctive mechanism to the description, e.g. "Dispatches a fresh subagent per task with spec-compliance then code-quality review after each."

Include a couple of natural trigger synonyms such as "execute a plan" or "run plan tasks" alongside "implementation plans".

Make the "what" explicit so the description conveys both the action and the trigger, rather than only the trigger.

DimensionReasoningScore

Specificity

The phrase "executing implementation plans with independent tasks" names the domain but offers only one generic action (executing plans) and omits the skill's actual mechanism (subagent dispatch, two-stage review).

2 / 5

Completeness

It has a clear "when" ("Use when executing implementation plans with independent tasks in the current session") but the "what" is generic — it never mentions subagents or the two-stage review that define the skill.

3 / 5

Trigger Term Quality

"implementation plans" and "independent tasks" are reasonably natural phrases a user might say, but common synonyms like "execute a plan" or "run tasks" are missing.

3 / 5

Distinctiveness Conflict Risk

"independent tasks" and "in the current session" distinguish it from the related executing-plans skill, leaving only minor overlap risk with that closely related skill.

4 / 5

Total

12

/

20

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
roman01la/skills-agents
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.