CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

subagent-driven-development

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

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 ./.agents/harness/adapters/antigravity/skills/subagent-driven-development/SKILL.md

The canonical home for this skill is subagent-driven-development in phatblat/dotfiles

SKILL.md
Quality
Evals
Security

Quality

Content

65%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 an extremely lean redirect stub that delegates the entire skill to an external file outside the bundle. While maximally concise and unambiguous as a directive, it provides no substantive guidance, workflow, or in-bundle references, so the skill is not self-contained and its actual process cannot be evaluated or executed from what is written.

Suggestions

Make the skill self-contained: inline the core workflow steps into SKILL.md, or place the detailed guidance in a file within the bundle (e.g. references/process.md) so the delegated content is actually shipped with the skill.

Add a brief overview of the subagent-driven process (the steps and validation checkpoints) before delegating, so the body is more than a bare redirect and survives the target file being absent.

If the stub pattern is intentional, verify the shared path exists in target environments and note a fallback (e.g. 'if the path is missing, ask the user for the shared skill location') so the redirect cannot silently fail.

DimensionReasoningScore

Conciseness

The body is two lines total — a maintenance comment and "Load and follow the shared skill at `~/.agents/skills/subagent-driven-development/SKILL.md`" — with no padding and no explanation of concepts Claude already knows. Every token serves the redirect, matching 'Lean and efficient; every token earns its place'.

5 / 5

Actionability

The single directive is concrete and executable (an exact file path to load), but all substantive guidance is delegated outside the body — 'missing key details' fits, since nothing about how to execute plan tasks is written here. Not 4 because the gap is not minor (100% of the substance is external); not 2 because an exact load-and-follow path is more than a high-level hint.

3 / 5

Workflow Clarity

The redirect action itself is unambiguous, but the skill's described process ("executing implementation plans with independent tasks") is inherently multi-step, and the body contains none of its sequence or validation checkpoints — they are entirely delegated to an external file. The simple-skill exception does not apply because this is not a genuinely simple skill; it hides a complex workflow elsewhere.

3 / 5

Progressive Disclosure

The reference to the shared skill is clearly signaled and only one level deep, but the body is a bare redirect with no overview content, and the referenced path (`~/.agents/skills/...`) lives outside the bundle — no references/, scripts/, or assets/ directories exist. Not 5 because there is no 'clear overview', only indirection to an unverifiable target.

3 / 5

Total

14

/

20

Passed

Description

36%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 provides an explicit and reasonably specific 'Use when' trigger but completely omits what the skill does — no capabilities, actions, or mention of its distinctive mechanism (subagent-driven delegation). It reads as half a description: a clear trigger with missing substance, which caps both completeness and specificity.

Suggestions

Add a 'what' clause stating concrete capabilities, e.g. 'Delegates independent plan tasks to parallel subagents and integrates their results. Use when executing implementation plans with independent tasks in the current session.'

Include distinctive trigger keywords such as 'subagents', 'parallel task execution', or 'task delegation' so the description is distinguishable from generic plan-execution skills.

Add natural trigger variations users would actually say (e.g. 'run the tasks in this plan', 'execute the todos in parallel') to broaden keyword coverage.

DimensionReasoningScore

Specificity

The description names a domain ("executing implementation plans with independent tasks") but contains no capability verbs at all — nothing states what the skill does. This matches 'Names the domain but actions are minimal or generic'; not score 1 because the domain language is concrete rather than pure abstraction.

2 / 5

Completeness

Only the 'when' is present ("Use when executing implementation plans with independent tasks in the current session"); the 'what' is entirely absent. Anchor 2 explicitly covers 'only when is present without what'; not 3 because that anchor requires a clear 'what', which this lacks.

2 / 5

Trigger Term Quality

"executing implementation plans" and "independent tasks" are phrases a user might naturally say, but coverage stops there — no synonyms or variations such as 'run the plan', 'work through the tasks', or 'parallel execution'. Fits 'Some relevant keywords but missing common variations or synonyms'; not 4 because coverage is thin, not merely missing a few terms.

3 / 5

Distinctiveness Conflict Risk

"executing implementation plans with independent tasks" is somewhat specific but never mentions subagents, delegation, or parallelism — the skill's distinctive mechanism — so it could trigger for any generic plan-execution or implementation skill. Not 4 because the overlap risk is more than minor.

3 / 5

Total

10

/

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

phatblat/dotfiles

Path

.agents/harness/adapters/antigravity/skills/subagent-driven-development/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.