Content
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid reference-style skill that covers Todoist operations comprehensively with good structural organization and useful pitfall documentation. Its main weaknesses are redundancy between sections (pitfalls repeated, quick reference duplicating workflow content), lack of concrete executable examples showing actual MCP tool invocations, and missing validation/confirmation steps for destructive operations. The content would benefit from being split across multiple files and including copy-paste-ready invocation patterns.
Suggestions
Add concrete, copy-paste-ready MCP tool invocation examples (e.g., a complete TODOIST_CREATE_TASK call with actual parameter values) rather than just listing parameter names and descriptions.
Add explicit validation/confirmation steps after destructive operations (DELETE_TASK, DELETE_SECTION, CLOSE_TASK) and after bulk operations (BULK_CREATE_TASKS) — e.g., 'Verify by calling GET_ALL_TASKS to confirm creation'.
Consolidate the duplicated pitfall information — remove per-workflow pitfalls that are repeated verbatim in the 'Known Pitfalls' section, or vice versa, to reduce token usage.
Consider splitting the quick reference table and detailed parameter documentation into a separate REFERENCE.md file to reduce the main skill's token footprint.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly comprehensive but includes some redundancy — the 'Known Pitfalls' section repeats information already covered in per-workflow pitfall sections (priority inversion, ID formats, filter syntax). The quick reference table at the end also largely duplicates information from the workflow sections. However, it generally avoids explaining concepts Claude already knows. | 2 / 3 |
Actionability | The skill provides specific tool names, parameter names, and concrete values (e.g., date formats, filter syntax examples), which is good. However, it lacks executable code examples or copy-paste-ready tool invocation examples showing actual MCP call patterns with real parameter structures. The guidance is detailed but remains at the 'describe the parameters' level rather than showing complete invocation examples. | 2 / 3 |
Workflow Clarity | Workflows are clearly sequenced with numbered steps and labeled as Required/Optional/Prerequisite, which is helpful. However, there are no explicit validation checkpoints or error recovery feedback loops — for example, after bulk task creation there's no 'verify tasks were created' step, and after delete operations there's no confirmation step. Given that delete/close operations are destructive, this is a notable gap. | 2 / 3 |
Progressive Disclosure | The content is well-organized with clear sections and headers, but it's a monolithic ~200-line document with no bundle files to offload detailed reference material. The quick reference table, detailed pitfalls, and per-workflow parameter documentation could be split into separate files. For a skill of this complexity, the single-file approach makes it harder to navigate and consumes significant context window. | 2 / 3 |
Total | 8 / 12 Passed |