ticket-trim SKILL.md skillA
ticket-trim from ehnruiz/claude-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add ehnruiz/claude-skills/ticket-trim@git:20261012.f7b3bf1Pins git:20261012.f7b3bf1 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- ehnruiz/claude-skills
- Path
skills/ticket-trim/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261012.f7b3bf1, committed Oct 12, 2026
- Size
- 2,437 bytes
- Repository stars
- 3
- License
- MIT
Shorten an existing ticket that is too long or too technical, moving the engineering detail into a Technical notes comment so nothing is lost. Use when the user gives a ticket key or link and asks to trim, condense, simplify or clean it up, or says a product owner or analyst found it hard to read.
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
# Ticket trim
Reshape one existing ticket to the `ticket-write` shape: a short plain-language description, the detail in a `Technical notes` comment. The budgets, the templates and the lint script are in the `ticket-write` skill's folder.
## Steps
1. **Read the ticket** in full, with its comments and any acceptance-criteria field. Note its type, its reporter, and whether it has images, mentions or checklists, which must survive the rewrite. If someone else reported it, say so before changing anything.
2. **Sort every sentence.**
- **Keep**: the effect, why it matters, outcomes someone can check, scope, links. These become the new description.
- **Move**: root causes, file paths, function names, config keys, phased plans, verification steps. These become the technical notes.
- **Link out**: anything that is really a document, such as a multi-phase plan with a decision log. Do this only with the user's agreement, since it creates a page.
Rewrite acceptance criteria that name an implementation ("retry with backoff") as the outcome ("a short outage shows no error to visitors"). Keep a long criterion when it is long because it is precise.
…Read the whole file at its exact version.
How to install
mdr add ehnruiz/claude-skills/ticket-trim@sha256:5ae911f6afcfc637The line at the top of this page pins the label git:20261012.f7b3bf1, 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_ouyutikpkozt7urz)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 12, 2026.
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 (2437 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
ehnruiz/claude-skills · 3 stars · license MIT · pushed 2026-10-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ouyutikpkozt7urz GET https://markdownregistry.com/api/v1/resolve?ref=ehnruiz/claude-skills/ticket-trim GET https://markdownregistry.com/api/v1/blob/5ae911f6afcfc637164999b2e4ff6b95df8a547a99775417714c3476537484a7
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.