planning-with-files
Transforms workflow to use Manus-style persistent markdown files for planning, progress tracking, and knowledge storage. Use when starting complex tasks, multi-step projects, research tasks, or when the user mentions planning, organizing work, tracking progress, or wants structured output.
93
91%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
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 has strong completeness with explicit 'Use when' triggers and good natural language keywords. However, it lacks specificity in describing concrete actions (what exactly does 'transforms workflow' mean in practice?) and has moderate conflict risk with other planning/organization skills due to broad trigger terms.
Suggestions
Add specific concrete actions like 'creates todo.md for task tracking, maintains progress.md for status updates, builds knowledge.md for research notes'
Clarify what 'Manus-style' means or add distinguishing characteristics to reduce overlap with generic planning skills
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (workflow transformation, markdown files) and some actions (planning, progress tracking, knowledge storage), but lacks concrete specific actions like 'create todo.md files', 'update progress sections', or 'generate summary documents'. | 2 / 3 |
Completeness | Clearly answers both what ('Transforms workflow to use Manus-style persistent markdown files for planning, progress tracking, and knowledge storage') and when ('Use when starting complex tasks, multi-step projects, research tasks, or when the user mentions planning, organizing work, tracking progress, or wants structured output'). | 3 / 3 |
Trigger Term Quality | Good coverage of natural terms users would say: 'complex tasks', 'multi-step projects', 'research tasks', 'planning', 'organizing work', 'tracking progress', 'structured output'. These are phrases users naturally use when needing this type of workflow. | 3 / 3 |
Distinctiveness Conflict Risk | The 'Manus-style' qualifier adds some distinctiveness, but terms like 'planning', 'organizing work', and 'structured output' could overlap with general project management or documentation skills. Could conflict with other planning or markdown-related skills. | 2 / 3 |
Total | 10 / 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 an excellent skill file that demonstrates best practices across all dimensions. It's concise yet comprehensive, provides immediately actionable templates and workflows, has clear sequencing with explicit checkpoints, and appropriately structures content with references to advanced materials. The use of tables for quick reference and the anti-patterns section are particularly effective.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, using tables and templates to convey information without explaining concepts Claude already knows. Every section serves a clear purpose with no padding or unnecessary explanations. | 3 / 3 |
Actionability | Provides concrete, copy-paste ready templates for task_plan.md and notes.md, clear bash-style commands showing the workflow loop, and specific file patterns. The guidance is immediately executable. | 3 / 3 |
Workflow Clarity | The workflow is explicitly sequenced with numbered loops, clear 'before/after' checkpoints, and explicit validation steps (read before decide, update after act). The anti-patterns table reinforces correct behavior. | 3 / 3 |
Progressive Disclosure | Well-structured with quick start, core workflow, templates, and rules in logical order. Advanced content is appropriately deferred to reference.md and examples.md with clear signaling. | 3 / 3 |
Total | 12 / 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
- jarrodwatts/claude-code-config
- Commit
bb7e8b0
- 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.