Turns "it's broken" into a clear bug report: steps to reproduce, expected and actual results, environment.
WHEN TO USE IT
When you have found a problem and want whoever fixes it to understand it first time.
Formats change. If a field stops working, check it against Anthropic's documentation.
One file. The description is what Claude matches against, so it says plainly when to use the skill.
---
name: bug-report
description: Write a clear bug report from a rough description of a problem. Use when the user wants to report a bug or file an issue.
---
Write a bug report from what the user described.
Use this structure:
**Title:** what is wrong, where, in under 80 characters.
**Steps to reproduce**
1. Numbered, starting from a clean state.
**Expected result** and **Actual result**, one line each.
**Environment:** device, browser or OS, app version, if known.
**Notes:** frequency (always, sometimes, once), and any error message
quoted exactly.
Rules:
- Ask for missing steps or the error text rather than inventing them.
- Remove passwords, tokens and personal details if the user pasted any,
and say that you did.Put the folder in your skills directory. Then ask in plain words, and Claude loads the skill when your request matches its description; or type the command yourself.
# for you, in every project
mkdir -p ~/.claude/skills/bug-report
mv SKILL.md ~/.claude/skills/bug-report/
# then, inside Claude Code, either ask naturally:
# help me write a bug report for this crash
# or run it by name:
# /bug-reportMORE SKILLS
The authority
Anthropic's documentation for Skills
This template is a starting point. Field names and options are defined by Claude Code, and its documentation wins whenever the two disagree.
https://code.claude.com/docs/en/skills