concise-planning
Use when a user asks for a plan for a coding task, to generate a clear, actionable, and atomic checklist.
Install with Tessl CLI
npx tessl i github:sickn33/antigravity-awesome-skills --skill concise-planning82
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
50%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 correctly leads with a 'Use when' clause but is light on specifics about what the skill actually does beyond generating a checklist. It relies on adjectives (clear, actionable, atomic) rather than concrete capabilities, and misses natural trigger terms users would commonly use when seeking planning help.
Suggestions
Add specific capabilities beyond 'generate checklist' - e.g., 'breaks down complex features into discrete implementation steps, identifies dependencies, estimates scope'
Expand trigger terms to include natural phrases like 'break down', 'implementation steps', 'how should I approach', 'task breakdown', 'todo list for coding'
Clarify the output format - e.g., 'produces numbered checklists with acceptance criteria for each step'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (coding task planning) and one action (generate checklist), but lacks comprehensive concrete actions. 'Clear, actionable, and atomic' are quality descriptors rather than specific capabilities. | 2 / 3 |
Completeness | Has a 'Use when' clause addressing when to trigger, but the 'what' is weak - only mentions generating a checklist without explaining what makes it valuable or what the output looks like beyond adjectives. | 2 / 3 |
Trigger Term Quality | Includes 'plan' and 'coding task' which are relevant, but misses common variations users might say like 'break down', 'steps', 'todo', 'implementation plan', 'task list', or 'how to approach'. | 2 / 3 |
Distinctiveness Conflict Risk | Somewhat specific to coding task planning, but could overlap with general task management skills, project planning skills, or coding assistance skills. 'Coding task' and 'checklist' provide some distinction but not strong boundaries. | 2 / 3 |
Total | 8 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted skill that efficiently teaches Claude how to generate actionable plans. It's concise, provides a concrete template, has a clear workflow with validation steps, and is appropriately structured for its scope. The checklist guidelines add valuable specificity without bloat.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, with no unnecessary explanations of concepts Claude already knows. Every section serves a clear purpose and the template is minimal yet complete. | 3 / 3 |
Actionability | Provides a concrete, copy-paste ready template with specific structure (Approach, Scope, Action Items, Validation). The checklist guidelines give clear, actionable rules (verb-first, atomic, concrete file names). | 3 / 3 |
Workflow Clarity | Clear 3-step workflow (Scan Context → Minimal Interaction → Generate Plan) with explicit validation requirement in the plan template. The sequence is unambiguous and includes a validation checkpoint. | 3 / 3 |
Progressive Disclosure | For a simple, single-purpose skill under 50 lines, the content is well-organized with clear sections (Goal, Workflow, Template, Guidelines). No external references needed and structure is easy to navigate. | 3 / 3 |
Total | 12 / 12 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
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 12 / 16 Passed | |
- 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.