CtrlK
BlogDocsLog inGet started
Tessl Logo

todoist-automation

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

75

1.56x
Quality

65%

Does it follow best practices?

Impact

94%

1.56x

Average score across 3 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

61%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 body is a dense, actionable MCP-orchestration guide with clear sequencing and strong parameter detail, but it loses points to redundant pitfall duplication and missing validation feedback loops for destructive/batch operations.

Suggestions

Add explicit post-action validation for destructive and batch operations (e.g., re-fetch the task/project after DELETE or BULK_CREATE to confirm the result) to lift workflow_clarity above the destructive/batch cap of 3.

Consolidate the 'Known Pitfalls' section by referencing the per-workflow Pitfalls instead of restating ID formats, priority inversion, and filter syntax, to remove redundancy.

Provide one or two complete example tool invocations with filled-in parameter values to push actionability toward copy-paste ready.

DimensionReasoningScore

Conciseness

Content is mostly operational and assumes Claude's competence without explaining what Todoist is, but the 'Known Pitfalls' section largely duplicates per-workflow pitfalls (ID formats, priority inversion, filter syntax), adding avoidable repetition.

3 / 5

Actionability

Concrete tool slugs, numbered tool sequences, exact parameter formats (YYYY-MM-DD, RFC3339), and a quick-reference table give mostly executable guidance; minor gaps in full example payloads keep it just below fully copy-paste ready.

4 / 5

Workflow Clarity

Sequences are clearly numbered with pre-flight checks ("always verify", "always check existing sections first"), but destructive (DELETE_TASK, DELETE_SECTION) and batch (BULK_CREATE_TASKS) operations lack explicit post-action validation/feedback loops, capping this at 3 per the rubric.

3 / 5

Progressive Disclosure

Well-organized single-file skill with clear sections (Prerequisites, Setup, Core Workflows, Common Patterns, Known Pitfalls, Quick Reference) and no nested references; the duplicated pitfalls content is the main organization gap.

4 / 5

Total

14

/

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 clearly names the domain and integration and is highly distinctive, but it lacks an explicit 'Use when...' trigger clause, which caps completeness. It is specific and low-conflict but not maximally complete on the 'when' dimension.

Suggestions

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

Include a couple of natural synonyms such as 'to-do list' or 'todo list' to broaden trigger coverage.

DimensionReasoningScore

Specificity

Lists several concrete capability areas — "task management, projects, sections, filtering, and bulk operations" — giving specific coverage rather than vague language, though these are domain labels rather than atomic actions.

4 / 5

Completeness

The 'what' is clearly stated ("Automate Todoist task management..."), but there is no 'Use when...' trigger clause; "Always search tools first for current schemas" is an instruction, not a usage trigger, so completeness is capped at 3.

3 / 5

Trigger Term Quality

Natural terms like "Todoist", "tasks", "projects", "filtering", and "bulk operations" match what users say, with good coverage; a few natural synonyms (e.g., "to-do list") are missing.

4 / 5

Distinctiveness Conflict Risk

Naming the specific app "Todoist" plus the integration "via Rube MCP (Composio)" gives a clear niche with minimal overlap risk against other skills.

5 / 5

Total

16

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
davepoon/buildwithclaude
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.