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-automation74
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
67%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 effectively communicates specific Sentry automation capabilities and is highly distinctive due to explicit tool naming. However, it lacks explicit trigger guidance ('Use when...') and could benefit from more natural user-facing keywords like 'error tracking' or 'crash reports' that users would actually say when needing this skill.
Suggestions
Add a 'Use when...' clause with trigger scenarios like 'Use when the user asks about Sentry, error tracking, crash reports, or exception monitoring'
Include natural user terms like 'error tracking', 'crash reports', 'exceptions', 'bug monitoring' alongside the technical Sentry terminology
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'manage issues/events, configure alerts, track releases, monitor projects and teams'. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers 'what' with specific Sentry automation tasks, but lacks an explicit 'Use when...' clause. The instruction 'Always search tools first' is operational guidance, not trigger guidance for when to select this skill. | 2 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Sentry', 'issues', 'events', 'alerts', 'releases', but missing common user variations like 'error tracking', 'crash reports', 'exceptions', or 'bug monitoring' that users might naturally say. | 2 / 3 |
Distinctiveness Conflict Risk | Very distinct with 'Sentry' and 'Rube MCP (Composio)' as clear identifiers. The specific domain of error monitoring/tracking is unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
70%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides comprehensive coverage of Sentry automation workflows with excellent structure and clear sequencing. However, it lacks executable code examples - relying on tool names and parameter descriptions rather than concrete API call syntax. The content is somewhat verbose with repeated pitfall information across sections.
Suggestions
Add executable code examples showing actual tool invocations with sample parameters (e.g., a complete RUBE_SEARCH_TOOLS call with expected response format)
Consolidate repeated pitfall information into the 'Known Pitfalls' section to reduce redundancy across workflow sections
Replace pseudocode in 'Common Patterns' with concrete, copy-paste ready examples showing actual parameter values
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundancy - pitfalls are repeated across sections, and the quick reference table duplicates information already covered in workflows. Some sections could be tightened. | 2 / 3 |
Actionability | Provides tool names and parameter lists, but lacks executable code examples. The 'ID Resolution' patterns show pseudocode-style steps rather than actual API calls with concrete syntax. No copy-paste ready examples. | 2 / 3 |
Workflow Clarity | Workflows are clearly sequenced with numbered steps, explicit [Required]/[Optional]/[Prerequisite] markers, and each workflow includes pitfalls section for error awareness. The setup section has clear validation checkpoints. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections: Prerequisites, Setup, Core Workflows, Common Patterns, Known Pitfalls, and Quick Reference. External toolkit docs are linked. Content is appropriately structured for a comprehensive skill. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- 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.