CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

deepen-plan

This skill should be used when deepening a plan with parallel research agents for each section.

51

Quality

64%

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/skills/03-plan/deepen-plan/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

56%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 delivers genuinely actionable orchestration guidance with a clear nine-step workflow, concrete commands, templates, and a strong worked example. Its main weaknesses are heavy repetition that inflates token cost and a monolithic structure with no reference files, so a ~530-line body carries roughly the same content a much leaner SKILL.md plus a few reference files would hold.

Suggestions

Cut the repeated parallelism emphasis to a single statement per section — the 'spawn in PARALLEL / no limit / 10-40 agents is fine' guidance appears nearly verbatim in sections 2, 3, 4, and 5 — and trim the 60-line Example Enhancement to one short section snippet.

Move the sub-agent prompt templates, learnings directory layout, and full example enhancement into a references/ file (e.g., references/templates.md) and point to them from the body, giving the SKILL.md a lean overview role.

Add a validate-fail-retry loop around the Quality Checks step (e.g., 'If any check fails, fix the plan file and re-run the checklist before presenting post-enhancement options') to earn the top workflow-clarity anchor.

DimensionReasoningScore

Conciseness

The 530-line body is heavily padded: the parallel-spawn instruction is restated many times ('Spawn ALL skill sub-agents in PARALLEL', 'No limit on skill sub-agents', '10, 20, 30 skill sub-agents is fine' vs '20, 30, 40 parallel agents is fine'), with pervasive caps/CRITICAL emphasis repeating the same point. It avoids explaining known concepts, so it is not anchor 1, but it clearly matches 'Noticeably verbose; several unnecessary explanations or padded sections'.

2 / 5

Actionability

Concrete, runnable bash discovery commands (ls/find/cat paths), copy-ready sub-agent prompt templates, an explicit enhancement output format, and a full before/after example cover the common cases. Minor gaps keep it below anchor 5: templates contain unfilled placeholders ('[skill-path]', '[relevant plan section]') and some steps are abstract ('prioritize by impact', 'flag conflicting advice').

4 / 5

Workflow Clarity

The nine main tasks are clearly numbered and sequenced, with real checkpoints: a gate on obtaining a valid plan path ('Do not proceed until you have a valid plan file path'), waiting for all agents before synthesis, dedup/prioritization rules, and a Quality Checks checklist plus a revert option guarding the in-place plan overwrite. It falls short of anchor 5 because the checks are a one-shot checklist without an explicit validate-fail-fix-retry feedback loop.

4 / 5

Progressive Disclosure

Section headers are clear and well-ordered, but the skill is a monolithic single file with no bundle references at all, while content that clearly belongs in separate files is inlined: the ~60-line Example Enhancement, the sub-agent prompt templates, and the learnings directory documentation. This matches 'Some structure but... content that should be separate is inline' rather than anchor 4, since nothing is split out.

3 / 5

Total

13

/

20

Passed

Description

57%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 both a what and a when clause and occupies a distinct niche, but it is thin: the only concrete detail is the parallel-research-agent mechanism, while the actual capability (merging research, best practices, and code examples into plan sections) and natural trigger synonyms are left unstated. One tight sentence listing concrete actions would lift specificity and trigger coverage substantially.

Suggestions

State the concrete outcomes in the description, e.g., 'Enhances each section of an existing plan with researched best practices, code examples, performance considerations, and edge cases by spawning parallel research agents per section.'

Add natural trigger synonyms so users can phrase the request differently: 'Use when the user asks to deepen, enhance, expand, or add research to an existing plan' (e.g., one from wf-shape).

Clarify the handoff boundary with sibling skills (wf-shape creates the plan, wf-review/wf-develop consume it) to reduce overlap risk with the other plan-workflow skills.

DimensionReasoningScore

Specificity

The description names the domain ("deepening a plan") and one mechanism ("parallel research agents for each section"), but "deepening" is a generic verb and no concrete outcome actions (e.g., enhancing sections with best practices, code examples, edge cases) are stated. This matches the anchor 'Names the domain but actions are minimal or generic' better than anchor 3, which requires 1-2 concrete actions.

2 / 5

Completeness

Both what ("deepening a plan with parallel research agents") and when ("should be used when deepening a plan") are explicitly present, satisfying the 'Use when...' requirement. It falls short of anchor 5 because the 'what' is not fully concrete and the 'when' is circular, restating the skill name rather than giving concrete trigger phrases.

4 / 5

Trigger Term Quality

"deepening a plan" and "research agents" are relevant keywords a workflow user might say, but common variations and synonyms ("enhance plan", "improve plan", "expand plan", "add research to plan") are missing, matching the anchor 'Some relevant keywords but missing common variations or synonyms'.

3 / 5

Distinctiveness Conflict Risk

The plan-deepening niche is mostly distinct with its own trigger ("deepen"), but there is minor overlap risk with closely related sibling plan skills (wf-shape, wf-review, wf-develop) that the description does not disambiguate, matching anchor 4 rather than the clear-niche anchor 5.

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

skill_md_line_count

SKILL.md is long (533 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository

marchatton/agent-skills

Path

.agents/skills/03-plan/deepen-plan/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.