beamer-automation
Automate Beamer tasks via Rube MCP (Composio). Always search tools first for current schemas.
67
53%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./composio-skills/beamer-automation/SKILL.mdQuality
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 (Beamer via Rube MCP/Composio) but fails to explain what specific capabilities are available or when Claude should use this skill. The procedural instruction about searching tools is misplaced in a description field.
Suggestions
Add specific Beamer capabilities like 'send product announcements, manage changelog entries, create notification campaigns, track user engagement'
Add a 'Use when...' clause with natural trigger terms like 'when users mention product announcements, changelog updates, in-app notifications, or Beamer'
Remove the procedural instruction ('Always search tools first') from the description - this belongs in the skill body, not the selection-focused description
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description says 'Automate Beamer tasks' which is extremely vague - it doesn't specify what tasks can be automated (sending notifications, managing users, analytics, etc.). 'Always search tools first' is procedural guidance, not a capability description. | 1 / 3 |
Completeness | The 'what' is vague ('automate Beamer tasks') and there is no 'when' clause or explicit trigger guidance. The instruction to 'search tools first' is implementation detail, not usage guidance. | 1 / 3 |
Trigger Term Quality | Contains 'Beamer', 'Rube MCP', and 'Composio' as keywords, but these are technical/product names rather than natural user language. Missing terms users might say like 'notifications', 'announcements', 'changelog', or 'product updates'. | 2 / 3 |
Distinctiveness Conflict Risk | The specific mention of 'Beamer' and 'Rube MCP (Composio)' provides some distinctiveness, but 'automate tasks' is generic enough to potentially conflict with other automation 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 Beamer automation through Rube MCP. It excels at workflow clarity with explicit sequencing and validation steps, and maintains excellent token efficiency. The main weakness is that the tool call examples are structural templates rather than fully executable code, though this may be intentional given the dynamic nature of tool discovery.
Suggestions
Consider showing one complete end-to-end example with actual Beamer-specific tool slugs and arguments (even if noting they may change) to make the guidance more concrete
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, avoiding unnecessary explanations of what Beamer or MCP are. Every section serves a purpose and assumes Claude's competence with APIs and tool execution patterns. | 3 / 3 |
Actionability | Provides concrete tool call patterns with parameter structures, but uses pseudo-code style rather than actual executable code. The examples show structure but aren't copy-paste ready for any specific runtime environment. | 2 / 3 |
Workflow Clarity | Clear 3-step workflow pattern with explicit sequencing (discover → check connection → execute). Includes validation checkpoint for connection status and explicit guidance on when to proceed. | 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. Quick reference table provides efficient navigation for common operations. | 3 / 3 |
Total | 11 / 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 | |
- Repository
- ComposioHQ/awesome-claude-skills
- Commit
2790447
- 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.