CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

61

Quality

74%

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 content is well-structured and actionable as a planning methodology, but it is materially too long and self-repetitive, and it violates its own progressive-disclosure guidance both by inlining reference-grade material and by shipping broken bundle links. Tightening redundancy and fixing the missing files would materially raise the score.

Suggestions

Collapse the duplicated material: keep the detailed six-step workflow once and reduce Quick Start, the three Examples, and the Quick Reference section to brief pointers rather than re-deriving the decision tree, complexity table, and pattern summaries a second time.

Fix broken bundle links: either create references/complexity-assessment-guide.md, references/content-specification-guide.md, and templates/skill-plan-template.md, or update the "For More Information" and Planning Output links to point at the four reference files that actually exist.

Move the full Quick Reference tables and the three end-to-end examples into references/ so SKILL.md stays within the <1,200-line ideal it prescribes, leaving only the overview, step pointers, and quick-start essentials inline.

DimensionReasoningScore

Conciseness

The ~1,330-line body restates the same material repeatedly — the 6-step workflow appears fully in Planning Workflow, again in Quick Start, again across three worked Examples, and again in the Quick Reference section (including a second copy of the decision tree and complexity tables) — well beyond the "some unnecessary explanation" of a 3.

2 / 5

Actionability

Provides concrete planning artifacts — a pattern-selection decision tree, a directory-structure template, an estimation formula with three worked examples, a dependency-documentation format, and real script commands — with only minor gaps where sections default to abstract prompting questions.

4 / 5

Workflow Clarity

The six steps are clearly sequenced with per-step Objectives, Outputs, and Examples plus a dedicated validation step with checklists, but validation is concentrated at the end rather than interleaved as explicit go/no-go gates between steps.

4 / 5

Progressive Disclosure

References are well-signaled with descriptive link text and four reference files plus plan-skill.py exist, but the SKILL.md itself is bloated with inline content (full Quick Reference, three complete examples) that the skill's own rules say belongs in references, and links to complexity-assessment-guide.md, content-specification-guide.md, and templates/skill-plan-template.md point at files/directories that do not exist.

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.

The description is strong: third-person, specific, and complete with an explicit "Use when" clause covering concrete trigger scenarios. Its only minor weakness is trigger-term breadth, where a few additional natural synonyms would round out coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Analyzes requirements, chooses organizational patterns (workflow/task/reference/capabilities), defines structure, estimates complexity, identifies dependencies, and creates detailed implementation plan" — giving comprehensive coverage of the planning workflow.

5 / 5

Completeness

Explicitly answers both what (the enumerated planning actions) and when ("Use when planning new skills, converting documentation to skills, or architecting complex skill systems") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural trigger phrases ("planning new skills", "converting documentation to skills", "architecting complex skill systems") but stops short of comprehensive synonym coverage, so it fits the "good coverage, a few terms missing" anchor rather than a 5.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche — upstream skill planning/architecture — with distinct triggers that are unlikely to fire for implementation or research skills, keeping conflict risk minimal.

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.

Validation12 / 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
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.