better-stack-automation

Automate Better Stack tasks via Rube MCP (Composio). Always search tools first for current schemas.

Quality

53%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./composio-skills/better-stack-automation/SKILL.md

Quality

Discovery

22%

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

This description is too vague to effectively guide skill selection. It names the integration (Better Stack via Rube MCP/Composio) but fails to specify what capabilities are available or when the skill should be triggered. The meta-instruction about searching tools first is operational guidance that doesn't help Claude decide when to select this skill.

Suggestions

Add specific capabilities: list concrete actions like 'create monitors', 'manage incidents', 'configure status pages', 'set up alerting rules'

Add a 'Use when...' clause with natural trigger terms like 'uptime monitoring', 'incident response', 'status page', 'Better Stack', 'server monitoring'

Remove or relocate the meta-instruction 'Always search tools first for current schemas' to the skill body - it's implementation detail, not selection criteria

Dimension	Reasoning	Score
Specificity	The description says 'Automate Better Stack tasks' which is extremely vague - it doesn't specify what tasks can be automated (monitoring, alerting, incident management, etc.). The only concrete action mentioned is 'search tools first' which is meta-guidance, not a capability.	1 / 3
Completeness	The 'what' is extremely weak ('automate tasks' is not specific), and there is no 'Use when...' clause or equivalent trigger guidance. The instruction to 'search tools first' is implementation guidance, not usage context.	1 / 3
Trigger Term Quality	Includes 'Better Stack', 'Rube MCP', and 'Composio' as identifiable terms, but lacks natural user language. Users might say 'monitoring', 'uptime', 'incidents', 'alerts', or 'status pages' - none of which appear here.	2 / 3
Distinctiveness Conflict Risk	'Better Stack' and 'Rube MCP (Composio)' provide some distinctiveness as specific product names, but 'automate tasks' is generic enough to potentially conflict with other automation or Composio-based skills.	2 / 3
	Total	6 / 12 Passed

Implementation

85%

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

This is a well-structured skill that efficiently teaches Better Stack automation through Rube MCP. It excels at workflow clarity with explicit validation steps and provides good progressive disclosure. The main weakness is that tool call examples use placeholder syntax rather than fully concrete, executable examples with realistic argument values.

Suggestions

Replace placeholder comments like '/* schema-compliant args from search results */' with concrete example arguments for a common Better Stack operation (e.g., creating a monitor)

Add one complete end-to-end example showing a real workflow from search to execution with actual tool slugs and arguments

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient, avoiding unnecessary explanations of what Better Stack or Composio are. Every section serves a purpose and assumes Claude understands the underlying concepts.	3 / 3
Actionability	Provides concrete tool call patterns with specific parameters, but uses pseudo-code style rather than fully executable examples. The argument placeholders like '/* schema-compliant args from search results */' reduce copy-paste readiness.	2 / 3
Workflow Clarity	Clear 3-step workflow pattern with explicit validation checkpoint (check connection status shows ACTIVE before proceeding). The Known Pitfalls section provides error prevention guidance and the sequence is unambiguous.	3 / 3
Progressive Disclosure	Well-organized with clear sections progressing from prerequisites to setup to workflow to pitfalls. External reference to Composio docs is one level deep and clearly signaled. Quick reference table aids navigation.	3 / 3
	Total	11 / 12 Passed

Validation

90%

Warnings & errors only

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

Repository: ComposioHQ/awesome-claude-skills
Commit: 2790447

Reviewed: 2 months ago

Table of Contents

Discovery Implementation Validation

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.