CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

planning-architect

Comprehensive skill development planning. Analyzes requirements, chooses organizational patterns (workflow/task/reference/capabilities), defines structure, estimates complexity, identifies dependencies, and creates detailed implementation plan. Use when planning new skills, converting documentation to skills, or architecting complex skill systems.

Quality

77%

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 ./.claude/skills/planning-architect/SKILL.md

The canonical home for this skill is planning-architect in fernandezbaptiste/Skrillz

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 teaches a coherent, actionable six-step planning workflow with good per-step examples and an estimation formula, but it badly violates its own progressive-disclosure guidance: at 4,800+ words it duplicates its core content across four summary sections and includes three broken bundle references plus internally inconsistent step naming. Consolidating the redundant sections and fixing the reference links would lift both conciseness and progressive disclosure.

Suggestions

Consolidate the four restatements of the six-step process (Quick Start, Planning Output, Success Criteria, Quick Reference) into a single brief summary, and move the duplicated pattern tables and decision tree into references/pattern-selection-guide.md to bring SKILL.md under its own 5,000-word target.

Fix the broken bundle references: create templates/skill-plan-template.md or remove the link, and correct 'references/content-specification-guide.md' and 'references/complexity-assessment-guide.md' to point at files that actually exist (e.g., complexity-estimation-guide.md).

Reconcile the Quick Reference table and 'For More Information' section with the actual six workflow steps, which currently use different step names and numbering.

DimensionReasoningScore

Conciseness

At 4,807 words / 1,329 lines, the body restates its core content four times: 'Quick Start: Plan a Skill in 30 Minutes', 'Planning Output', 'Success Criteria', and 'Quick Reference' each re-summarize the same six steps and outputs, and the pattern-selection decision tree appears in full both in Step 2 and again in 'Quick Reference'. These are several unnecessary, padded sections — noticeably verbose, not merely 'some' over-explanation.

2 / 5

Actionability

Guidance is mostly executable: a concrete pattern decision tree, an estimation formula with three worked numeric examples, complete file-structure examples, and runnable commands ('python scripts/plan-skill.py --interactive'). Minor gaps remain, e.g. final plan output is only described abstractly and the promised structured-output template link is broken.

4 / 5

Workflow Clarity

The six steps are clearly sequenced, each with Objective/Process/Output/Example, and Step 6 defines validation criteria and test cases — most checkpoints are present. However, the 'Quick Reference' table lists different step names ('4. Plan Content', '6. Create Plan Document') than the actual workflow steps ('4. Estimate Complexity', '6. Define Validation Criteria'), and 'For More Information' misnumbers the steps, creating internal inconsistency that keeps it below a 5.

4 / 5

Progressive Disclosure

References are well-signaled with descriptive link text and four real reference files plus a script exist, but three referenced paths are broken — 'templates/skill-plan-template.md' (no templates/ directory), 'references/content-specification-guide.md', and 'references/complexity-assessment-guide.md' (the actual file is complexity-estimation-guide.md) — and substantial duplicated summary content (Quick Reference, Success Criteria) is inlined in SKILL.md rather than moved to references. Broken navigation links and inlined duplicate content are more than the 'minor organization gaps' of a 4.

3 / 5

Total

13

/

20

Passed

Description

92%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: it states concrete capabilities in third person, names the organizational patterns it chooses among, and provides an explicit 'Use when' clause with three concrete trigger scenarios. The only gap is modest synonym coverage for natural trigger phrasings like 'create/build a skill'.

DimensionReasoningScore

Specificity

The description lists six concrete actions — 'Analyzes requirements, chooses organizational patterns (workflow/task/reference/capabilities), defines structure, estimates complexity, identifies dependencies, and creates detailed implementation plan' — comprehensively covering the planning pipeline with no coverage gaps, matching the comprehensive-actions anchor rather than the 'minor gaps' anchor at 4.

5 / 5

Completeness

It explicitly answers 'what' with the six-action list and 'when' with the concrete 'Use when planning new skills, converting documentation to skills, or architecting complex skill systems' trigger clause, matching the anchor-5 pattern of clear what plus explicit when with concrete trigger phrases.

5 / 5

Trigger Term Quality

'planning new skills', 'converting documentation to skills', and 'architecting complex skill systems' are natural phrases users would say, but common variations such as 'create a skill', 'build a skill', 'design a skill', or 'skill structure' are absent — good keyword coverage with a few natural terms missing, not the comprehensive synonym coverage of the top anchor.

4 / 5

Distinctiveness Conflict Risk

The description occupies a clear niche (Claude Code skill development planning) with triggers ('planning new skills', 'converting documentation to skills') unlikely to fire for unrelated skills — minimal conflict risk, matching the top anchor.

5 / 5

Total

19

/

20

Passed

Validation

75%

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

Validation — 12 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

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

Warning

allowed_tools_field

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

Warning

relative_links

Relative link issues: 1 missing

Warning

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

12

/

16

Passed

Repository

fernandezbaptiste/Skrillz

Path

.claude/skills/planning-architect/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.