CtrlK
BlogDocsLog inGet started
Tessl Logo

planning

Create and manage persistent markdown planning files for structured task execution. Use when the user asks to "create a plan", "track progress", "start a research project", or when a task requires more than 5 tool calls and needs structured phase tracking to stay focused and avoid goal drift.

66

Quality

79%

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 ./cli-tool/components/skills/ai-maestro/planning/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 a well-organized, actionable planning skill with concrete templates, rules, and recovery protocols. The main weaknesses are minor promotional padding and the absence of explicit templates for two of the three planning files.

Suggestions

Add copy-paste-ready markdown templates for findings.md and progress.md to match the task_plan.md example and close the actionability gap.

Trim the marketing-flavored intro sentence and the "Full AI Maestro Experience" section to improve token efficiency.

Add a short numbered creation-order workflow (e.g., 1. create task_plan.md, 2. create findings.md during research, 3. maintain progress.md throughout) to make the sequence explicit.

DimensionReasoningScore

Conciseness

The body is well-structured and mostly lean, but the opening ("Solve the execution problem... so you never lose context") and the closing "Full AI Maestro Experience" section carry mild promotional padding that could be trimmed.

4 / 5

Actionability

Provides an executable mkdir command and a copy-paste-ready task_plan.md template plus concrete rules and protocols, but templates for findings.md and progress.md are only described in the table rather than given, leaving a minor gap.

4 / 5

Workflow Clarity

The 6 Rules, 3-Strike Protocol, and 5-Question Reboot provide genuine feedback loops and recovery checkpoints, but there is no crisp numbered sequence for creating and updating the three files in order.

4 / 5

Progressive Disclosure

The ~80-line body is self-contained with clear section headers and no nested references, but it slightly exceeds the simple-skill line budget and contains minor marketing content, keeping it just below a 5.

4 / 5

Total

16

/

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.

The description is strong: it clearly answers both what and when with concrete, natural-language trigger phrases in proper third-person voice. Its main limitation is that the action list, while specific, is not exhaustive and lacks synonym coverage for triggers.

Suggestions

Add a few synonym trigger terms (e.g., "make a TODO", "organize a project", "plan phases") to broaden natural keyword coverage toward a 5 on trigger term quality.

Expand the action list slightly (e.g., "update, review, and archive planning files") to make capability coverage more comprehensive.

DimensionReasoningScore

Specificity

Names the domain ("persistent markdown planning files for structured task execution") with several concrete actions—create, manage, track progress, structured phase tracking—but coverage is not fully comprehensive, so it sits just below a 5.

4 / 5

Completeness

Explicitly states what it does ("Create and manage persistent markdown planning files...") and when to use it ("Use when the user asks to...") with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Includes natural phrases users would actually say ("create a plan", "track progress", "start a research project") plus a quantitative trigger (">5 tool calls"), but lacks common synonyms and variations that would push it to 5.

4 / 5

Distinctiveness Conflict Risk

The persistent-markdown-planning niche with quantitative and phrase triggers is mostly distinct, but the broad concept of task planning carries minor overlap risk with other task-management skills.

4 / 5

Total

17

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
davila7/claude-code-templates
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.