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.
Install with Tessl CLI
npx tessl i github:NeverSight/skills_feed --skill project-planner86
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
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.
This description effectively communicates when to trigger with explicit trigger terms and answers both what/when questions. However, it could be more specific about the concrete actions performed (what does 'suggests session commands' actually mean?) and some trigger terms like 'check status' are generic enough to risk conflicts with other skills.
Suggestions
Expand specificity by detailing what 'session commands' are suggested and what criteria define a 'stale' plan (e.g., 'Detects project plans not updated in X days and suggests /sync or /refresh commands')
Make trigger terms more distinctive by adding project-plan-specific qualifiers to generic terms (e.g., 'check plan status' instead of 'check status')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (project plans) and two actions (detects stale plans, suggests session commands), but lacks comprehensive detail about what 'detecting stale' means or what specific session commands are suggested. | 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), meeting the requirement for explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger terms users would say: 'sync plan', 'update plan', 'check status', 'plan is stale', 'track progress', 'project planning' - these are realistic phrases users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | While 'project plans' and 'stale' are somewhat specific, terms like 'check status' and 'track progress' are generic enough to potentially overlap with other project management or status-tracking skills. | 2 / 3 |
Total | 10 / 12 Passed |
Implementation
85%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-structured awareness/detection skill that clearly defines its limited scope and provides actionable command suggestions. The content is concise and well-organized, though the detection logic could benefit from more concrete implementation details rather than pseudocode-style descriptions.
Suggestions
Replace pseudocode detection examples with actual shell commands or code snippets (e.g., show the actual git commands to check staleness like `git log --since="$(stat -c %Y docs/PLAN.md)" --oneline`)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, using tables and code blocks to convey information without unnecessary explanation. It assumes Claude understands concepts like git, staleness detection, and session commands. | 3 / 3 |
Actionability | Provides clear command suggestions in a table format, but the detection logic sections use pseudocode-style descriptions rather than executable code. The actual implementation of staleness detection is described conceptually rather than with concrete commands. | 2 / 3 |
Workflow Clarity | For a detection/suggestion skill that explicitly states it 'only suggests, never modifies,' the workflow is appropriately clear. Each situation maps to a specific command suggestion, and the staleness heuristics provide explicit criteria. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections (Purpose, Detection Logic, Quick Reference, Staleness Heuristics, Notes). For a skill under 50 lines with no need for external references, the structure is appropriate and easy to navigate. | 3 / 3 |
Total | 11 / 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.
- 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.