Name: microsoft-to-do
Rating: 59.2 (1 reviews)
Author: membranedev

microsoft-to-do

Microsoft To Do integration. Manage Tasks, Steps, Categories. Use when the user wants to interact with Microsoft To Do data.

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/microsoft-to-do/SKILL.md

Quality

Content

68%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 highly actionable with copy-paste-ready commands and a well-sequenced connection workflow with state-based checkpoints. Its main gaps are mild padding in the intro and a lack of validation guidance for destructive actions.

Suggestions

Trim or remove the opening descriptive paragraph about what Microsoft To Do is, since Claude already knows this.

Add a validation/confirmation checkpoint for destructive actions (e.g. verify the task ID via get-task before running delete-task) to satisfy the workflow-clarity feedback-loop requirement.

Label the referenced 'Step 2' explicitly (e.g. add a '## Running actions' heading the flow points to) to remove the dangling cross-reference.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but the opening paragraph ('Microsoft To Do is a cloud-based task management app...') and some prose around connection states explain context Claude does not need, fitting the 'mostly efficient with some unnecessary explanation' anchor.	3 / 5
Actionability	Commands are fully executable and copy-paste ready (e.g. 'membrane action run <actionId> --connectionId=CONNECTION_ID --input ... --json') and the proxy flag table covers the common cases, matching the fully executable anchor.	5 / 5
Workflow Clarity	The connection flow is well-sequenced with explicit state checkpoints and a re-poll feedback loop, but the 'Popular actions' table includes destructive operations (delete-task, delete-task-list) with no validation/confirmation guidance, capping workflow clarity at 3 per the destructive-operations rule.	3 / 5
Progressive Disclosure	The single SKILL.md is well-organized with clear section headers and no nested references; content is appropriately inline given there are no bundle files, with only minor organization gaps.	4 / 5
	Total	15 / 20 Passed

Description

68%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 distinct and includes both a 'what' and a 'when' clause with the natural product trigger. Its weaknesses are the generic single verb ('Manage') for specificity and a somewhat vague 'when' clause that lacks concrete trigger phrases.

Suggestions

Replace the generic verb 'Manage' with concrete actions, e.g. 'Create, update, list, and delete Tasks, Steps, and Task Lists' to improve specificity.

Expand the 'Use when...' clause with concrete triggers, e.g. 'Use when the user wants to create tasks, check off to-dos, organize task lists, or manage Microsoft To Do data'.

Dimension	Reasoning	Score
Specificity	The description names the domain and concrete objects ('Manage Tasks, Steps, Categories') but relies on a single generic verb ('Manage') rather than enumerating concrete actions, matching the 'actions minimal or generic' anchor.	2 / 5
Completeness	Both 'what' ('Microsoft To Do integration. Manage Tasks, Steps, Categories.') and 'when' ('Use when the user wants to interact with Microsoft To Do data.') are present, but the 'when' clause is generic rather than listing concrete trigger phrases.	4 / 5
Trigger Term Quality	It includes the natural product name and trigger phrase ('Use when the user wants to interact with Microsoft To Do data'), giving good keyword coverage, though synonyms are absent.	4 / 5
Distinctiveness Conflict Risk	'Microsoft To Do' is a specific named product with distinct triggers, giving it a clear niche and minimal conflict risk with other skills.	5 / 5
	Total	15 / 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: membranedev/application-skills
Path: skills/microsoft-to-do/SKILL.md
Commit: f484c82

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.