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.

59

Quality

68%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/sentry-automation/SKILL.md

The canonical home for this skill is sentry-automation in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

67%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.

The body is well-structured and actionable for an MCP integration skill, with clear sequenced workflows and concrete tool/parameter guidance. Its main weakness is redundancy (the Quick Reference table and the empty 'When to Use' section) that could be trimmed.

Suggestions

Remove or replace the generic 'When to Use' filler line with concrete trigger guidance.

Consider condensing the Quick Reference table since its contents duplicate the per-workflow tool sequences already documented above.

DimensionReasoningScore

Conciseness

Mostly efficient and free of concept over-explanation, but the Quick Reference table duplicates the tool lists already given in each workflow and the trailing 'When to Use' section is a content-free filler line.

3 / 5

Actionability

Provides concrete tool slugs, named parameters, and example values (e.g., query syntax, sort options) that are the executable form for an MCP skill, though it stops short of full example tool-call payloads.

4 / 5

Workflow Clarity

Six numbered workflows each carry 'When to use', sequenced tool calls with [Required]/[Optional]/[Prerequisite] markers, and the Setup section has an explicit validation checkpoint (confirm ACTIVE); minor verification gaps exist within the create/deploy workflows.

4 / 5

Progressive Disclosure

Well-organized into clear sections (Prerequisites, Setup, Core Workflows, Common Patterns, Known Pitfalls, Quick Reference) with no nested references and appropriate structure, though the filler 'When to Use' section and duplicated table are minor organization gaps.

4 / 5

Total

15

/

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.

The description is specific and well-scoped to Sentry automation with strong distinctiveness, but it omits any explicit 'when to use' trigger guidance, which caps completeness. Voice is correctly third person.

Suggestions

Add an explicit 'Use when...' clause naming natural trigger phrases (e.g., 'Use when the user wants to triage Sentry errors, set up alerts, or track releases').

Drop or de-emphasize the technical 'Rube MCP (Composio)' framing in favor of user-facing terms to improve trigger term quality.

DimensionReasoningScore

Specificity

Lists several concrete actions ('manage issues/events, configure alerts, track releases, monitor projects and teams') but stops short of full coverage (no mention of deploys, source maps, or monitors).

4 / 5

Completeness

Has a clear 'what' but no 'Use when...' clause or equivalent explicit trigger guidance, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

Natural keywords users would say are present ('Sentry', 'issues', 'alerts', 'releases', 'projects and teams') with good coverage, though it lacks natural trigger synonyms and the 'Rube MCP (Composio)' phrasing is technical jargon.

4 / 5

Distinctiveness Conflict Risk

Clearly scoped to Sentry via Rube MCP with distinct triggers, giving it a clear niche with minimal conflict risk against other skills.

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.

Validation15 / 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
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.