CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/sentry-automation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, highly actionable MCP orchestration guide whose tool slugs, parameters, and pitfalls capture genuinely non-obvious knowledge. Its main weaknesses are systematic duplication (pitfalls repeated across three sections plus a redundant table), missing verification steps in mutating workflows, and a monolithic single-file layout with no progressive disclosure of detail.

Suggestions

Consolidate the ID-format and slug pitfalls into the single "Known Pitfalls" section and remove their repetition from each workflow's pitfalls block, the Common Patterns section, and the vacuous closing "When to Use" section.

Add verification checkpoints to mutating workflows, e.g., after `SENTRY_CREATE_PROJECT_RULE_FOR_ALERTS` retrieve the rule via `SENTRY_RETRIEVE_ALERT_RULE_DETAILS` to confirm it was created with the intended conditions, and list releases after creating one.

Provide a concrete minimal `conditions`/`actions` JSON example for alert-rule creation instead of deferring to Sentry docs, and consider moving the per-workflow tool detail into a references file so SKILL.md stays a lean overview with the Quick Reference table.

DimensionReasoningScore

Conciseness

Most content earns its tokens (exact tool slugs, parameter names, Sentry query syntax Claude cannot know), but pitfalls are repeated across three places (per-workflow "Pitfalls", "Common Patterns", and "Known Pitfalls" — e.g., the slug-vs-display-name warning appears four times), the Quick Reference table restates the workflows, and the closing "When to Use" section is pure filler ("applicable to execute the workflow or actions described in the overview"). This is more than minor trimming, so it sits at anchor 3 rather than 4.

3 / 5

Actionability

The guidance is highly concrete for an instruction-only skill: exact tool names, [Required]/[Optional] sequencing, real parameter names, and worked examples like `is:unresolved` and `statsPeriod: 24h`. It is not 5 because alert-rule creation defers the critical `conditions`/`actions`/`filters` JSON schemas to external Sentry docs rather than providing concrete examples, leaving the hardest step under-specified.

4 / 5

Workflow Clarity

Sequences are clearly ordered with prerequisite/required tags and the setup flow has an explicit validation gate ("Confirm connection status shows ACTIVE"), but the mutating workflows — creating alert rules, updating monitors, creating releases — include no verification or error-recovery checkpoints (e.g., retrieve the created rule, list releases to confirm). Steps are present but validation gaps match anchor 3, not 4.

3 / 5

Progressive Disclosure

The skill is a single ~230-line file with no bundle files: all six detailed workflows, parameter catalogs, and a 15-row tool table are inlined in SKILL.md. Sections are well-organized, but this is essentially a full API reference inline (matching anchor 3's example of ~200 lines of reference that belongs in a separate file) rather than a lean overview pointing one level deep, so it does not reach anchor 4.

3 / 5

Total

13

/

20

Passed

Description

70%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A solid, specific description with strong distinctiveness, but it is missing any 'when to use' trigger guidance and lacks natural trigger variations like 'errors', 'crashes', or 'error tracking'. Adding an explicit use-when clause would materially raise its routing reliability.

Suggestions

Add an explicit trigger clause, e.g., "Use when the user mentions Sentry, error tracking, crashes, alert rules, or release tracking."

Include natural user vocabulary such as "errors", "crashes", "stack traces", and "error monitoring" alongside the existing domain terms.

Replace the generic lead "Automate Sentry tasks" with a more concrete verb phrase like "Manage Sentry issues, alerts, releases, and monitors" to sharpen specificity.

DimensionReasoningScore

Specificity

"manage issues/events, configure alerts, track releases, monitor projects and teams" lists several specific domain actions with only minor gaps. It is not 5 because "Automate Sentry tasks" and "monitor projects and teams" stay at the domain level without concrete operations (e.g., viewing stack traces or creating rules), and not 3 because well more than 1-2 concrete actions are named.

4 / 5

Completeness

The "what" is clear (automating Sentry issue/alert/release/project operations via Rube MCP), but there is no "Use when..." clause or equivalent explicit trigger guidance; the second sentence ("Always search tools first for current schemas") is procedural, not a trigger. Per the rubric guideline, a missing 'when' clause caps completeness at 3.

3 / 5

Trigger Term Quality

The description carries good natural keywords ("Sentry", "issues", "alerts", "releases", "projects", "teams") but misses common variations users would naturally say such as "errors", "crashes", "error tracking", or "stack traces". Anchor 4 ("good keyword coverage; a few natural terms missing") is the closest fit.

4 / 5

Distinctiveness Conflict Risk

"Sentry" plus "Rube MCP (Composio)" defines a clear niche with distinct triggers and minimal overlap risk with other skills. It clearly matches the anchor-5 example pattern of a specific toolchain with dedicated triggers, not the minor-overlap anchor 4.

5 / 5

Total

16

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

skills/sentry-automation/SKILL.md

Reviewed

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.