CtrlK
BlogDocsLog inGet started
Tessl Logo

sentry-automation

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.

Install with Tessl CLI

npx tessl i github:davepoon/buildwithclaude --skill sentry-automation
What are skills?

74

Does it follow best practices?

Validation for skill structure

SKILL.md
Review
Evals

Evaluation results

95%

47%

On-Call Error Investigation Runbook

Issue investigation workflow and setup sequence

Criteria
Without context
With context

RUBE_SEARCH_TOOLS first

0%

80%

RUBE_MANAGE_CONNECTIONS setup

0%

100%

LIST_AN_ORGANIZATIONS_ISSUES required first

50%

100%

Correct investigation tool sequence

50%

100%

Organization slug format

100%

100%

Issue ID vs Event ID distinction

100%

100%

Query syntax examples

100%

100%

sort parameter values

0%

100%

statsPeriod parameter

0%

100%

Cursor-based pagination

100%

100%

RETRIEVE_ISSUE_TAG_DETAILS mentioned

0%

100%

Events have different stack traces note

40%

40%

Without context: $0.5115 · 2m 15s · 27 turns · 536 in / 8,021 out tokens

With context: $0.3175 · 1m 32s · 13 turns · 175 in / 5,038 out tokens

98%

49%

Sentry Alert Rules Setup Guide

Alert rule creation and project slug resolution

Criteria
Without context
With context

RUBE_SEARCH_TOOLS mentioned

0%

100%

RUBE_MANAGE_CONNECTIONS prerequisite

0%

100%

RETRIEVE_ORGANIZATION_PROJECTS first

41%

100%

Project slug vs display name

40%

100%

Two distinct alert rule types

75%

100%

actionMatch must be explicit

80%

100%

frequency in minutes

100%

100%

frequency alert fatigue warning

85%

100%

List existing rules step

62%

100%

conditions/actions/filters schemas

28%

71%

UPDATE_ORGANIZATION_ALERT_RULES mentioned

0%

100%

Organization slug format

40%

100%

Without context: $0.4316 · 2m 54s · 28 turns · 984 in / 6,512 out tokens

With context: $0.2758 · 1m 9s · 14 turns · 426 in / 3,437 out tokens

90%

26%

Release Tracking Automation for CI/CD Pipeline

Release lifecycle management workflow

Criteria
Without context
With context

RUBE_SEARCH_TOOLS step

0%

57%

LIST_ORGANIZATION_RELEASES first

37%

100%

CREATE_RELEASE_FOR_ORGANIZATION tool

37%

100%

projects array for multi-project

58%

100%

Unique version constraint

100%

100%

Deploy is separate from create

100%

100%

CREATE_RELEASE_DEPLOY_FOR_ORG tool

37%

100%

environment parameter for deploy

100%

100%

Source maps require release to exist first

100%

100%

dateReleased or version parameter

100%

100%

UPDATE_RELEASE_DETAILS mentioned

0%

0%

Organization slug format

66%

100%

Without context: $0.2530 · 1m 15s · 15 turns · 82 in / 4,225 out tokens

With context: $0.3388 · 1m 14s · 16 turns · 269 in / 4,136 out tokens

Evaluated
Agent
Claude Code

Table of Contents

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.