Sentry Connector for Muse
Triage errors fast — resolve, archive, or assign issues with explicit confirmation.
- What
- Triage errors fast — resolve, archive, or assign issues with explicit confirmation.
- Cost
- Free
- Needs
- A Sentry account and an auth token (sentry.io → Settings → Auth Tokens) with scopes org:read, project:read, event:read (plus event:write for resolve/archive/assign), kept in your Muse's secure vault (never paste secrets here). Note: this skill targets sentry.io (US SaaS); EU and self-hosted instances are out of scope.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
A Muse agent skill for Sentry error triage: list organizations and projects, list unresolved issues from the last 24 hours sorted by frequency, and resolve, archive, or assign issues. The write commands each need an exact --confirm string echoed by the CLI; reading needs no confirmation. Uses a Sentry auth token (org:read, project:read, event:read — plus event:write for the write commands), kept in Muse's secure vault. Targets sentry.io (US SaaS); EU and self-hosted instances are out of scope. Free tier available. Draft: written from Sentry's public API docs, not yet live-tested end-to-end — this listing's unverified status reflects that. No secrets in the repo.
Curated by Skill Harbor — free, open-source build (MIT) by @bluman1.
Version:
Install
Prerequisites: A Sentry account and an auth token (sentry.io → Settings → Auth Tokens) with scopes org:read, project:read, event:read (plus event:write for resolve/archive/assign), kept in your Muse's secure vault (never paste secrets here). Note: this skill targets sentry.io (US SaaS); EU and self-hosted instances are out of scope. No GitHub account needed unless listed here. Install "Sentry Connector for Muse" for me. A Muse agent skill for Sentry error triage: list orgs and projects, list recent unresolved issues, resolve/archive/assign with explicit confirmation. Repository: https://github.com/bluman1/muse-connectors/tree/main/connectors/sentry 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "sentry". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. save my Sentry auth token in the vault). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.