New: 98,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 eric-tramel in eric-tramel/moraine

Help prepare and, only with explicit user approval, file a sanitized Moraine bug report for reproducible defects in Moraine itself.

Apache-2.0Auto-check passedTesting & QA

Install Bug Report

skills CLI
$ npx skills add eric-tramel/moraine --skill bug-report -a claude-code

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

GitHub CLI
$ gh skill install eric-tramel/moraine 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/eric-tramel/moraine.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/moraine/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
117
Token cost
~1.4k tokens
SKILL.md length
604 words
Files
1
Skills in repo
19
Repo updated
First seen
Licence
Apache-2.0

At a glance

Help prepare and, only with explicit user approval, file a sanitized Moraine bug report for reproducible defects in Moraine itself.

  • Works in 4 steps: Identify the affected Moraine surface:… → Check whether the behavior is… → Separate Moraine defects from… → …
  • Tasks that involve QA and bug reports
  • SKILL.md covers Destination, Consent Boundary, Privacy Rules and Triage, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Bug Report is an agent skill from eric-tramel/moraine. Help prepare and, only with explicit user approval, file a sanitized Moraine bug report for reproducible defects in Moraine itself.

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 repository describes itself as: Unified realtime agent trace database & search MCP. The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve QA and bug reports

Example prompts

  • “/bug-report”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Identify the affected Moraine surface: CLI, setup, ingest source, monitor,
  2. Check whether the behavior is reproducible or has enough evidence to debug.
  3. Separate Moraine defects from user-specific environment problems. A missing
  4. Prefer a small sanitized reproducer over broad environment dumps.

What it can do on your machine

Read from SKILL.md and the folder at commit 2fb4aec. 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

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown and bash).

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

  • Network

    No URLs in SKILL.md.

    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 36 tokens; SKILL.md has 604 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~36
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 eric-tramel/moraine at commit 2fb4aec, republished under its Apache-2.0 licence (© eric-tramel). 604 words, ~1,388 tokens.

