CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

bugsnag-automation

Automate Bugsnag tasks via Rube MCP (Composio). 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 ./composio-skills/bugsnag-automation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 compact, well-structured automation skill that gives concrete tool-call patterns, a clear sequenced workflow with connection validation, and a useful pitfalls section. Main weaknesses are repeated instructions across sections and placeholder arguments rather than fully worked call examples.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — no explanation of what Bugsnag or MCP is, and every section carries actionable content. Minor trimming is possible since 'Always search first' and 'Check connection' are each repeated across Prerequisites, Tool Discovery, the workflow steps, and Known Pitfalls.

4 / 5

Actionability

Concrete call blocks are given for RUBE_SEARCH_TOOLS, RUBE_MANAGE_CONNECTIONS, and RUBE_MULTI_EXECUTE_TOOL with realistic parameter shapes, plus a Quick Reference table mapping operations to tool calls. The examples contain placeholders (e.g. 'tool_slug: "TOOL_SLUG_FROM_SEARCH"', 'arguments: {/* schema-compliant args */}') rather than copy-paste-ready values, though the skill explicitly justifies this because schemas are dynamic.

4 / 5

Workflow Clarity

The three-step Core Workflow Pattern (discover → check connection → execute) is clearly sequenced, and the Setup section includes validation checkpoints ('If connection is not ACTIVE, follow the returned auth link', 'Confirm connection status shows ACTIVE before running any workflows'). A minor gap: no post-execution verification of tool results is specified.

4 / 5

Progressive Disclosure

No bundle files exist, and the ~85-line body is well organized into Prerequisites, Setup, Tool Discovery, Core Workflow, Pitfalls, and a Quick Reference table with easy navigation. It exceeds the under-50-line simple-skill threshold, so perfect marks don't apply, but nothing here clearly belongs in a separate file.

4 / 5

Total

16

/

20

Passed

Description

52%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 identifies a distinctive niche (Bugsnag automation via Rube MCP) but is thin: it names no concrete capabilities, includes no 'use when' trigger guidance, and misses natural synonyms users would say. The procedural 'Always search tools first' sentence occupies space that capabilities or triggers should fill.

Suggestions

List concrete capabilities instead of 'tasks', e.g. 'Retrieve Bugsnag error events, crash reports, and release stability data; manage projects and releases.'

Add an explicit trigger clause, e.g. 'Use when the user mentions Bugsnag, error monitoring, crash reports, or exception tracking.'

Move the 'Always search tools first for current schemas' instruction into the body — it is workflow guidance, not a capability, and crowds the description.

DimensionReasoningScore

Specificity

'Automate Bugsnag tasks' names the domain but the action is generic — no concrete capabilities (e.g. retrieving error events, managing projects, viewing releases) are listed. 'Always search tools first for current schemas' is procedural guidance, not a capability, and the sentence is in third person so no voice penalty applies.

2 / 5

Completeness

The 'what' is stated reasonably clearly (automate Bugsnag operations via Rube MCP), but there is no 'Use when...' clause or any equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

'Bugsnag' is a natural, relevant keyword a user would say, but the description misses common variations and synonyms such as 'errors', 'crashes', 'exceptions', 'error monitoring', or 'stability'. 'Rube MCP (Composio)' is technical jargon rather than user language.

3 / 5

Distinctiveness Conflict Risk

'Bugsnag' is a unique product name giving the skill a clear niche with distinct triggers and minimal conflict risk — no other skill category would plausibly match a Bugsnag-related request.

5 / 5

Total

13

/

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

ComposioHQ/awesome-claude-skills

Path

composio-skills/bugsnag-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.