001-jeremy-taskwarrior-integration
Enforces complete Taskwarrior integration protocol for ALL coding tasks. Activates automatically when user mentions "taskwarrior", "task warrior", "tw", or discusses task management. Decomposes all coding work into properly tracked Taskwarrior tasks with full lifecycle: task add → task start → implementation → task done. Integrates with Timewarrior for automatic time tracking.
81
77%
Does it follow best practices?
Impact
81%
1.76xAverage score across 6 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./backups/skills-migration-20251108-070147/plugins/productivity/001-jeremy-taskwarrior-integration/skills/001-jeremy-taskwarrior-integration/SKILL.mdQuality
Discovery
100%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 is a strong skill description that clearly identifies its domain (Taskwarrior integration), lists specific actions (task lifecycle management, time tracking), and provides explicit trigger conditions. It uses third person voice appropriately and covers natural keyword variations. The description is concise yet comprehensive enough to distinguish it from other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: decomposes coding work into tasks, tracks full lifecycle (task add → task start → implementation → task done), integrates with Timewarrior for time tracking. These are concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what (decomposes coding work into Taskwarrior tasks with full lifecycle, integrates with Timewarrior) and when ('Activates automatically when user mentions "taskwarrior", "task warrior", "tw", or discusses task management'). Explicit trigger guidance is present. | 3 / 3 |
Trigger Term Quality | Includes natural trigger terms users would say: 'taskwarrior', 'task warrior', 'tw', 'task management'. These cover common variations including abbreviations and alternate spellings. | 3 / 3 |
Distinctiveness Conflict Risk | Very distinct niche targeting Taskwarrior specifically, with clear trigger terms tied to a specific tool. Unlikely to conflict with generic task management or coding skills due to the explicit Taskwarrior/Timewarrior focus. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
55%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides highly actionable, well-sequenced Taskwarrior integration guidance with concrete commands and clear workflows. However, it is severely bloated—repeating the same lifecycle pattern 6+ times across examples, summaries, and expected workflows. The entire content should be condensed to roughly 1/3 its current size by extracting reference material (tag taxonomy, priority matrix, troubleshooting) into separate files and eliminating redundant examples.
Suggestions
Reduce from ~400 lines to ~120-150 by removing redundant lifecycle demonstrations—keep one protocol walkthrough and one complex example, cut the rest.
Extract the tag taxonomy, priority guidelines, troubleshooting, and quick reference table into a separate REFERENCE.md file, linking from the main skill.
Remove the 'What This Skill Does', 'Summary', and 'When This Skill Activates' sections—these explain things Claude can infer from the protocol itself.
Eliminate the 'Integration with Your Workflow' section entirely—it's vague, non-actionable filler about VS Code extensions and CI/CD pipelines with no concrete guidance.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~400+ lines. Massive redundancy: the same lifecycle (add → start → done) is repeated in the protocol, four examples, the expected workflow, the quick reference, the summary, and the best practices. Priority guidelines, tag taxonomies, and troubleshooting sections explain things Claude already knows. The 'What This Skill Does' and 'Summary' sections say the same thing twice. | 1 / 3 |
Actionability | All commands are concrete, executable bash commands with proper Taskwarrior syntax. Examples include specific task IDs, real project names, and complete command sequences. The quick reference table and code blocks are copy-paste ready. | 3 / 3 |
Workflow Clarity | The 5-phase protocol is clearly sequenced with explicit validation checkpoints (verify task is active, check timew, completion checklist). Special scenarios cover blockers, scope changes, and multi-session work with clear stop/annotate/modify feedback loops. The enforcement rules and verification checklist are explicit. | 3 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files. The tag taxonomy, priority guidelines, troubleshooting, and integration sections could easily be split into separate reference files. Everything is inlined in one massive document with no navigation structure beyond headers. | 1 / 3 |
Total | 8 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (588 lines); consider splitting into references/ and linking | Warning |
Total | 10 / 11 Passed | |
- Commit
805deb2
- 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.