pp-sentry

Manage Sentry organizations, projects, incidents, and observability data via API.

1.9k|565|Updated Mar 28, 2026
One-click install
npx skills add https://github.com/mvanhorn/printing-press-library --skill pp-sentry
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pp-sentry
Source: https://github.com/mvanhorn/printing-press-library/tree/main/cli-skills/pp-sentry
Command: npx skills add https://github.com/mvanhorn/printing-press-library --skill pp-sentry

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enables structured access and management of Sentry observability data, reducing the difficulty of API interactions and manual data handling.

Core Features & Use Cases

  • Inventory Management: List and retrieve details of Sentry organizations, projects, issues, and teams.
  • Data Export and Search: Export data to JSON or CSV for offline analysis, and perform local searches and SQL queries.
  • Use Case: An engineer wants to quickly list all projects in their organization and export error data for further analysis.

Quick Start

Use the sentry skill to list all organizations accessible to your token.

Frequently Asked Questions about pp-sentry

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I export Sentry error data to CSV or JSON for offline analysis?

You can export Sentry observability data to CSV or JSON for offline analysis using structured commands that retrieve issues, projects, and incidents, reducing manual API interactions and data handling.

Can I run local SQL queries against my Sentry monitoring data?

Yes, you can perform local searches and SQL queries against exported Sentry data, enabling structured access to organizations, projects, issues, and teams without direct API calls.

What is the best way to list all projects and teams in a Sentry organization?

The best way to list Sentry projects and teams is using structured inventory commands that retrieve details directly from your organization via the API, streamlining monitoring workflows.

Does this approach require direct Sentry API knowledge to manage incidents?

No, it reduces the difficulty of API interactions by providing structured commands to manage Sentry incidents and observability data, abstracting manual API handling.

What are the limitations of exporting Sentry issues locally?

Exporting Sentry issues locally requires a valid API token for access, and large exports may need offline SQL querying and local search to manage the exported JSON or CSV data effectively.