writing-tickets SKILL.md skillA

writing-tickets from jcottam/agent-resources is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add jcottam/agent-resources/writing-tickets@v1.0.0

Pins v1.0.0 in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
jcottam/agent-resources
Path
skills/productivity/writing-tickets/SKILL.md
Versions recorded
1
Latest version
v1.0.0, committed Oct 24, 2026
Size
3,810 bytes
Repository stars
21
License
MIT

Write or rewrite an issue tracker ticket (Linear, GitHub Issues, Jira, or similar) that a person or coding agent will pick up. States the objective, evidence, decisions already made, hard rules, and done criteria, and leaves the how to the implementer. Use when the user says "write a ticket", "file an issue", "create a Linear issue", "open a GitHub issue", "rewrite this ticket", "turn this into a ticket", or any variation of wanting a task written up for someone else to implement.

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

# Writing Tickets

A ticket sets up whoever picks it up, whether a person or a coding agent, to succeed. It says **what** needs to happen and **why**, not **how**. The implementer is closest to the code and decides the approach.

This matters even more for AI agents, which take tickets literally: every step you list is something they build, whether or not it still makes sense once they're in the code. Prescriptive tickets add bloat, unintended behavior, and things that later have to be ripped out.

## Before writing

1. Do light discovery only: read the error, the failing log, the relevant file or two, and the recent commits. The goal is to get the problem and its evidence right, not to design the fix.
2. Find out what's already decided. Ask the requester if a choice that matters is still open (for example, which version, which vendor, or what's in or out of scope).

## Sections

Use these sections in this order and skip any that would be empty.

- **Objective.** One or two sentences on the outcome we want and why it matters.
…

Read the whole file at its exact version.

How to install

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_w5qyzm7hoa5tc2z3/a22f87c900a9907f4a8e3b534746c18568c4cb08839def44abb74c6dddac1d46.json

Then /plugin install writing-tickets@markdownregistry-w5qyzm7hoa5tc2z3 in Claude Code. It installs v1.0.0, the one graded A here, pinned to the commit it was graded at, and leaves it there.

The exact contents, by fingerprint
mdr add jcottam/agent-resources/writing-tickets@sha256:a22f87c900a9907f

The line at the top of this page pins the label v1.0.0, 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.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_w5qyzm7hoa5tc2z3.svg)](https://markdownregistry.com/a/art_w5qyzm7hoa5tc2z3)

1 badge image fetches in 30 days. What the badge shows.

Ask from your agent
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry

Then ask it: what changed in jcottam/agent-resources/writing-tickets since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.

Got a copy of writing-tickets from somewhere else? Ask it: where did my writing-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 24, 2026.

Watch this file (sign in, one email per new version)

versioncommittedcommitsizeaudit
v1.0.0 latest2026-10-24 3bf1385 3,810 BA view
Keep it current by itself, install once

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.

Install on GitHub

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.

Keep it current by itself

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.

Check a whole project

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

A  17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • pass: Frontmatter block present
  • pass: Frontmatter declares a name
  • pass: Frontmatter declares a description
  • pass: Size between 200 bytes and 200 KB (3810 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

GitHub

jcottam/agent-resources · 21 stars · license MIT · pushed 2026-11-17 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_w5qyzm7hoa5tc2z3
GET https://markdownregistry.com/api/v1/resolve?ref=jcottam/agent-resources/writing-tickets
GET https://markdownregistry.com/api/v1/blob/a22f87c900a9907f4a8e3b534746c18568c4cb08839def44abb74c6dddac1d46

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 jcottam/agent-resources

AGENTS.md AGENTS.md file
jcottam/agent-resources · AGENTS.md
git:20260514.905ef91 · audit A · 21 stars
CLAUDE.md CLAUDE.md file
jcottam/agent-resources · CLAUDE.md
git:20260514.905ef91 · audit B · 21 stars
content-wireframe SKILL.md skill
jcottam/agent-resources · skills/design/content-wireframe/SKILL.md · Draft a content wireframe for a website or page before any design or code. Produces a structured markdown document with…
git:20260530.a60d20b · audit A · 21 stars
babysit-pr SKILL.md skill
jcottam/agent-resources · skills/engineering/babysit-pr/SKILL.md · Babysit review comments on the current branch's pull request. Bugbot comes first: wait for its review, fix each valid…
v1.2.0 · audit A · 21 stars
new-project SKILL.md skill
jcottam/agent-resources · skills/engineering/new-project/SKILL.md · Kickstart a new project by interviewing for context, choosing Astro or Next.js and extras, then scaffolding a barebones…
v0.2.0 · audit A · 21 stars
orient SKILL.md skill
jcottam/agent-resources · skills/engineering/orient/SKILL.md · Orient a developer to an unfamiliar codebase by systematically exploring its structure, purpose, features, conventions…
v1.0.0 · audit A · 21 stars
promote-skill SKILL.md skill
jcottam/agent-resources · skills/engineering/promote-skill/SKILL.md · Move a tested personal agent skill into a shared skills repository, check for overlap, normalize metadata, update the…
v1.0.0 · audit A · 21 stars
review-pr SKILL.md skill
jcottam/agent-resources · skills/engineering/review-pr/SKILL.md · Forensic, stage-aware pull request review. Reconstructs the commit narrative, tests architectural premises against…
v4.0.0 · audit A · 21 stars
ship SKILL.md skill
jcottam/agent-resources · skills/engineering/ship/SKILL.md · Validate a branch, run quality gates, update documentation and changelog, and open a pull request. Supports GitHub…
v1.6.0 · audit A · 21 stars
squash-branch SKILL.md skill
jcottam/agent-resources · skills/engineering/squash-branch/SKILL.md · Review commits in a branch, date range, or recent history; group related work into a clean linear history; and verify…
v1.0.0 · audit A · 21 stars
release-notes SKILL.md skill
jcottam/agent-resources · skills/productivity/release-notes/SKILL.md · Summarize a logical grouping of git commits into plain-language release notes for non-technical readers. Use when the…
v1.1.0 · audit A · 21 stars
host SKILL.md skill
jcottam/agent-resources · skills/publishing/host/SKILL.md · Upload files to Cloudflare R2 and return a shareable public URL. Supports any file type (HTML, images, PDFs, etc.) with…
v1.2.0 · audit A · 21 stars

Every file in jcottam/agent-resources

Browse by kind, by grade A, or by owner.