Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →microck/file-todos
This skill should be used when managing the file-based todo tracking system in the todos/ directory. It provides workflows for creating todos, managing status and dependencies, conducting triage, and integrating with slash commands and code review processes.
Passed 16 of 19 test cases with the skill, and 5 of 19 without it.
and 10 more in the full report
13 fixed6 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
When approving a pending issue `001-pending-p2-mailer-test.md` during triage without changing its priority, what exact target filename should `mv` use?
| Checked | Without skill | With skill |
|---|---|---|
| The destination filename is 001-ready-p2-mailer-test.md | Missed | Passed |
The instructions your model reads when the skill loads.
The todos/ directory contains a file-based tracking system for managing code review feedback, technical debt, feature requests, and work items. Each todo is a markdown file with YAML frontmatter and structured sections.
This skill should be used when:
Todo files follow this naming pattern:
{issue_id}-{status}-{priority}-{description}.md
Components:
pending (needs triage), ready (approved), complete (done)p1 (critical), p2 (important), p3 (nice-to-have)Examples:
001-pending-p1-mailer-test.md
002-ready-p1-fix-n-plus-1.md
005-complete-p2-refactor-csv.md
Each todo is a markdown file with YAML frontmatter and structured sections. Use the template at assets/todo-template.md as a starting point when creating new todos.
Required sections:
test cases passed, vs 5 / 19 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.