AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Triage Bug

skill-spencerpauly-skills-repo-triage-bug · by spencerpauly

Take a raw bug report and turn it into a clean, prioritized ticket with a title, repro steps, and severity. Use when the user says "triage this", pastes a support escalation, or asks "what's this bug".

↗ Website ↗ Repository
— No reviews yet
0 installs
36 views
0.0% view→install

Install

$ agentstack add skill-spencerpauly-skills-repo-triage-bug

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-spencerpauly-skills-repo-triage-bug)

Reliability & compatibility

✓ Security review passed
0 installs to date
— no reviews yet
○ 4mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Triage Bug? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Triage Bug

Convert a noisy bug report into a ticket someone can act on: one-line title, repro steps, severity, area.

When to use

  • Support escalates a bug.
  • A teammate dumps a Slack thread or screenshot.
  • The user says "triage this" or "what's this bug".

Steps

  1. Re-read the report once, in full. Don't start writing yet.
  2. Restate the symptom in one sentence as a user would say it. No internal jargon.
  3. Pull out repro steps even if the original report doesn't separate them. Number them 1, 2, 3.
  4. Note the gap between expected and actual.
  5. Decide severity with this rubric:
  • S1 — production down, data loss, or security issue.
  • S2 — common path broken, no workaround.
  • S3 — broken with workaround.
  • S4 — cosmetic / rare path.
  1. Identify the area (one of: editor, billing, auth, api, infra, marketing).

Output format

## Title

## Severity
S2

## Area
billing

## Repro
1. ...
2. ...
3. ...

## Expected vs actual
- Expected: ...
- Actual: ...

## Notes
- URLs, screenshots, affected user IDs.

Don't

  • Don't open with "I think the issue is..." — the title goes first.
  • Don't skip severity. Every ticket gets one, even if it's a guess.
  • Don't paste raw stack traces into the title. Summarize.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Agent Skills