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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill 001-jeremy-taskwarrior-integration76
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
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 defines its purpose, provides explicit activation triggers, and describes concrete actions in the task lifecycle. It uses third person voice appropriately and includes both the tool name and common abbreviations. The description effectively distinguishes itself from generic task management skills through specific tool references.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions: 'Decomposes all coding work into properly tracked Taskwarrior tasks with full lifecycle: task add → task start → implementation → task done' and 'Integrates with Timewarrior for automatic time tracking.' | 3 / 3 |
Completeness | Clearly answers both what (enforces Taskwarrior integration, decomposes coding work, tracks lifecycle, integrates with Timewarrior) and when ('Activates automatically when user mentions...' with explicit triggers). | 3 / 3 |
Trigger Term Quality | Explicitly includes natural trigger terms users would say: 'taskwarrior', 'task warrior', 'tw', and 'task management'. These cover common variations including abbreviations. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting Taskwarrior/Timewarrior integration with distinct tool-specific triggers. Unlikely to conflict with generic task management or coding skills due to explicit tool names. | 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.
This skill provides highly actionable, executable guidance with clear workflows and validation steps, but is severely undermined by extreme verbosity and poor organization. The same concepts are repeated multiple times, basic Taskwarrior knowledge is over-explained, and the entire document is a monolithic wall that should be split into multiple files. Token efficiency is very poor despite the content being technically correct.
Suggestions
Reduce content by 60-70% by eliminating repetition (e.g., 'NO CODE BEFORE TASKS' stated once, not 4+ times) and removing explanations of basic Taskwarrior concepts Claude already knows
Split into multiple files: SKILL.md (core workflow ~50 lines), EXAMPLES.md (decomposition examples), REFERENCE.md (tag taxonomy, commands table), TROUBLESHOOTING.md
Remove the verbose 'What This Skill Does' and 'When This Skill Activates' sections - the activation triggers belong in frontmatter, not body content
Consolidate the 4 nearly-identical example workflows into 1-2 representative examples with brief variations noted
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~500+ lines with excessive repetition. The 'NO CODE BEFORE TASKS' rule is stated 4+ times, basic Taskwarrior concepts Claude already knows are over-explained, and the same workflow is demonstrated repeatedly with minor variations. | 1 / 3 |
Actionability | Provides fully executable bash commands throughout, with complete copy-paste ready examples for every scenario. Commands include all required attributes and the quick reference table is immediately usable. | 3 / 3 |
Workflow Clarity | Clear 5-phase workflow with explicit validation checkpoints (verify task active, check timew, completion checklist). Includes feedback loops for blockers, scope changes, and error recovery scenarios. | 3 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files. Content that could be split (tag taxonomy, troubleshooting, examples) is all inline. The 500+ line document would benefit greatly from splitting into separate reference files. | 1 / 3 |
Total | 8 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 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 |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs | Warning |
Total | 12 / 16 Passed | |
- 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.