emit-tickets SKILL.md skillA
emit-tickets from event4u-app/agent-config is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add event4u-app/agent-config/emit-tickets@git:20261102.d483573Pins git:20261102.d483573 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- event4u-app/agent-config
- Path
src/skills/emit-tickets/SKILL.md- Versions recorded
- 6
- Latest version
- git:20261102.d483573, committed Nov 2, 2026
- First version recorded
- Jun 15, 2026
- Size
- 6,947 bytes
- Repository stars
- 19
- License
- MIT
Use when materialising a roadmap into a ticket bundle — 'turn this roadmap into tickets', 'materialise tickets', 'mach Tickets aus der Roadmap', 'emit tickets for this plan'.
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
# emit-tickets
Materialise a roadmap into an `agents/tickets/{slug}/` bundle — one ticket per
buildable step — then wire the markers back and run the buildability gate.
## When to use
| Signal | Match |
|---|---|
| "turn this roadmap into tickets" | yes |
| "materialise / emit tickets for \<roadmap\>" | yes |
| "mach Tickets aus der Roadmap" | yes |
| "plan the work for \<roadmap\>" | yes |
| User wants a YAML ticket bundle, not a prose plan | yes |
| Refining or splitting an existing ticket | no → use `refine-ticket` |
| Estimating a single ticket | no → use `estimate-ticket` |
**Upstream:** `roadmap-writing` — author the roadmap first.
**Downstream:** `src/scripts/lint_ticket_buildable.ts` (the build-readiness gate). A ticket reaches a tracker by paste or MCP (ADR-102) — no export script.
## Procedure
Steps at a glance:
1. Locate and parse the roadmap.
2. Create `agents/tickets/{slug}/` and draft one ticket YAML per materializable step.
3. Assign `model_tier` via the granularity floor; split oversized steps.
4. Compute SHA refs for `adr_refs` / `source_refs`.
5. Write `manifest.yml` with acyclic `dependency_graph` and empty `linear_state`.
…Read the whole file at its exact version.
How to install
mdr add event4u-app/agent-config/emit-tickets@sha256:85488713bf74b043The line at the top of this page pins the label git:20261102.d483573, 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_cuod7hozzwblckrl)
6 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 6 versions of this file, between Jun 15, 2026 and Nov 2, 2026, about one every 28 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261102.d483573 latest | 2026-11-02 | d483573 | 6,947 B | A | view · diff |
| git:20261102.9e567e0 | 2026-11-02 | 9e567e0 | 7,305 B | A | view · diff |
| git:20260706.65fa12b | 2026-07-06 | 65fa12b | 6,454 B | A | view · diff |
| git:20260618.09b5544 | 2026-06-18 | 09b5544 | 6,448 B | A | view · diff |
| git:20260616.bdffdbb | 2026-06-16 | bdffdbb | 6,448 B | A | view · diff |
| git:20260615.3c5cc0e | 2026-06-15 | 3c5cc0e | 6,187 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 (6947 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
event4u-app/agent-config · 19 stars · license MIT · pushed 2026-11-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_cuod7hozzwblckrl GET https://markdownregistry.com/api/v1/resolve?ref=event4u-app/agent-config/emit-tickets GET https://markdownregistry.com/api/v1/blob/85488713bf74b043aa5f2cdf33741ef99aac5cc5559eef2f3bc4b1c0b0fe389a
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.