todoist

Manage Todoist tasks via the `todoist` CLI (list, add, modify, complete, delete). Supports filters, projects, labels, and priorities.

Quality

73%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Risky

Do not use without reviewing

Optimize this skill with Tessl

npx tessl skill review --optimize ./public/skills/2mawi2/todoist-task-manager/SKILL.md

Quality

Discovery

67%

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 strong in specificity and distinctiveness, clearly naming the tool (Todoist CLI) and listing concrete operations (list, add, modify, complete, delete) along with supported features. Its main weaknesses are the lack of an explicit 'Use when...' clause and missing some natural user trigger terms like 'to-do', 'todo', or 'task management'.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to manage tasks, to-dos, or mentions Todoist.'

Include natural trigger term variations such as 'to-do list', 'todo', 'task management', and 'checklist' to improve matching with user language.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: list, add, modify, complete, delete tasks. Also mentions specific features: filters, projects, labels, and priorities.	3 / 3
Completeness	Clearly answers 'what does this do' with specific actions and features, but lacks an explicit 'Use when...' clause or equivalent trigger guidance, which caps this at 2 per the rubric.	2 / 3
Trigger Term Quality	Includes good terms like 'Todoist', 'tasks', 'todoist CLI', 'projects', 'labels', 'priorities', but misses common user phrases like 'to-do list', 'todo', 'task management', or 'reminders'. Users might not say 'todoist CLI' naturally.	2 / 3
Distinctiveness Conflict Risk	Very clearly scoped to Todoist specifically via the `todoist` CLI tool. The mention of the specific tool and service name makes it highly unlikely to conflict with other task management or general productivity skills.	3 / 3
	Total	10 / 12 Passed

Implementation

79%

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, actionable CLI reference skill with excellent concrete examples and efficient token usage. Its main weakness is the lack of explicit workflow sequencing—particularly around sync requirements after mutations—which could lead to stale cache issues. The filter syntax section, while useful, adds length that could be offloaded to a reference file.

Suggestions

Add a sync validation checkpoint to the modify/complete/delete sections (e.g., 'Always run `todoist sync` after mutations to push changes')

Consider extracting the filter syntax table into a separate FILTERS.md reference file to keep the main skill leaner

Dimension	Reasoning	Score
Conciseness	The skill is lean and efficient. Every section provides concrete commands without explaining what Todoist is or how CLI tools work. The filter syntax table is a useful reference that earns its place. No unnecessary padding or explanations of concepts Claude already knows.	3 / 3
Actionability	Every section contains fully executable, copy-paste ready commands with clear inline comments explaining what each does. The setup section provides a complete step-by-step with actual commands. Examples cover the full range of operations with realistic arguments.	3 / 3
Workflow Clarity	The skill is organized by operation type which is clear, but there's no explicit workflow for common multi-step scenarios (e.g., sync → list → modify → sync). The note about running 'todoist sync' after changes is buried at the bottom rather than integrated as a validation checkpoint in the modify/complete/delete workflows.	2 / 3
Progressive Disclosure	The content is well-structured with clear section headers, but the filter syntax table and reference section make the file somewhat long. The filter syntax could be split into a separate reference file. However, for a standalone skill with no bundle, the organization is reasonable with clear sections acting as progressive layers.	2 / 3
	Total	10 / 12 Passed

Validation

72%

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 — 8 / 11 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	8 / 11 Passed

Repository: Demerzels-lab/elsamultiskillagent
Commit: f45fcb5

Reviewed: 12 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.