todoist-automation

Automate Todoist task management, projects, sections, filtering, and bulk operations via Rube MCP (Composio). Always search tools first for current schemas.

1.56x

Quality

—

Does it follow best practices?

Impact

94%

1.56x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Quality

Content

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable and well sequenced, with genuinely non-obvious API pitfalls. Its weaknesses are redundancy across sections (hurting conciseness), missing validation feedback loops for destructive/batch operations (capping workflow clarity), and a monolithic single-file structure that could leverage progressive disclosure.

Suggestions

Collapse the duplicated pitfalls: present priority inversion, ID formats, and filter syntax once in the Known Pitfalls section and reference them from the workflows instead of restating in each section's Pitfalls block; consider dropping or shrinking the Quick Reference table that repeats the workflow listings.

Add explicit validation/verification checkpoints before destructive and batch operations — e.g., for DELETE_TASK verify the task_id via GET_TASK first, and for BULK_CREATE_TASKS confirm project/section IDs resolve before submitting the batch.

Move the Quick Reference table and/or the detailed Known Pitfalls into one-level-deep reference files (e.g., references/QUICK_REFERENCE.md) and signal them from the overview, so the main SKILL.md stays a lean entry point.

Dimension	Reasoning	Score
Conciseness	The body is largely non-obvious API-specific detail Claude would not know (tool slugs, parameter formats, pitfalls), but it is ~230 lines with notable redundancy: priority inversion, ID-format quirks, due-date handling, and filter syntax each repeat across the per-workflow Pitfalls blocks, the Known Pitfalls section, and the Quick Reference table. This could be tightened, matching the 'mostly efficient but could be tightened' anchor.	2 / 3
Actionability	Guidance is concrete and copy-paste ready: exact tool slugs, exact parameter names, concrete field formats (YYYY-MM-DD, RFC3339), filter-syntax examples, and natural-language date examples leave no ambiguity about what to call and with what arguments.	3 / 3
Workflow Clarity	Workflows are well sequenced with [Prerequisite]/[Required]/[Optional] tags and the Setup section has explicit checkpoints ("Confirm connection status shows ACTIVE before running any workflows"), but destructive and batch operations (DELETE_TASK, DELETE_SECTION, BULK_CREATE_TASKS) lack explicit validate-then-proceed feedback loops; per the rubric this caps workflow_clarity at 2.	2 / 3
Progressive Disclosure	No bundle files exist and all content is inline in a single ~230-line SKILL.md. Sections are clearly organized, but a document of this size covering five workflows plus a Quick Reference table and detailed pitfalls is monolithic and could be split into one-level-deep reference files; it is not the deeply-nested or poorly-organized case (1) nor the well-signaled multi-file case (3).	2 / 3
	Total	9 / 12 Passed

Description

82%

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 is specific, uses natural trigger terms, and occupies a clear niche, but it lacks an explicit 'Use when...' trigger clause so the WHEN is only implied. Adding a usage trigger would raise the completeness dimension.

Suggestions

Add an explicit trigger clause such as 'Use when the user wants to manage Todoist tasks, projects, sections, or filters, or perform bulk task operations.' to satisfy the WHEN requirement.

Drop the procedural aside 'Always search tools first for current schemas.' from the description — it is a behavioral instruction, not a capability or trigger, and adds noise.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete action areas — "task management, projects, sections, filtering, and bulk operations" — naming the domain and several specific operations, matching the anchor for multiple specific concrete actions.	3 / 3
Completeness	It clearly answers WHAT ("Automate Todoist task management, projects, sections, filtering, and bulk operations via Rube MCP") but has no "Use when..." clause or equivalent explicit trigger guidance, so WHEN is only implied; per the rubric a missing explicit trigger caps completeness at 2.	2 / 3
Trigger Term Quality	Natural terms a user would say are well covered — "Todoist", "tasks", "projects", "sections", "filtering", "bulk operations" — matching the anchor for good coverage of natural terms.	3 / 3
Distinctiveness Conflict Risk	Todoist automation via Rube MCP (Composio) is a clear, narrow niche with distinct triggers unlikely to overlap with other skills.	3 / 3
	Total	11 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: davepoon/buildwithclaude
Commit: 366e45b

Reviewed: about 22 hours ago

Table of Contents

Discovery Implementation Validation

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.