CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

project-planner

Universal project planning for non-technical projects. Domains: business, personal, creative, academic, organizational, events. Capabilities: goal setting, milestone planning, resource allocation, timeline creation, risk assessment, progress tracking. Actions: create, plan, structure, breakdown, track projects. Keywords: project plan, roadmap, strategy, goal setting, milestones, timeline, action plan, project management, business plan, personal goals, creative project, academic planning, event planning, organizational change, OKRs, SMART goals, Gantt chart. Use when: creating project plans, setting goals/milestones, planning business initiatives, organizing events, structuring academic work, developing strategies/roadmaps.

Quality

76%

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 ./skills/project-planner/SKILL.md
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 delivers genuinely actionable planning infrastructure — exact file conventions, frontmatter spec, section templates, and validation checklists — but at roughly twice the necessary length. Trigger catalogs are repeated three times, generic principle/quality sections add nothing Claude doesn't know, and the complete-plan template duplicates the step-by-step templates, all of which inflates token cost for every invocation.

Suggestions

Cut the duplicated trigger catalogs: 'Common Project Types Example Triggers' repeats the 'When to Use This Skill' categories almost verbatim — keep one copy and delete the other.

Delete 'Core Planning Principles' and 'Quality Standards' (generic guidance like 'Clarity over complexity' and 'No jargon without explanation'); fold any non-redundant items into the existing Format Validation checklist.

Consolidate the seven per-step output templates and the 'Complete Plan Template' into one canonical template, or move the per-step detail templates to a references/ file that SKILL.md links to, to cut the ~550-line body to a lean overview.

DimensionReasoningScore

Conciseness

Noticeably verbose with several padded/duplicated sections: trigger catalogs appear three times ("When to Use This Skill", "Common Project Types Example Triggers" lines repeating the same categories, and the frontmatter echo); "Core Planning Principles" ("Clarity over complexity - Simple, understandable plans") and "Quality Standards" ("No jargon without explanation", "Ambiguity eliminated") restate knowledge Claude already has; the "Complete Plan Template" duplicates the seven per-step output formats. Matches anchor 2 (several unnecessary or padded sections). Not 1 because the templates themselves are the skill's deliverable rather than filler explanation; not 3 because the duplication is pervasive, not occasional.

2 / 5

Actionability

Concrete, executable guidance throughout: an actual shell check ("test -f docs/plan.md && cat docs/plan.md"), exact naming convention ("PLAN-YYYYMMDD-HHMM-{project-slug}.md"), a complete required-frontmatter YAML spec, full per-section markdown templates, and stepwise tracker update workflows. Matches anchor 4 (mostly executable with minor gaps). Not 5 because the Example Usage section summarizes what a plan would contain instead of showing one completed filled-in plan, and "Same structure as implementation-planner" defers to an external skill without restating the structure. Not 3 because formats, paths, and commands are specific and directly usable.

4 / 5

Workflow Clarity

Multi-step processes are clearly sequenced with checkpoints: the mandatory Pre-Planning Protocol with a decision branch on active plans, distinct create/complete/pause tracker workflows, a phase-aware Continue Planning workflow, and a Format Validation checklist before finalizing. Matches anchor 4 (clear sequence, most checkpoints present). Not 5 because there are no error-recovery feedback loops (e.g., what to do when the validation checklist fails or docs/plan.md is malformed) and the tracker structure is only defined by reference to another skill.

4 / 5

Progressive Disclosure

Well-organized single file with clear section headers, but no bundle files exist and ~550 lines are inlined monolithically — the seven per-step output templates, the Complete Plan Template, and the example scenarios are content that could live in reference files or be deduplicated. Matches anchor 3 (some structure, but content that should be separate is inline). Not 4 because no references exist and the bulk template material is not split out; not 2 because section organization is consistent and navigable, unlike the structureless inlining of the anchor-2 example.

3 / 5

Total

13

/

20

Passed

Description

87%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: third-person, comprehensive natural keywords with synonyms, and an explicit 'Use when:' clause answering both what and when. The main risk is scope ambiguity — 'universal' planning vocabulary like roadmap, strategy, and project management overlaps the referenced implementation-planner skill, and the description alone doesn't tell Claude when to defer.

DimensionReasoningScore

Specificity

Lists several specific domain actions ("goal setting, milestone planning, resource allocation, timeline creation, risk assessment, progress tracking") beyond just naming the domain, matching the anchor for several specific actions with minor gaps. Not 5 because the Actions segment ("create, plan, structure, breakdown, track projects") is generic verb-listing rather than concrete deliverable actions, and not 3 because the capability enumeration is multi-item and domain-specific.

4 / 5

Completeness

Explicitly answers both: what ("Universal project planning for non-technical projects... goal setting, milestone planning, resource allocation...") and when ("Use when: creating project plans, setting goals/milestones, planning business initiatives, organizing events, structuring academic work, developing strategies/roadmaps"). This mirrors the anchor-5 example structure with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural-term coverage including synonyms and domain vocabulary: "project plan, roadmap, strategy, goal setting, milestones, timeline, action plan, project management, business plan, personal goals, creative project, academic planning, event planning, organizational change, OKRs, SMART goals, Gantt chart". Matches the anchor for comprehensive coverage with synonyms (project plan / action plan / business plan; goal setting / SMART goals). Not 4 because few natural planning terms are actually missing.

5 / 5

Distinctiveness Conflict Risk

The "non-technical projects" qualifier narrows the niche, but the description itself omits the body's software exclusion ("NOT for software development - Use implementation-planner"), and its broad triggers ("roadmap, strategy, action plan, project management, milestones") would frequently fire in technical contexts where the sibling implementation-planner applies. Somewhat specific but real overlap risk with closely related planning skills. Not 4 because the software/technical boundary is not stated in the description; not 2 because the domain enumeration and non-technical qualifier do distinguish it from generic skills.

3 / 5

Total

17

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

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

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository

samhvw8/dot-claude

Path

skills/project-planner/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.