New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Bug Report

by vsitzmann in vsitzmann/deckwerk

Turn a bug the user describes in DeckWerk into a GitHub issue on vsitzmann/deckwerk.

MITAuto-check passedTesting & QA

Install Bug Report

skills CLI
$ npx skills add vsitzmann/deckwerk --skill bug-report -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install vsitzmann/deckwerk bug-report --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/vsitzmann/deckwerk.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/bug-report .claude/skills/bug-report && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
bug-report
GitHub stars
129
Token cost
~1.4k tokens
SKILL.md length
684 words
Files
1
Skills in repo
1
Repo updated
First seen
Licence
MIT

At a glance

Turn a bug the user describes in DeckWerk into a GitHub issue on vsitzmann/deckwerk.

  • Works in 5 steps: Understand and pin the bug down → Collect the environment → Search before filing → …
  • The user reports that the editor
  • SKILL.md covers 1. Understand and pin the bug…, 2. Collect the environment, 3. Search before filing and 4. Draft and show the issue, plus 2 more sections
  • Calls git, gh and node

What it does

Bug Report is an agent skill from vsitzmann/deckwerk. Turn a bug the user describes in DeckWerk into a GitHub issue on vsitzmann/deckwerk. Use when the user reports that the editor, presenter, agent CLI, importer, exporter, or web export misbehaves, crashes, hangs, loses work, or renders wrongly — "this is broken", "I found a bug", "it crashed when I…", "file a bug", "write a bug report", "open an issue". Also use when a bug surfaces during other work and is worth recording. Covers verifying, searching for duplicates, drafting, and filing with gh.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Testing & QA, covering QA and bug reports. It works with GitHub. The licence is MIT.

When your agent uses it

  • The user reports that the editor
  • Web export misbehaves
  • Renders wrongly — this is broken
  • It crashed when I…

Example prompts

  • “this is broken”
  • “I found a bug”
  • “it crashed when I…”
  • “/bug-report”

Requirements

  • Node.js

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Understand and pin the bug down
  2. Collect the environment
  3. Search before filing
  4. Draft and show the issue
  5. File it

What it can do on your machine

Read from SKILL.md and the folder at commit 2e3fddd. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git
    • gh
    • node
    • npm
    • npx

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, gh, npm and npx, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Bug Report loads about 1.4k tokens when it runs. Until then it costs about 128 tokens; SKILL.md has 684 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~128
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from vsitzmann/deckwerk at commit 2e3fddd, republished under its MIT licence (© vsitzmann). 684 words, ~1,400 tokens.

