sentry
Fetch and analyze Sentry issues, events, transactions, and logs. Helps agents debug errors, find root causes, and understand what happened at specific times.
65
77%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Low
Low-risk findings worth noting
Fix and improve this skill with Tessl
tessl review fix ./skills/sentry/SKILL.mdLow
Low-risk findings.
1 low severity finding. Worth noting, but not necessarily harmful.
W011: Third-party content exposure detected (indirect prompt injection risk).
What this means
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
Why it was flagged
Required workflow in `fetch-event.js`/`fetch-issue.js`/`search-events.js`/`search-logs.js` calls Sentry’s REST API at runtime and then converts outsider-authored event/issue/log fields (message, request body, exception stack, breadcrumbs) into readable text via `formatEvent`/`formatIssue`/`formatLogEntry` and prints them (potentially to be included in the agent’s LLM context by the runtime harness).
- Repository
- mitsuhiko/agent-stuff
- Commit
d265b8e
- Audited
- Security analysis
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.