home / skills / robzolkos / appsignal-cli / appsignal

appsignal skill

safe

This skill helps you diagnose AppSignal errors by fetching incidents and samples and guiding debugging steps for faster resolution.

npx playbooks add skill robzolkos/appsignal-cli --skill appsignal

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

2.9 KB

---
name: appsignal
description: Fetch and analyze AppSignal error incidents. Use when debugging errors, investigating exceptions, or when the user mentions AppSignal, incidents, or error monitoring.
argument-hint: "[incidents|samples] [command] [options]"
allowed-tools: Bash(appsignal-cli *)
---

# AppSignal CLI

Use the `appsignal-cli` CLI to fetch error incidents and samples from AppSignal for debugging and analysis.

## Prerequisites

Ensure `APPSIGNAL_TOKEN` and `APPSIGNAL_APP_ID` environment variables are set, or a `.appsignal-cli.yaml` config file exists.

## Common Workflows

### Investigate Recent Errors

```bash
# List open incidents
appsignal-cli incidents list

# Get details for a specific incident
appsignal-cli incidents get <number>
```

### Filter Incidents

```bash
# By state: open, closed, wip
appsignal-cli incidents list --state open

# By namespace: web, background, frontend
appsignal-cli incidents list --namespace web

# By date (ISO 8601)
appsignal-cli incidents list --since 2024-01-15

# By minimum occurrences
appsignal-cli incidents list --min-occurrences 10

# Combine filters
appsignal-cli incidents list --namespace background --min-occurrences 5
```

### Get Detailed Error Information

```bash
# Standard detail view
appsignal-cli incidents get <number>

# With params and session data
appsignal-cli --verbose incidents get <number>

# Export as markdown for analysis
appsignal-cli incidents export <number> -o error-report.md
```

### Work with Error Samples

```bash
# List recent error samples
appsignal-cli samples list --limit 10

# Get full sample details (params, session, environment)
appsignal-cli samples get <sample-id>
```

### Manage Incidents

```bash
# Close a resolved incident
appsignal-cli incidents close <number>

# Reopen if issue recurs
appsignal-cli incidents reopen <number>
```

## Output Formats

Use `--compact` for token-efficient output when analyzing errors:

```bash
appsignal-cli --compact incidents list
appsignal-cli --compact incidents get <number>
```

Use `--json` for structured data:

```bash
appsignal-cli --json incidents list
```

## Debugging Steps

When asked to debug an AppSignal error:

1. **List incidents** to find the relevant error
2. **Get incident details** including backtrace
3. **Analyze the backtrace** to identify the root cause
4. **Find the relevant code** in the codebase
5. **Propose a fix** based on the error context

## Available Commands

| Command | Description |
|---------|-------------|
| `apps` | List all applications |
| `incidents list` | List error incidents |
| `incidents get <n>` | Get incident details |
| `incidents close <n>` | Close an incident |
| `incidents reopen <n>` | Reopen an incident |
| `incidents export <n>` | Export to markdown |
| `samples list` | List error samples |
| `samples get <id>` | Get sample details |
| `config show` | Show current config |
| `config init` | Initialize config file |
| `config set <k> <v>` | Set config value |

Overview

This skill lets you fetch and analyze AppSignal error incidents and samples from the command line. It helps quickly find recent exceptions, inspect backtraces and request/session data, and export reports for debugging. Use it to speed up root-cause analysis and incident management for services monitored by AppSignal.

How this skill works

The skill runs the appsignal-cli tool to list incidents, retrieve incident details, and fetch error samples. It supports filters (state, namespace, date, minimum occurrences) and output modes (--compact for token-efficient text, --json for structured data, export to Markdown). It can also perform incident management actions like closing or reopening incidents and show or initialize configuration.

When to use it

Investigating a new or recurring error reported by AppSignal
When you need backtraces, params, and session data to reproduce a bug
Filtering incidents by state, namespace, date, or occurrence count
Exporting an incident report to share with the team
Listing recent error samples to triage noisy errors

Best practices

Ensure APPSIGNAL_TOKEN and APPSIGNAL_APP_ID are set or run config init before using the CLI
Start with incidents list and apply filters to narrow candidates before fetching details
Use --compact for concise output in conversational analysis and --json when you need structured data
Fetch samples get and use verbose mode for params and session context when reproducing issues
Export incidents to Markdown for ticketing systems or post-mortem notes

Example use cases

List open incidents in the web namespace from the last month to prioritize work
Get the full backtrace and session data for incident #42 to identify the failing method
Filter incidents with min-occurrences >= 10 to find high-impact errors
Export an incident to error-report.md and attach it to an issue tracker
Close an incident after deploying a confirmed fix, or reopen if it recurs

FAQ

What credentials does the skill need?

Set APPSIGNAL_TOKEN and APPSIGNAL_APP_ID in the environment or run config init to create a .appsignal-cli.yaml with the credentials.

How can I get compact, token-efficient output for analysis?

Run commands with --compact to reduce verbosity, or use --json when you need structured output for tooling.