Name: todoist-automation
Rating: 56.00000000000001 (1 reviews)
Author: administrakt0r

todoist-automation

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

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/todoist-automation/SKILL.md

The canonical home for this skill is todoist-automation in administrakt0r/AI-Agents-Safe-Coding-Skills

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.

The content is a well-structured, highly actionable MCP reference, but it suffers from duplicated pitfalls, missing validation checkpoints on destructive/batch operations, and a monolithic inline structure with no progressive disclosure to reference files.

Suggestions

Add explicit validation steps before destructive/batch operations (e.g. 'Verify the resolved task ID with GET_TASK before CLOSE/DELETE'; 'Dry-run bulk create on one task before the full batch').

De-duplicate pitfalls: keep them once either in each workflow or in 'Known Pitfalls', not both.

Move the Quick Reference table and full filter-syntax reference into a references/ file (e.g. REFERENCE.md) and link to it from the body for progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is dense and factual with no concept over-explanation, but pitfalls are stated twice (per-workflow 'Pitfalls' subsections and again in 'Known Pitfalls') and the Quick Reference table restates workflow content, so it could be tightened.	3 / 5
Actionability	Concrete tool slugs, exact parameter names, and precise formats (YYYY-MM-DD, RFC3339, filter syntax) are given with sequenced [Required]/[Optional] tags, but there are no complete example tool invocations with all arguments filled, leaving minor gaps.	4 / 5
Workflow Clarity	Workflows are clearly numbered with prerequisite/required/optional markers, but destructive and batch operations (DELETE_TASK, DELETE_SECTION, BULK_CREATE_TASKS) lack explicit pre-execution validation checkpoints, which caps workflow clarity at 3 per the rubric.	3 / 5
Progressive Disclosure	Sections are well-organized, but with no references/scripts/assets bundle, all detail (full filter syntax, Quick Reference table, Known Pitfalls) is inlined in a ~230-line monolith that could be split into one-level-deep reference files.	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.

The description is specific, distinctive, and third-person, but it lacks an explicit 'when to use' trigger clause, capping completeness. Adding a 'Use when...' sentence naming user-facing triggers would lift it into the top band.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user wants to manage Todoist tasks, projects, sections, or run bulk task operations.'

Add natural synonyms users say ('to-do list', 'reminders') to broaden trigger-term coverage.

Convert domain labels into discrete actions (e.g. 'create, update, complete, and filter tasks') for fuller specificity.

Dimension	Reasoning	Score
Specificity	Lists several concrete operation domains ("task management, projects, sections, filtering, and bulk operations") tied to a specific integration ("via Rube MCP (Composio)"), but these are domain labels rather than discrete actions like 'extract, fill, merge', leaving minor coverage gaps.	4 / 5
Completeness	The 'what' is clearly stated (automate Todoist task/projects/sections/filtering/bulk ops), but there is no explicit 'Use when...' trigger clause — only the procedural "Always search tools first" — so per the judging guidelines completeness is capped at 3.	3 / 5
Trigger Term Quality	Natural terms a user would say are present ("Todoist", "task management", "projects", "filtering", "bulk operations") with good coverage, but synonyms like 'to-do list' or 'reminders' and file/extension cues are missing.	4 / 5
Distinctiveness Conflict Risk	Names a clear niche (Todoist automation via Rube MCP/Composio) with distinct triggers and minimal overlap risk against other skills.	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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/todoist-automation/SKILL.md
Commit: debb2ec

Reviewed: 1 day 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.