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

63%

Does it follow best practices?

Impact

94%

1.56x

Average score across 3 eval scenarios

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/all-skills/skills/todoist-automation/SKILL.md

Quality

Content

57%Weight 40%Scale 1-5

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

A highly actionable, well-structured reference for Todoist MCP operations with concrete tool sequences and parameter-level detail throughout. Its weaknesses are significant duplication of pitfalls across sections, no validation checkpoints around destructive and bulk operations, and a monolithic single-file layout where the parameter catalogs and quick-reference table belong in separate reference files.

Suggestions

Consolidate the repeated pitfalls — priority inversion, due-date rules, and filter syntax each appear two to three times across workflow sections and Known Pitfalls — into a single authoritative section and cross-reference it.

Add validation checkpoints for destructive and batch operations: confirm with the user before DELETE_TASK/DELETE_SECTION, and verify bulk-created tasks by listing the target project afterwards with error-recovery steps on partial failure.

Split the Quick Reference table and the per-workflow parameter catalogs into reference files (e.g., references/tools.md, references/parameters.md), keeping SKILL.md as a workflow overview.

Dimension	Reasoning	Score
Conciseness	The body is dense with API-specific detail Claude cannot know (tool slugs, parameter names, ID format quirks), but key pitfalls are repeated — priority inversion appears three times (workflow 1 params/pitfalls and the Known Pitfalls section), and due-date rules and filter pitfalls each appear twice — so it could be meaningfully tightened. It is not a 2 because nothing explains concepts Claude already knows.	3 / 5
Actionability	Gives concrete tool slugs, exact parameter names, precise formats (RFC3339 `YYYY-MM-DDTHH:mm:ssZ`, `YYYY-MM-DD`), filter operators (`&`, `\|`, `!`), and a Quick Reference table mapping task to tool to params — mostly executable guidance with the minor gap of no complete example tool invocations or payloads, which keeps it below the fully copy-paste-ready 5 anchor.	4 / 5
Workflow Clarity	Sequences are clearly numbered with [Required]/[Optional]/[Prerequisite] markers and setup includes connection verification, but destructive operations (`TODOIST_DELETE_TASK`, `TODOIST_DELETE_SECTION`) and batch operations (`TODOIST_BULK_CREATE_TASKS`) lack validation or confirmation checkpoints, which caps workflow clarity at 3 per the rubric's destructive/batch rule. Not a 2 because sequences are well defined and some error-recovery hints exist (retry with numeric ID on HTTP 400).	3 / 5
Progressive Disclosure	Section structure is good with clear headers, but ~230 lines of per-workflow parameter catalogs plus a 17-row Quick Reference API table are all inlined in a single SKILL.md with zero reference files — content that belongs in bundle files is inline, matching the 3 anchor. Not a 2 because the structure is well organized, not minimal.	3 / 5
	Total	13 / 20 Passed

Description

70%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description that names the product and five concrete capability areas with low conflict risk, but it lacks an explicit "Use when..." trigger clause and misses natural synonyms like "to-do list". Adding trigger guidance would lift the two weakest dimensions.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user mentions Todoist, to-do lists, tasks, projects, or task filtering".

Include natural synonyms users actually say — "to-do list", "todo", "reminders", "checklist" — alongside the product-specific terms.

Replace the generic "task management" phrase with concrete actions (create, update, complete, delete tasks) to sharpen the what.

Dimension	Reasoning	Score
Specificity	Lists several concrete capability areas ("task management, projects, sections, filtering, and bulk operations"), matching the several-specific-actions anchor, though "task management" is generic phrasing and actions are noun-listed rather than distinct concrete verbs, keeping it below the comprehensive 5 anchor.	4 / 5
Completeness	The "what" is clearly stated (automating Todoist task/project/section/filtering/bulk operations), but there is no "Use when..." trigger clause; "Always search tools first for current schemas" is an instruction, not a when-condition, which caps completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	"Todoist", "tasks", "projects", "sections", "filtering", "bulk operations" give good natural keyword coverage (a user would say "Todoist"), but common synonyms like "to-do list", "todo", "reminders", or "checklist" are missing, so it falls short of the comprehensive 5 anchor.	4 / 5
Distinctiveness Conflict Risk	"Todoist" is a clear niche trigger with distinct, product-specific terms; minimal risk of firing for the wrong skill, matching the clear-niche anchor.	5 / 5
	Total	16 / 20 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
Path: plugins/all-skills/skills/todoist-automation/SKILL.md
Commit: c9856ea

Reviewed: 6 days 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.