todoist-automation
Automate Todoist task management, projects, sections, filtering, and bulk operations via Rube MCP (Composio). Always search tools first for current schemas.
Install with Tessl CLI
npx tessl i github:davepoon/buildwithclaude --skill todoist-automation70
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
50%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description effectively communicates specific Todoist capabilities and has a clear, distinctive niche. However, it critically lacks explicit trigger guidance ('Use when...') which would help Claude know when to select this skill, and includes technical jargon (Rube MCP, Composio) that users wouldn't naturally mention.
Suggestions
Add a 'Use when...' clause with trigger terms like 'when the user mentions Todoist, to-do lists, task organization, or wants to manage tasks programmatically'
Include natural language variations users might say: 'to-do', 'todo', 'tasks', 'reminders', 'task list'
Move technical implementation details (Rube MCP, Composio) to the skill body rather than the description, as users won't reference these terms
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'task management, projects, sections, filtering, and bulk operations' - these are distinct, actionable capabilities within the Todoist domain. | 3 / 3 |
Completeness | Describes what it does (Todoist automation) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. The instruction to 'search tools first' is implementation guidance, not selection guidance. | 1 / 3 |
Trigger Term Quality | Includes 'Todoist' and 'task management' which are natural terms, but missing common variations users might say like 'to-do list', 'tasks', 'reminders', or 'todo'. Technical terms like 'Rube MCP (Composio)' are jargon users wouldn't naturally use. | 2 / 3 |
Distinctiveness Conflict Risk | Very clear niche - specifically targets Todoist via Rube MCP/Composio. The combination of platform (Todoist) and integration method makes it highly distinctive and unlikely to conflict with other task management skills. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, highly actionable skill with excellent workflow clarity and specific, executable guidance. The main weaknesses are moderate verbosity from repeated pitfall warnings across sections and a monolithic structure that could benefit from splitting reference material into separate files. The content successfully teaches Claude exactly how to use Todoist via Rube MCP with clear tool sequences and parameter specifications.
Suggestions
Consolidate duplicate pitfall warnings (ID formats, priority inversion) into the single 'Known Pitfalls' section and remove redundant mentions from individual workflows
Consider extracting the Quick Reference table and detailed parameter lists into a separate REFERENCE.md file to reduce SKILL.md length
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some redundancy - pitfalls are repeated across sections (ID formats mentioned multiple times), and some explanations could be tighter. The Known Pitfalls section largely duplicates warnings already given in workflow sections. | 2 / 3 |
Actionability | Excellent actionability with specific tool names, exact parameter names, concrete examples of filter syntax, date formats (RFC3339, YYYY-MM-DD), and clear key parameters for each operation. The quick reference table provides copy-paste ready tool slugs and params. | 3 / 3 |
Workflow Clarity | Clear numbered sequences with explicit prerequisites marked, optional vs required steps labeled, and validation built into the setup flow (verify connection ACTIVE before proceeding). Each workflow has a 'When to use' trigger and logical tool ordering. | 3 / 3 |
Progressive Disclosure | Content is well-structured with clear sections, but it's a monolithic document (~250 lines) that could benefit from splitting detailed pitfalls or the quick reference into separate files. The single external link to Composio docs is appropriate, but no internal file references exist. | 2 / 3 |
Total | 10 / 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 |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 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.