CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

apex-plan

Plan and scope a project — discovery, challenge assumptions, present S/M/L options with token and cost estimates. Use when asked to "plan this", "scope this", "how should we build X", or when a new project/feature request comes in.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/ai-agency/tonone/skills/apex-plan/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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.

A concise, well-structured orchestration skill with concrete output templates and clear sequencing including a user-choice gate and a review/escalation checkpoint. Its main defect is the dependency on docs/output-kit.md (and /atlas-report), neither of which exists in the bundle, leaving the promised output format undefined.

Suggestions

Inline the essential output-format rules from docs/output-kit.md (box-drawing skeleton, severity indicators) into SKILL.md, or actually ship docs/output-kit.md in the bundle so the reference resolves.

Add brief error-recovery guidance for the dispatch phase: what to do when a specialist fails, badly exceeds its token budget, or returns output conflicting with another specialist.

Remove the duplicated 40-line CLI budget mention and the redundant 'Lead with your recommendation' line, since the template already encodes both.

DimensionReasoningScore

Conciseness

The body is lean and operational — the 12-specialist roster and challenge-assumption questions are genuinely unknown information Claude needs — but the 40-line CLI budget is stated twice and the recommendation guidance ("Lead with your recommendation and why") duplicates the template line "My recommendation: [S/M/L] because [reason]".

4 / 5

Actionability

Provides copy-paste-ready skeletons for the S/M/L options and the usage receipt, plus concrete directives ("Run independent specialists in parallel", "invoke /atlas-report"). Not a 5 because the critical output-format rules are delegated to docs/output-kit.md, which is not present in the bundle, and /atlas-report is assumed to exist externally.

4 / 5

Workflow Clarity

Seven clearly sequenced steps with an explicit wait-gate ("Do not proceed until they choose S, M, or L") and a review checkpoint with escalation rules in step 6. Not a 5 because there is no error-recovery guidance for specialist failures or badly exceeded estimates; the only conditional handling is the 40-line overflow branch in step 7.

4 / 5

Progressive Disclosure

The body itself is well-sectioned with templates inline, but the one external reference — "Follow the output format defined in docs/output-kit.md" — is clearly signaled yet resolves to nothing: the bundle contains no docs/ (or any references/scripts/assets) directory, so the skill is not self-contained and the referenced material is unavailable.

3 / 5

Total

15

/

20

Passed

Description

83%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.

A strong description in third-person voice that clearly states what the skill does and gives explicit, natural trigger phrases. Its only weaknesses are minor: incomplete action coverage in the 'what' and a slightly broad new-project trigger that could overlap with sibling planning skills.

DimensionReasoningScore

Specificity

Names several concrete actions — "discovery, challenge assumptions, present S/M/L options with token and cost estimates" — but omits downstream behaviors (dispatching specialists, delivering reports), so coverage has minor gaps rather than being comprehensive.

4 / 5

Completeness

Explicitly answers both: what ("Plan and scope a project — discovery, challenge assumptions, present S/M/L options with token and cost estimates") and when ("Use when asked to 'plan this', 'scope this', 'how should we build X'...") with concrete trigger phrases. Not a 4 because the 'when' clause is fully explicit, not merely present.

5 / 5

Trigger Term Quality

Includes natural phrases users would actually say — "plan this", "scope this", "how should we build X" — plus the scenario "when a new project/feature request comes in", but misses common synonyms like "estimate this", "proposal", or "feasibility".

4 / 5

Distinctiveness Conflict Risk

The S/M/L-options-with-token-and-cost-estimates framing carves a fairly distinct niche, but the trigger "when a new project/feature request comes in" is broad enough to overlap with general planning or architecture skills.

4 / 5

Total

17

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository

jeremylongshore/tons-of-skills-marketplace

Path

plugins/ai-agency/tonone/skills/apex-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.