next-ticket SKILL.md skillA
next-ticket from doodledood/manifest-dev is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add doodledood/manifest-dev/next-ticket@git:20261108.b3711f7Pins git:20261108.b3711f7 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- doodledood/manifest-dev
- Path
claude-plugins/manifest-dev/skills/next-ticket/SKILL.md- Versions recorded
- 13
- Latest version
- git:20261108.b3711f7, committed Nov 8, 2026
- First version recorded
- Aug 12, 2026
- Size
- 9,074 bytes
- Repository stars
- 78
- License
- MIT
Read the project''s Ticket store, choose the single best Ticket for the human-plus-AI session to work on now, claim it, and present it with the reason it leads. Use when asking what''s next, what should I work on, or pulling the next Ticket from the backlog. Selection stops after presentation; execution belongs to run-ticket or the person holding the claim.
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
# next-ticket Find the store, read it, name one ticket. The store follows the ticket convention (`../ticket-up/references/TICKET_CONVENTION.md` — read it if the convention isn't already in context), and every state a Ticket is in and every move it makes, a pick and its claim among them, is `../ticket-up/references/AUTOMATED_EXECUTION.md` → *Transitions* — read that section too. **Finding the store.** Read `tickets/store-config.md` — one fixed, repo-relative location naming the venue. A GitHub-venue config means the store is that repo's issues under the efforts' tracking issues; query instead of reading files. A project that deliberately keeps its store elsewhere says so in its own context file, already loaded when you run. Without either, look before asking: if no store exists anywhere, say so plainly and offer the two ways one appears — `ticket-up` on a finished manifest, or writing tickets by hand under the convention — since a project with no work tracked yet needs a store, not a question about which kind. Where something is there, don't assume which venue it is, not even when `tickets/<effort>/` directories are sitting in front of you, since a project whose store moved to a… …
Read the whole file at its exact version.
How to install
mdr add doodledood/manifest-dev/next-ticket@sha256:49a32b02b1dacebaThe line at the top of this page pins the label git:20261108.b3711f7, 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_rcyqgaggftesk6j3)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 13 versions of this file, between Aug 12, 2026 and Nov 8, 2026, about one every 7 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261108.b3711f7 latest | 2026-11-08 | b3711f7 | 9,074 B | A | view · diff |
| git:20261107.aed92e6 | 2026-11-07 | aed92e6 | 9,064 B | A | view · diff |
| git:20261025.d5ed8ec | 2026-10-25 | d5ed8ec | 8,658 B | A | view · diff |
| git:20261023.438b677 | 2026-10-23 | 438b677 | 8,856 B | A | view · diff |
| git:20261021.af0c096 | 2026-10-21 | af0c096 | 8,746 B | A | view · diff |
| git:20261021.eb17749 | 2026-10-21 | eb17749 | 7,834 B | A | view · diff |
| git:20261021.849b1bb | 2026-10-21 | 849b1bb | 7,853 B | A | view · diff |
| git:20261018.ef6b7cf | 2026-10-18 | ef6b7cf | 7,664 B | A | view · diff |
| git:20260905.7f3e60f | 2026-09-05 | 7f3e60f | 7,600 B | A | view · diff |
| git:20260825.f208ed9 | 2026-08-25 | f208ed9 | 7,481 B | A | view · diff |
| git:20260820.5bb949c | 2026-08-20 | 5bb949c | 6,872 B | A | view · diff |
| git:20260814.9115515 | 2026-08-14 | 9115515 | 6,217 B | A | view · diff |
| git:20260812.a685a9a | 2026-08-12 | a685a9a | 5,800 B | A | view |
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 (9074 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
doodledood/manifest-dev · 78 stars · license MIT · pushed 2026-11-08 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_rcyqgaggftesk6j3 GET https://markdownregistry.com/api/v1/resolve?ref=doodledood/manifest-dev/next-ticket GET https://markdownregistry.com/api/v1/blob/49a32b02b1daceba5345f0227417c16ac05317e59800edde6359d206c01c969b
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.