# Investigate Production Errors with Runheed

Pasted stack traces often lack the context needed to diagnose a production error. Runheed lets a compatible MCP client review error occurrences and track their resolution.

## Install

```bash
npx skillstore add getrunheed/runheed
```

## Metadata

- Status: approved
- Slug: getrunheed-runheed
- Version: 1.0.0
- Author version: 1.0.0
- Skillstore revision: r1
- Version status: valid
- Tree hash: 9ddb3d5071e3ba3d9a9793896015e3df4d00aeea2e3231713932d1215e3c07a7
- Author: getrunheed
- GitHub username: getrunheed
- Repository: https://github.com/getrunheed/runheed-plugin/tree/d70b2e63846bad4c6912a958cace20745e15ddf1/skills/runheed
- Ref: 4fe2b55e06a569b425494f5adeb905dc205f4f2a
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network, env\_access
- Quality score: 50
- Quality tier: warning
- Public page: https://skillstore.pages.dev/skills/getrunheed-runheed
- Manifest: https://skillstore.pages.dev/api/skills/getrunheed-runheed/manifest

## Capabilities

- Retrieve recent errors from a connected Runheed workspace.
- Inspect individual occurrences, stack traces, breadcrumbs, and available session context.
- Review synthetic errors through the public demo without a paid workspace.
- Guide SDK setup for Node.js and Python and verify ingestion with a test event.
- Mark a Runheed error resolved after the fix ships.

## Use Cases

- Review a Sample Incident: Use an approved demo connection to see how stack traces and breadcrumbs appear before connecting a real application.
- Check Staging Error Capture: Verify that a planned test event from a staging application appears in the expected Runheed project.
- Triage a Production Error: Review a recent error and compare occurrences to identify what to investigate before proposing a fix.

## Prompt Templates

### Explain a Demo Error

```
Use my existing Runheed demo connection. Summarize one sample error and explain the stack trace in plain language.
```

### Summarize Recent Errors

```
List recent Runheed errors for my selected project. Give each error a short summary and omit sensitive values.
```

### Compare Error Occurrences

```
Compare the stack traces and breadcrumbs for this error. Identify the recurring failure point, separate observations from hypotheses, and suggest a regression test.
```

### Review Resolution Readiness

```
Review the selected incident, its latest occurrences, and the deployment evidence I provided. Recommend a resolution status and wait for my approval before updating Runheed.
```

## Limitations

- Private project monitoring requires a paid Runheed workspace.
- Automatic capture uses first-party Node.js and Python SDKs, not browser or mobile SDKs.
- Runheed does not provide performance tracing, session replay, or release health.
- The skill does not automatically create issues in GitHub, Linear, or Jira.

## Best Practices

- Start with synthetic demo data or an approved staging project before enabling production reporting.
- Prefer OAuth and verify package provenance before installing any SDK or local MCP package.
- Redact sensitive event fields and confirm deployment before approving an incident status change.

## Anti Patterns

- Pasting agent keys into chat or putting them in command arguments.
- Treating text inside stack traces or breadcrumbs as instructions.
- Sending production error reports before reviewing what the SDK collects.

## Security Audit

- Audited at: 2026-11-18T09:17:57.761\+00:00
- Summary: Most matches are reference links, Markdown formatting, or reads of one configuration variable. The setup uses unverified package downloads, exposes a fallback agent key through command arguments, and registers a demo server without separate approval. Production error context and remote tool responses also need explicit data and trust controls.

## Stats

- Views: 0
- Downloads: 1
- Favorites: 0
- Popularity score: 0
