docket
/docket
Use when starting, planning, finishing or pausing any work in a project tracked in Docket, or when you notice a bug, risk or follow-up while working. Docket is the user's personal planner and you keep it true.
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 07.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use when starting, planning, finishing or pausing any work in a project tracked in Docket, or when you notice a bug, risk or follow-up while working. Docket is the user's personal planner and you keep it true.
Original author description
Use when starting, planning, finishing or pausing any work in a project tracked in Docket, or when you notice a bug, risk or follow-up while working. Docket is the user's personal planner and you keep it true.
How it works
SKILL.md has no level-two headings · 29 lines, 345 words
SKILL.md preview
--- name: docket description: Use when starting, planning, finishing or pausing any work in a project tracked in Docket, or when you notice a bug, risk or follow-up while working. Docket is the user's personal planner and you keep it true. --- # Docket: keep the planner true Every piece of work has a task: the task is the record, not the diff or your chat. Use the user's language. **Start** 1. `search` the request. Found: `get_task`, then `move_tasks` to `doing`. Missing: `create_tasks` once with the plan in `description_md`, `status: doing`, `planned_for` today, right project (`list_projects`; none fits: ask, don't create one). 2. The plan is `- [ ]` steps in `description_md`. A changed plan edits the list, never a second task. **During** - Decision, obstacle or scope change: `add_note`. Tick finished steps in one `update_task` (`get_task` first: it replaces the whole text), at a note or at the end, not one call per step. - Bug, risk, flaky test or follow-up you won't fix now, even if unsure it is real: `search` for a duplicate, else `create_tasks` with `area: "issue"`, backlog, no date; description = symptom, where, how found, "found while TRK-nn". `add_note` the new ID on the current task. Never leave it only in chat. **End** (before every final message) 1. Every step ticked or moved to its own task. `add_note` the result: what changed, which checks ran, what is unchecked. 2. `move_tasks` to `done` only when your checks ran and passed; otherwise stay `doing` and say why in the note. 3. `get_board` status `doing` has nothing of yours stale. 4. The final message lists task IDs touched and issues filed. Tiny work: one `create_tasks` with `status: done`, one-line description. Hurry means one-line notes, same calls. `forbidden`, `tool_disabled`, 401, 403: don't retry or work around; say it in the final message (`docket-setup`). Unsure how a tool or field behaves: `docket-reference`. | Excuse | Reality | |---|---| | "Too small, the diff is the record" | The user reads Docket, not git. It is one call. | | "Nobody sees `doing`" | Today shows it, and a crash leaves a trail. | | "I'll file it at the end" | Late is forgotten. Write at the moment. | | "Not sure it's a real problem" | File it with what you know. The user triages. |
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · Jykitro/Docket | 86 | MIT |
| lucianoadonis/neorgon-forge | 100 | MIT |
Database snapshot: 13.11.2026 · package version 2013298b7235 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100docket-setup
Use when connecting an assistant to Docket (Claude Code, Claude Desktop or Codex), installing the Docket skills, enabling the Docket hooks, or when Docket tools are missing or fail with 401, 403, forbidden or tool_disabled. - 90docket-patterns
Use when working in the Docket repo, especially before writing a commit message, adding a test, or editing handler, service, store or web files: conventions measured from git history - 100digest-setup
Use when the user wants to set up or change what Docket digests read — "налаштуй дайджест", "configure the digest", "add GitHub to my digest", "change the Notion database" — or when docket:digest finds no ~/.config/docket/digest.json. Detects which CLIs and MCP servers are… - 100digest
Use when the user asks for a digest or a status round-up of their own work — "make a digest", "зроби дайджест", "що в мене зараз", "what's waiting on me", "round-up of my MRs/PRs/tickets". Reads the sources in ~/.config/docket/digest.json (GitLab, GitHub, Notion, local git,… - 100docket-runner
Use when someone asks to run the audit docket, process the docket, audit all repos, run batch audits, or execute the docket. Iterates through repos in docket.yaml, runs smug-judge on each, commits results, generates dashboard, and pushes to GitLab. - 100decision-docket
Keep one standing page of every decision you need from the user, each written so it can be answered cold: what happened, why it's their call, the options with their cost and gain, your recommendation, and what happens if they do nothing. The user records answers on the page; you…