Automate Sentry tasks via Rube MCP (Composio): manage issues/events, configure alerts, track releases, monitor projects and teams. Always search tools first for current schemas.
57
66%
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 ./plugins/all-skills/skills/sentry-automation/SKILL.mdLow
Low-risk findings.
2 low severity findings. Worth noting, but not necessarily harmful.
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.
The required runtime workflow calls Rube MCP Sentry toolkit tools (e.g., `SENTRY_LIST_AN_ORGANIZATIONS_ISSUES` / `SENTRY_GET_ORGANIZATION_ISSUE_DETAILS`) which return issue/event text authored by other parties (Sentry issue/event content originates from external application users/clients and is not authored by the operating user), and that returned free text is ingested into the agent’s LLM context.
The skill fetches instructions or code from an external URL at runtime, and the fetched content directly controls the agent’s prompts or executes code. This dynamic dependency allows the external source to modify the agent’s behavior without any changes to the skill itself.
The skill requires adding and using https://rube.app/mcp as the MCP server and explicitly instructs to call RUBE_SEARCH_TOOLS at runtime to fetch current tool schemas from that endpoint, which directly control agent tool prompts/instructions.
b79ed72
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.