debug-sentry-monitor SKILL.md skillA
This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.
debug-sentry-monitor from kensaurus/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add kensaurus/skills/debug-sentry-monitor@git:20261001.3fce9fbPins git:20261001.3fce9fb in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- kensaurus/skills
- Path
skills/debug-sentry-monitor/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261001.3fce9fb, committed Oct 1, 2026
- First version recorded
- Sep 23, 2026
- Size
- 17,250 bytes
- Repository stars
- 9
- License
- MIT
Operate Sentry: triage and fix unresolved issues, cut noise, audit instrumentation, monitor after deploy. Use when "check Sentry" or "review production errors". One bug → workflow-fix-and-ship. Plan-only audit → plan-error-handling.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Sentry Monitor **Degree of freedom: MIXED.** Triage bucket and root cause `[HIGH freedom]`; resolve-only-after-verify `[LOW freedom — run exactly]`. Triage, fix, and audit Sentry on any project via the `sentry` MCP. Auto-detects config. ## How to reason 1. **Observe** — issue type, frames, users, first-seen, release 2. **Interpret** — app frame vs extension noise; new vs regression 3. **Classify** — Noise / Code Bug / Data Bug / Performance / Regression / Config Gap 4. **Severity** — regressions and multi-user crashes first; never resolve Performance ## Worked example > **Observe:** 80 events of `TypeError: undefined.email` on `/account`, started at release `1.14.0`. > **Interpret:** app frames in the profile card; correlates with the onboarding PR. > **Classify:** Data Bug + Regression — API null for incomplete profiles. > **Fix:** handle null at the contract; do not resolve until the fix is committed and the loop is green. ## Self-critique before reporting - **No resolve without proof** — issue stays unresolved if the fix is unverified - **No band-aid** — `?.` / swallowed catch is not the sole fix - **Bucket is one** — Noise is not used to mute an app-frame crash …
Read the whole file at its exact version.
How to install
mdr add kensaurus/skills/debug-sentry-monitor@sha256:c75b401b082a3cd1The line at the top of this page pins the label git:20261001.3fce9fb, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_ajemtlqzl7ablb3m)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Sep 23, 2026 and Oct 1, 2026, about one every 2 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261001.3fce9fb latest | 2026-10-01 | 3fce9fb | 17,250 B | A | view · diff |
| git:20260926.c7354ac | 2026-09-26 | c7354ac | 17,277 B | A | view · diff |
| git:20260923.938ff43 | 2026-09-23 | 938ff43 | 17,298 B | A | view · diff |
| git:20260923.68c095e | 2026-09-23 | 68c095e | 16,190 B | A | view · diff |
| git:20260923.cf348bd | 2026-09-23 | cf348bd | 17,031 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (17250 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
kensaurus/skills · 9 stars · license MIT · pushed 2026-10-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ajemtlqzl7ablb3m GET https://markdownregistry.com/api/v1/resolve?ref=kensaurus/skills/debug-sentry-monitor GET https://markdownregistry.com/api/v1/blob/c75b401b082a3cd1420673a72f2f89752e1dd3160bc9fd78954275334619a411
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from kensaurus/skills
Every file in kensaurus/skills