cs-bug-report SKILL.md skillA
cs-bug-report from polar-bear-org/claude-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add polar-bear-org/claude-skills/cs-bug-report@git:20261026.a2f0899Pins git:20261026.a2f0899 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- polar-bear-org/claude-skills
- Path
packs/ai-for-customer-service-pack/skills/cs-bug-report/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261026.a2f0899, committed Oct 26, 2026
- First version recorded
- Sep 27, 2026
- Size
- 5,126 bytes
- Repository stars
- 51
- License
- a license file GitHub does not identify
Turns a customer ticket into a bug report engineering can act on, with steps to reproduce, expected and actual result, impact and customers affected, urgency, a workaround and what the customer was told. Use for "run cs-bug-report", "bug report template", "write a bug report from this ticket", "escalate to engineering", "engineering ignores my escalations", "steps to reproduce", "turn this ticket into a bug", part of the AI for Customer Service Pack by 90n.
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
# Bug Report Template ## When To Use I escalate a ticket and it just sits because engineering cannot act on it. The report says "customer says checkout is broken", engineering cannot recreate it, and the ticket dies in the backlog while support keeps apologising. Use this to answer: what does engineering need to recreate, size and prioritise this defect today. ## When Not To Use If many customers are hit at once by an outage, use Incident Communication Plan; a bug report is one defect handed to engineering, not a message to everyone. If you are not sure the ticket is a defect at all, check it against the Escalation Matrix entry criteria first. ## Inputs - The ticket thread (anonymised), screenshots or error text - What you tried to reproduce it, and on what version, browser or device - How many similar tickets you have, and what the customer was promised If you have none of this, I start from the ticket text alone and mark the output as a first draft with "not yet reproduced" at the top. ## Approach …
Read the whole file at its exact version.
How to install
mdr add polar-bear-org/claude-skills/cs-bug-report@sha256:5bb43cf27ac86f40The line at the top of this page pins the label git:20261026.a2f0899, 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_5uggd2m6wj7kvbrn)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Sep 27, 2026 and Oct 26, 2026, about one every 29 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261026.a2f0899 latest | 2026-10-26 | a2f0899 | 5,126 B | A | view · diff |
| git:20260927.63d5f36 | 2026-09-27 | 63d5f36 | 5,078 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 (5126 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
polar-bear-org/claude-skills · 51 stars · license a license file GitHub does not identify · pushed 2026-10-26 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_5uggd2m6wj7kvbrn GET https://markdownregistry.com/api/v1/resolve?ref=polar-bear-org/claude-skills/cs-bug-report GET https://markdownregistry.com/api/v1/blob/5bb43cf27ac86f406d24c8f2dccd80a7a589413d3eebac388d6d8482710171bd
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.