concise-planning

Use when a user asks for a plan for a coding task, to generate a clear, actionable, and atomic checklist.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/concise-planning/SKILL.md

Quality

Content

78%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 tight, actionable instruction skill: a clear three-step workflow, a concrete output template, and good section organization with no unnecessary reference structure. Its only flaws are minor boilerplate sections and the absence of a worked plan example.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence, but boilerplate like "This skill is applicable to execute the workflow or actions described in the overview" and generic Limitations lines could be trimmed, matching anchor 4 rather than 5.	4 / 5
Actionability	Concrete, executable guidance throughout: a fixed plan structure (Approach/Scope/Action Items/Validation), a copy-paste markdown template, and specific constraints ("at most 1-2 questions", "6-10 atomic, ordered tasks"); a worked input-to-output example is the missing piece, so anchor 4 rather than 5.	4 / 5
Workflow Clarity	The 3-step workflow (Scan Context, Minimal Interaction, Generate Plan) is clearly sequenced with unambiguous steps and a "Validation: At least one item for testing" requirement; validation targets the output plan rather than the process itself, matching anchor 4 rather than 5. This is not a destructive or batch operation, so no cap applies.	4 / 5
Progressive Disclosure	A simple single-purpose skill (~65 lines) with no bundle files: well-organized sections, nothing inlined that belongs in a separate file, and no nested references, satisfying the simple-skill condition for a top score.	5 / 5
	Total	17 / 20 Passed

Description

67%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 cleanly answers both what the skill does and when to use it, with a concise explicit trigger clause. Its weaknesses are limited action coverage (only 'generate a checklist') and a broad trigger that risks overlap with other planning skills.

Suggestions

List 2-3 concrete actions instead of one, e.g. 'Turn a coding request into an approach, a scoped In/Out list, and 6-10 atomic verb-first tasks' to raise specificity.

Add natural trigger synonyms users would say, such as 'break down this task', 'give me steps', or 'create a todo list' to improve trigger term coverage.

Sharpen the trigger to reduce conflict with general planning skills, e.g. 'Use when a user asks for a concise, atomic checklist-style plan for a coding task (not full architecture design)'.

Dimension	Reasoning	Score
Specificity	"generate a clear, actionable, and atomic checklist" names the domain (coding-task planning) with one concrete action, matching anchor 3; it does not list several specific actions (4) and the action is more concrete than generic (2).	3 / 5
Completeness	Both parts are explicit: the what ("generate a clear, actionable, and atomic checklist") and the when ("Use when a user asks for a plan for a coding task") with a concrete trigger phrase, matching anchor 5 rather than 4 since the 'when' is already explicit and specific.	5 / 5
Trigger Term Quality	"asks for a plan for a coding task" is a natural phrase, but common variations users say ("break down this task", "steps", "roadmap", "todo list") are missing, matching anchor 3 rather than 4.	3 / 5
Distinctiveness Conflict Risk	"plan for a coding task" is a fairly broad trigger that overlaps with general planning and project-breakdown skills, matching anchor 3 ("somewhat specific but could still overlap"); it is not generic enough for 2 nor narrowly triggered enough for 4.	3 / 5
	Total	14 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: sickn33/agentic-awesome-skills
Path: skills/concise-planning/SKILL.md
Commit: 7b534bc

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.