project-planner
Detects stale project plans and suggests session commands. Triggers on: sync plan, update plan, check status, plan is stale, track progress, project planning.
79
69%
Does it follow best practices?
Impact
94%
1.54xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./data/skills-md/0xdarkmatter/claude-mods/project-planner/SKILL.mdQuality
Discovery
82%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 functional with a clear 'what' and explicit 'when' triggers, which is its strongest aspect. The trigger terms are natural and well-chosen. However, the specificity of capabilities could be improved — 'suggests session commands' is vague, and some trigger terms like 'project planning' risk overlap with other skills.
Suggestions
Clarify what 'suggests session commands' means concretely — e.g., 'suggests commands to re-sync milestones, update task statuses, or regenerate timelines'.
Narrow the generic trigger 'project planning' to something more distinctive to reduce conflict risk with general project management skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (project plans) and two actions (detects stale plans, suggests session commands), but lacks detail on what 'suggests session commands' means concretely or what specific operations are performed. | 2 / 3 |
Completeness | Clearly answers both 'what' (detects stale project plans and suggests session commands) and 'when' (explicit 'Triggers on:' clause with specific trigger phrases), satisfying the requirement for explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes a good set of natural trigger terms users would say: 'sync plan', 'update plan', 'check status', 'plan is stale', 'track progress', 'project planning' — these cover common variations well. | 3 / 3 |
Distinctiveness Conflict Risk | The terms 'project planning' and 'track progress' are somewhat generic and could overlap with general project management or task tracking skills. However, the specific focus on 'stale plans' and 'session commands' provides some distinctiveness. | 2 / 3 |
Total | 10 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a clear conceptual framework for detecting stale project plans and suggesting commands, with a useful quick reference table. However, it lacks executable implementation details — the detection logic is described in pseudocode scenarios rather than actual commands Claude could run (e.g., `stat`, `git log --since`). The content has minor redundancy between sections.
Suggestions
Replace the pseudocode detection logic blocks with actual executable shell commands (e.g., `stat -c %Y docs/PLAN.md`, `git log --since='3 days ago' --oneline | wc -l`) so Claude can perform the staleness checks.
Add a sequenced workflow: 1. Check file exists → 2. Get modification time → 3. Compare with git activity → 4. Suggest appropriate command, to make the detection process unambiguous.
Remove redundant content between the intro paragraph, Purpose section, and Notes section to tighten token efficiency.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient but has some redundancy — the 'Purpose' section restates what the intro already says, and the 'Notes' section repeats the read/write distinction already covered. The 'This skill does NOT manage plans directly' framing is slightly verbose for Claude. | 2 / 3 |
Actionability | Provides concrete command suggestions and a useful quick reference table, but the detection logic blocks are illustrative pseudocode rather than executable code. There are no actual implementation details — no shell commands to check staleness, no code to compare git log dates with file modification times. | 2 / 3 |
Workflow Clarity | The detection scenarios are clearly enumerated and the quick reference table provides a clear situation-to-action mapping. However, there's no sequenced workflow for how Claude should actually perform detection (e.g., check file exists → check modification date → compare with git log → suggest), and no validation or feedback loops. | 2 / 3 |
Progressive Disclosure | For a skill of this size (~60 lines), the content is well-organized with clear sections (Purpose, Detection Logic, Quick Reference, Staleness Heuristics, Notes). No unnecessary nesting or external references needed for this scope. | 3 / 3 |
Total | 9 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- NeverSight/skills_feed
- Commit
9f4534c
- 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.