robzolkos/appsignal-cli

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