How do I install the Bug Report skill?

Run npx skillmds@latest add cadrianmae/bug-report in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Bug Report safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Bug Report?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Bug Report free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Bug Report?

cadrianmae (@cadrianmae) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Bug Report by cadrianmae — Agent Skill

Name: Bug Report
Rating: 4.666666666666667 (3 reviews)
Author: cadrianmae

Bug Report

This skill should be used when the user asks to "file a bug", "report a bug", "log a bug", "create a bug issue", or mentions a marketplace plugin bug that should be tracked. Files bug reports as GitHub issues on cadrianmae/claude-marketplace.

cadrianmae Updated Sep 10, 2026

File contents

File a Bug Report

File a bug report as a GitHub issue on cadrianmae/claude-marketplace. This is for logging only — do NOT attempt to fix the bug in this session.

Quick Example

/cadrianmae-issues:bug cron plugin - schedule matching fails for weekly expressions

Workflow

Ask 1-2 clarifying questions if the description is unclear:
- What were the steps to reproduce?
- What was expected vs what actually happened?
Determine which marketplace plugin is affected — infer from conversation context, the description, or ask the user
Compose the issue title and body using the template below
Create the issue with gh issue create
Confirm the issue URL and return to the user's current work

Labels

Always apply bug
If a specific plugin is affected, also apply plugin:<name> (e.g. plugin:cron, plugin:tts)

Issue Creation

After gathering details, compose the issue and file it:

gh issue create \
    --repo cadrianmae/claude-marketplace \
    --title "<concise bug title>" \
    --body "<issue body>" \
    --label bug \
    --label "plugin:<name>"

Issue Body Template

## Description
<clarified description>

## Steps to Reproduce
<from clarifying questions, or 'Not specified' if user skipped>

## Expected Behaviour
<from clarifying questions, or 'Not specified' if user skipped>

---
Plugin: <plugin name or n/a>
Date: <YYYY-MM-DD>

After Filing

Respond with the issue URL, e.g.: "Bug filed: https://github.com/cadrianmae/claude-marketplace/issues/42. Continuing with your current work."

Return focus to whatever the user was working on before this command.

---name: bug-reportdescription: This skill should be used when the user asks to "file a bug", "report a bug", "log a bug", "create a bug issue", or mentions a marketplace plugin bug that should be tracked. Files bug reports as GitHub issues on cadrianmae/claude-marketplace.---# File a Bug ReportFile a bug report as a GitHub issue on `cadrianmae/claude-marketplace`. This is for logging only — do NOT attempt to fix the bug in this session.## Quick Example```bash/cadrianmae-issues:bug cron plugin - schedule matching fails for weekly expressions```## Workflow1. Ask 1-2 clarifying questions if the description is unclear: - What were the steps to reproduce? - What was expected vs what actually happened?2. Determine which marketplace plugin is affected — infer from conversation context, the description, or ask the user3. Compose the issue title and body using the template below4. Create the issue with `gh issue create`5. Confirm the issue URL and return to the user's current work## Labels- Always apply `bug`- If a specific plugin is affected, also apply `plugin:<name>` (e.g. `plugin:cron`, `plugin:tts`)## Issue CreationAfter gathering details, compose the issue and file it:```bashgh issue create \ --repo cadrianmae/claude-marketplace \ --title "<concise bug title>" \ --body "<issue body>" \ --label bug \ --label "plugin:<name>"```### Issue Body Template```markdown## Description<clarified description>## Steps to Reproduce<from clarifying questions, or 'Not specified' if user skipped>## Expected Behaviour<from clarifying questions, or 'Not specified' if user skipped>---Plugin: <plugin name or n/a>Date: <YYYY-MM-DD>```## After FilingRespond with the issue URL, e.g.:"Bug filed: https://github.com/cadrianmae/claude-marketplace/issues/42. Continuing with your current work."Return focus to whatever the user was working on before this command.

Frequently asked questions