BF ms-todo-oauth
Manage Microsoft To Do lists and tasks through a local Python CLI backed by Microsoft Graph OAuth. Use when an agent needs to inspect, add, complete, delete, search, export, or summarize Microsoft To Do tasks, including priorities, due dates, reminders, recurrence, and list selection. Requires local dependency setup and an interactive OAuth authorization-code login on first use.
As a process F 53/100 · Will not run — References files that are not bundled: scripts/MANUAL_TEST_CHECKLIST.txt
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 7. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 9388 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: scripts/MANUAL_TEST_CHECKLIST.txt
Process rating: all ten parameters 53/100
- 0Tools and files. 1 referenced file(s) missing: scripts/MANUAL_TEST_CHECKLIST.txt
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 40Execution cost. Instruction body is 9388 tokens: crowds the task out of the window
- 50When it triggers. No condition that starts the skill
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 165 steps
- 100Failures and branches. 17 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 14 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (11 tags): a typed call is more reliable
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -5TODO / placeholder text left in the skill
- -2localhost URLs: will not work for another user
- -253 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +3Description length 381: enough signal without eating the budget
- +4Structure: 60 headings
- +3Step-by-step instructions: 165 items
- +4Has examples (53 code blocks)
- +3All 2 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 62.