- name
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add Doist/todoist-cli --skill verify -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add Doist/todoist-cli --skill verify -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add Doist/todoist-cli --skill verify -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add Doist/todoist-cli --skill verify -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/Doist/todoist-cli/tree/HEAD/.agents/skills/verifyFrom the publisher
npm run verify
It runs every check CI runs (about fifteen seconds) and records the pass. Fix every failure; never weaken a check to pass it. Done when it prints Verified., or says only docs changed and there is nothing to check.
The checks prove nothing broke. Now prove the change does what was asked, with the proof its kind needs:
Check the proof can fail: undo the change and see the test fail, or run the scenario that used to break. Done when you have seen it fail and then pass. A refactor is the exception: its proof is the pinned tests passing before and after (see refactor).
Rate every claim on this ladder:
path:line).Claims about behaviour ("fixed", "works", "safe", "no regressions") need ran or higher. A fact the code shows needs cited. Anything lower goes under Not verified, with why.
For a change to code others rely on (shared helpers in src/lib/, command registration and global flags in src/index.ts, an @doist/cli-core or @doist/todoist-sdk upgrade), name the one fact that makes it safe, and how you proved it.
Report format:
What changed: <one line>
Verified:
- <claim> — ran: <command or test>, <what it showed>
Not verified:
- <claim> — <why>
Safe because: <the one fact>, <how you proved it> (only for shared code)
Proves a change works before it is called done, and reports the evidence on a ladder from "said" to "ran". Use when you are about to say "done", "fixed", "works" or "ready", when asked to check or tes
---name: verifydescription: Proves a change works before it is called done, and reports the evidence on a ladder from "said" to "ran". Use…---# .agents/skills/verify/SKILL.mdOverview
Proves a change works before it is called done, and reports the evidence on a ladder from "said" to "ran". Use when you are about to say "done", "fixed", "works" or "ready", when asked to check or test a change, or before opening a pull request.
FAQ
Download .agents/skills/verify/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/Doist/todoist-cli.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.