Download SKILL.mdSave it as .claude/skills/bug-report/SKILL.md (or your agent's skills folder).
name
bug-report
description
Help prepare and, only with explicit user approval, file a sanitized Moraine bug report for reproducible defects in Moraine itself.

Bug Report

Use this skill when the user hit a likely Moraine defect and wants help turning it into a useful GitHub issue. A Moraine bug is a reproducible problem in the Moraine CLI, ingest, monitor, MCP server, setup flow, packaging, documentation, or bundled plugins.

Do not use this skill for general support, one-off local setup help, unrelated agent-harness issues, or private debugging that cannot be generalized into a Moraine repository issue. Troubleshoot those locally instead, and file a report only if the evidence points to a fixable Moraine defect.

Destination

The Moraine repository is:

text
https://github.com/eric-tramel/moraine

New bug reports go through GitHub Issues:

text
https://github.com/eric-tramel/moraine/issues/new

If a GitHub issue tool, browser, or gh is available, use it only after the user explicitly confirms the final redacted report. If no posting tool is available, provide the issue URL and the prepared report body.

Never silently post an issue on the user's behalf. Even if the user says "file it", first show the final sanitized title and body, then ask for explicit confirmation before creating the issue. If the user declines, stop after providing the draft.

Do not upload logs, configs, screenshots, session transcripts, or command output without the same explicit confirmation.

Privacy Rules

All bug reports must anonymize PII and host-specific details before they leave the user's machine.

Redact or generalize:

  • Usernames, hostnames, emails, organization names, repo names, client names, and internal project names.
  • Exact absolute paths such as home directories, workspace roots, socket paths, and temp directories.
  • Secrets, tokens, API keys, cookies, auth headers, database URLs, and credentials.
  • Private prompts, agent transcripts, file contents, logs, or screenshots unless the user explicitly approves a minimal sanitized excerpt.
  • Exact host environment details that fingerprint the machine. Prefer broad labels like "macOS on Apple Silicon", "Linux x86_64", "Homebrew install", or "uv tool install" instead of full hardware, hostname, local account, or full directory layouts.

Use placeholders such as <home>, <repo>, <project>, <host>, <workspace>, <token>, and <private transcript omitted>.

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

Triage

Before drafting a report, determine whether the issue belongs in the Moraine repo:

  1. Identify the affected Moraine surface: CLI, setup, ingest source, monitor, MCP search, ClickHouse schema, packaging, documentation, Codex plugin, Claude Code plugin, Hermes plugin, or another bundled integration.
  2. Check whether the behavior is reproducible or has enough evidence to debug.
  3. Separate Moraine defects from user-specific environment problems. A missing local dependency, local permissions issue, custom shell setup, broken external harness install, or private repo configuration is usually support unless Moraine handles it incorrectly or gives a misleading failure.
  4. Prefer a small sanitized reproducer over broad environment dumps.

Report Structure

Draft reports in this shape:

markdown
## Summary

One or two sentences describing the Moraine bug and affected surface.

## Affected Area

- Moraine component: CLI | setup | ingest | monitor | MCP | packaging | docs | plugin
- Harness, if relevant: Codex | Claude Code | Hermes | OpenCode | Cursor | Kimi CLI | Pi Coding Agent | other
- Install method, if relevant: release bundle | uv tool | Homebrew | source checkout | unknown

## Version

- Moraine version: output of `moraine --version`, if available
- Broad platform: sanitized OS and architecture category only

## Steps To Reproduce

1. Minimal first step.
2. Minimal second step.
3. Command or action that triggers the bug, with paths and private names replaced.

## Expected Behavior

What Moraine should have done.

## Actual Behavior

What happened instead, including the sanitized error message or symptom.

## Sanitized Evidence

Short redacted excerpts only. Replace private values with placeholders.

## Workaround

Known workaround, if any.

## Notes

Any suspected regression range, related issue, or additional context that does
not expose private data.

Evidence Collection

Ask before running commands that may read local state. Prefer narrow commands whose output can be summarized and redacted, such as:

bash
moraine --version
moraine status
moraine logs --lines 100

When logs are useful, include only the shortest sanitized excerpt that explains the failure. Do not include full session content or full config files. Summarize config shape instead of posting exact values.

If prior agent context matters and Moraine MCP tools are available, use the current harness's Moraine search tools to recover the relevant session or error, then apply the same redaction rules before drafting the issue.

Posting Workflow

  1. Draft a sanitized title and body using the report structure.
  2. Point out any assumptions or missing reproduction details.
  3. Ask the user whether they want to post it to GitHub.
  4. If they say yes, show the final redacted report and ask for explicit posting confirmation.
  5. Create the GitHub issue only after that confirmation, then return the issue URL.
  6. If they do not confirm, leave them with the draft and the new-issue URL.

© eric-tramel, Apache-2.0. 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 plugins/moraine/skills/bug-report of eric-tramel/moraine.

Open the folder on GitHubat commit 2fb4aec

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 skilleric-tramel/moraine117—~1.4kAutomated safety check: PassApache-2.0
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/OpenShell16k—~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.

    16k 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 today
    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…

    537 GitHub stars~1.9k tokensUpdated today
    Testing & QAAuto-check passed

More from eric-tramel/moraine

All 19 skills in this repo

  • Moraine Release Publisher

    eric-tramel/moraine

    Cuts and publishes a Moraine release end to end: version bump PR, tag, GitHub release notes, workflow check and PyPI package verification.

    117 GitHub stars~2.5k tokensUpdated 4 days ago
    Auto-check passed

  • Moraine Release Notes

    eric-tramel/moraine

    Rewrites a moraine GitHub release body into a usage-focused format with install block, what's new, platform table, upgrade notes and one deduplicated changelog.

    117 GitHub stars~2.7k tokensUpdated 4 days ago
    Auto-check passed

  • Multi-Persona Code Review

    eric-tramel/moraine

    Coordinates a delegated review of a Moraine PR or local change by seven focused reviewer subagents, merges their findings and follows up on the fixes.

    117 GitHub stars~1.3k tokensUpdated 4 days ago
    Auto-check passed

  • Elegance-Focused Code Review

    eric-tramel/moraine

    Looks at a pull request for the smallest good design, hunting for simplifications and architectural moves that remove whole classes of problems.

    117 GitHub stars~473 tokensUpdated 4 days ago
    Auto-check passed

  • Idiomatic Code Review

    eric-tramel/moraine

    Reviews a pull request for idiomatic implementation: use of the language, standard library, ecosystem conventions and the repository's own patterns.

    117 GitHub stars~469 tokensUpdated 4 days ago
    Auto-check passed

  • Code Review Security Review

    eric-tramel/moraine

    Review a PR through the CodeReviewSecurityReview persona. An agent skill from eric-tramel/moraine.

    117 GitHub stars~497 tokensUpdated 4 days ago
    Auto-check passed

Works with

Categories

Questions about Bug Report

What does Bug Report do?

Help prepare and, only with explicit user approval, file a sanitized Moraine bug report for reproducible defects in Moraine itself. Bug Report is an agent skill from eric-tramel/moraine. Help prepare and, only with explicit user approval, file a sanitized Moraine bug report for reproducible defects in Moraine itself.

When should I use Bug Report?

Bug Report fits situations like: tasks that involve QA and bug reports.

How do I install Bug Report in Claude Code?

Run `npx skills add eric-tramel/moraine --skill bug-report -a claude-code`. Or copy the skill folder (plugins/moraine/skills/bug-report in eric-tramel/moraine) 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 eric-tramel/moraine --skill bug-report -a codex`. Or copy the skill folder (plugins/moraine/skills/bug-report in eric-tramel/moraine) 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 eric-tramel/moraine --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?

SKILL.md names no scripts, command-line tools or credentials: Bug Report is instructions for the agent only.

Does Bug Report access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. 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 Apache-2.0 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, 16k 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?

eric-tramel (a GitHub user) maintains it in eric-tramel/moraine, which has 117 GitHub stars. The repository holds 19 skills in this directory. The repository was last updated on October 5, 2026.

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