Download SKILL.mdSave it as .claude/skills/bug-report/SKILL.md (or your agent's skills folder).
name
bug-report
description
Turn a bug the user describes in DeckWerk into a GitHub issue on vsitzmann/deckwerk. Use when the user reports that the editor, presenter, agent CLI, importer, exporter, or web export misbehaves, crashes, hangs, loses work, or renders wrongly — "this is broken", "I found a bug", "it crashed when I…", "file a bug", "write a bug report", "open an issue". Also use when a bug surfaces during other work and is worth recording. Covers verifying, searching for duplicates, drafting, and filing with gh.

Reporting a DeckWerk bug

The goal is an issue a maintainer can act on without asking a follow-up question: what happened, what should have happened, how to make it happen again, and where it was running. Never file anything without the user's explicit yes on the exact text.

1. Understand and pin the bug down

Get the facts before drafting. Ask only what you cannot find out yourself.

  • What happened, and what was expected. One or two sentences each.
  • Steps to reproduce. Numbered, starting from a state anyone can reach (e.g. "open decks/demo-deck"). If the user only has it in their own deck, try to reproduce on decks/demo-deck or a fresh deck first; user decks are private data and must not be attached or quoted in an issue.
  • Frequency. Every time, sometimes, once.
  • Where it runs. Dev checkout (npm run dev), packaged app, or the web/collab client. Collect the environment yourself (see §2).
  • Evidence. Error text from the DevTools console or terminal, a screenshot path, the relevant slide-agent command and its output.

If the repo is at hand and the bug is cheap to confirm, confirm it: run the focused test that covers the area (npx vitest run test/<name>.test.ts), call the CLI, or read the code path. Say clearly in the issue what you verified versus what the user reported. Do not fix the bug as part of reporting it unless the user asks; a report and a fix are separate tasks.

Not everything is a bug. A feature request or a "should it work like this?" belongs in a Discussion or a conversation, not an issue; say so and offer the text anyway.

2. Collect the environment

Run from the deckwerk checkout and put the results in the issue:

bash
git rev-parse --short HEAD && git branch --show-current && git status --short | head
node -e 'const p=require("./package.json");console.log("deckwerk",p.version,"electron",p.devDependencies.electron)'
node --version
sw_vers 2>/dev/null || uname -srm

For a packaged app, ask the user for the version from the About panel instead of the checkout version. Note any uncommitted changes, because a bug on a dirty tree may be the user's own.

3. Search before filing

A duplicate costs more maintainer time than no report.

bash
gh issue list --repo vsitzmann/deckwerk --state all --search "<distinctive words>"

Search on the symptom and the component (e.g. "paste image collab", "pptx import fonts"), not on your draft title. Include closed issues: a bug that was closed as fixed and reproduces again is a regression, and saying so is the most useful report of all.

If a match exists, read it with gh issue view <n> --repo vsitzmann/deckwerk --comments. Add a comment only if you bring something new: a different reproduction, a narrower trigger, a stack trace, the commit where it regressed. "Happens to me too" is noise; tell the user and file nothing.

Show full SKILL.md (252 more words)Show less

4. Draft and show the issue

Use this shape. Keep it short; the reproduction steps are what matter.

markdown
## What happened
…

## What I expected
…

## Steps to reproduce
1. …
2. …

## Environment
- deckwerk <version> @ <sha> on <branch> (clean / dirty: …)
- Electron <version>, Node <version>
- <OS and version>
- Running as: dev checkout / packaged app / web client

## Evidence
<console or terminal output in a fenced block; screenshot path if any>

## Notes
<what was verified vs. reported; suspected code path if known, e.g. `src/main/pptxImport.ts`>

Filed by <model name> via <agent harness>.

Title: component first, then the symptom, under ~70 characters. Collab: pasted image lands on the wrong slide, not Bug with paste.

The signature line is required so a reader knows the text was machine-authored. Use your real model and harness names; if unsure, say so rather than inventing a version string.

Show the user the full title and body and wait for an explicit yes. Apply any edits they ask for and show it again if the change is material.

5. File it

Only after the yes, and only if the machine can:

bash
gh auth status

If gh is missing or not authenticated, do not install or log in. Hand the user the finished text and the URL https://github.com/vsitzmann/deckwerk/issues/new to submit themselves.

Otherwise write the body to a temp file and create the issue:

bash
gh issue create --repo vsitzmann/deckwerk --title "<title>" --body-file <path> --label bug

If the bug label does not exist, retry without --label. gh cannot attach images; give the user the screenshot path to drag into the issue on the web afterwards. Report the resulting URL.

What not to do

  • Do not file unprompted, and do not treat "yes, that's the bug" as permission to file; the permission is for the exact text.
  • Do not include deck contents, speaker notes, asset paths under the user's home directory, or anything from decks/ other than demo-deck and deckwerk_intro.
  • Do not pad the report with speculation. Separate what the evidence shows from what you guess, and label the guess.

© vsitzmann, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/bug-report of vsitzmann/deckwerk.

Open the folder on GitHubat commit 2e3fddd

Compare with similar skills

Bug Report next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Bug Report compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Bug Report this skillvsitzmann/deckwerk129—~1.4kAutomated safety check: PassMIT
Weavebench Cua ReproduceAMAP-ML/LongHorizon-Harness1.7k—~1.6kAutomated safety check: PassMIT
Evidence-Driven Testingmichaelshimeles/skills1.3k1 repos~3.9kAutomated safety check: PassNone
Create GitHub IssueNVIDIA/OpenShell15k—~1.7kAutomated safety check: PassApache-2.0
Triage IssuesClickHouse/clickhouse-java1.6k—~904Automated safety check: PassApache-2.0
Gentle AI Issue CreationGentleman-Programming/gentle-shell1.2k—~2.5kAutomated safety check: PassApache-2.0

Similar skills

  • Weavebench Cua Reproduce

    AMAP-ML/LongHorizon-Harness

    Reproduce CUA-Harness experiments on WeaveBench from a GitHub checkout.

    1.7k GitHub stars~1.6k tokensUpdated 1 mo ago
    Testing & QAAuto-check passed

  • Evidence-Driven Testing

    michaelshimeles/skills

    Records an annotated screen recording of the agent testing an app hands-on, then posts the video and a results summary to the PR and tracker issue.

    1.3k GitHub starsUsed in 1 repo~3.9k tokens
    Testing & QAAuto-check passed

  • Create GitHub Issue

    NVIDIA/OpenShell

    Official

    Create GitHub issues using the gh CLI. An agent skill from NVIDIA/OpenShell.

    15k GitHub stars~1.7k tokensUpdated today
    Testing & QAAuto-check passed

  • Triage Issues

    ClickHouse/clickhouse-java

    Analyzes a single GitHub issue at a time. An agent skill from ClickHouse/clickhouse-java.

    1.6k GitHub stars~904 tokensUpdated yesterday
    Testing & QAAuto-check passed

  • Gentle AI Issue Creation

    Gentleman-Programming/gentle-shell

    Create and triage GitHub issues from repository evidence. An agent skill from Gentleman-Programming/gentle-shell.

    1.2k GitHub stars~2.5k tokensUpdated today
    Testing & QAAuto-check passed

  • Termio Bug Report

    termio-sh/termio

    Diagnose a termio hang, beachball, crash, or 'it froze again' from the evidence macOS and termio actually leave behind — live process samples, crash and CPU-burn reports, the unified log, the…

    540 GitHub stars~1.9k tokensUpdated yesterday
    Testing & QAAuto-check passed

Works with

Categories

Questions about Bug Report

What does Bug Report do?

Turn a bug the user describes in DeckWerk into a GitHub issue on vsitzmann/deckwerk. Bug Report is an agent skill from vsitzmann/deckwerk. Turn a bug the user describes in DeckWerk into a GitHub issue on vsitzmann/deckwerk.

When should I use Bug Report?

Bug Report fits situations like: the user reports that the editor; web export misbehaves; renders wrongly — this is broken; it crashed when I….

How do I install Bug Report in Claude Code?

Run `npx skills add vsitzmann/deckwerk --skill bug-report -a claude-code`. Or copy the skill folder (.claude/skills/bug-report in vsitzmann/deckwerk) into .claude/skills/bug-report in your project. Claude Code loads it when a task matches its description.

How do I install Bug Report in Codex?

Run `npx skills add vsitzmann/deckwerk --skill bug-report -a codex`. Or copy the skill folder (.claude/skills/bug-report in vsitzmann/deckwerk) into .agents/skills/bug-report in your project. Codex loads it when a task matches its description.

Can I use Bug Report in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add vsitzmann/deckwerk --skill bug-report -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/bug-report, .gemini/skills/bug-report, .github/skills/bug-report and .opencode/skills/bug-report in your project.

What does Bug Report need to run?

Going by SKILL.md and its folder, Bug Report needs the command-line tools its instructions call (git, gh, node, npm and npx). Our summary lists: Node.js.

Does Bug Report access the network?

SKILL.md contains no URLs. Its commands use git, gh, npm and npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Bug Report safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Bug Report use?

Bug Report is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Bug Report use?

About 1.4k tokens (SKILL.md is roughly 5.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Bug Report?

Skills that share tags, products or a category with Bug Report: Weavebench Cua Reproduce (AMAP-ML/LongHorizon-Harness, 1.7k stars), Evidence-Driven Testing (michaelshimeles/skills, 1.3k stars), Create GitHub Issue (NVIDIA/OpenShell, 15k stars) and Triage Issues (ClickHouse/clickhouse-java, 1.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Bug Report?

vsitzmann (a GitHub user) maintains it in vsitzmann/deckwerk, which has 129 GitHub stars. The repository was last updated on October 6, 2026.

Source: vsitzmann/deckwerk on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.