to-tickets SKILL.md skillA
to-tickets in mattpocock/skills is at git:20261006.9e2abf8 (Oct 6, 2026), graded A.
mdr add mattpocock/skills/to-tickets@git:20261006.9e2abf8This copy is 2 versions behind it. See what changed · install this older copy instead
This line moves to the next version by itself within about an hour of that file saving one. A copy already installed stays as it is until you update it.
to-tickets from miklschmidt/archboard is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- miklschmidt/archboard
- Path
.agents/skills/to-tickets/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261025.3b43540, committed Oct 25, 2026
- Size
- 5,671 bytes
- Repository stars
- 11
- License
- a license file GitHub does not identify
Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links on a real tracker).
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# To Tickets Break a plan, spec, or conversation into a set of **tickets**: tracer-bullet vertical slices, each declaring the tickets that **block** it. The issue tracker and triage label vocabulary should have been provided to you. If not, tell the user to run `/setup-matt-pocock-skills`. ## Process ### 1. Gather context Work from whatever is already in the conversation context. If the user passes a reference (a spec path, an issue number or URL) as an argument, fetch it and read its full body and comments. ### 2. Explore the codebase (optional) If you have not already explored the codebase, do so to understand the current state of the code. Ticket titles and descriptions should use the project's domain glossary vocabulary, and respect ADRs in the area you're touching. Look for opportunities to prefactor the code to make the implementation easier. "Make the change easy, then make the easy change." ### 3. Draft vertical slices Break the work into **tracer bullet** tickets. <vertical-slice-rules> - Each slice cuts a narrow but COMPLETE path through every layer (schema, API, UI, tests): vertical, NOT a horizontal slice of one layer …
Read the whole file at its exact version.
How to install
mdr add miklschmidt/archboard/to-tickets@git:20261025.3b43540Pins git:20261025.3b43540 in mdr.lock, 2 versions behind the newest at the top of this page.
claude plugin marketplace add https://markdownregistry.com/mp/a/art_ito3womoxdzky6m5/5c9fba69845c2519b9b35b9af42ae5142c21f8ca15ac2123dc2722002c8058ae.json
Then /plugin install to-tickets@markdownregistry-ito3womoxdzky6m5 in Claude Code. It installs git:20261025.3b43540, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add miklschmidt/archboard/to-tickets@sha256:5c9fba69845c2519The older copy line above pins the label git:20261025.3b43540, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_ito3womoxdzky6m5)
2 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: get me the newest mattpocock/skills/to-tickets, and what changed since 5c9fba6? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of to-tickets from somewhere else? Ask it: where did my to-tickets come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 1 version of this file, committed on Oct 25, 2026.
Watch this file (sign in, one email per new version)
Copies
Newest: git:20261006.9e2abf8 of to-tickets in mattpocock/skills (skills/engineering/to-tickets/SKILL.md), graded A.
This copy: byte for byte that file's version git:20260819.3216582, which it committed on Aug 19, 2026, before this repository did; graded A, 2 versions behind.
See what changed since these bytes · ask your agent
Matched on the exact bytes and the commit dates, nothing else. It does not say who wrote the file or where this repository got it.
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/to-tickets/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (5671 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
miklschmidt/archboard · 11 stars · license a license file GitHub does not identify · pushed 2026-11-18 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ito3womoxdzky6m5 GET https://markdownregistry.com/api/v1/resolve?ref=miklschmidt/archboard/to-tickets GET https://markdownregistry.com/api/v1/blob/5c9fba69845c2519b9b35b9af42ae5142c21f8ca15ac2123dc2722002c8058ae
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from miklschmidt/archboard
Every file in miklschmidt/archboard
Other files named to-tickets
Browse by kind, by grade A, or by owner.
Kept in .agents/skills, the folder Codex reads. More agent skills for Codex.