adrapid-automation
Automate Adrapid tasks via Rube MCP (Composio). Always search tools first for current schemas.
69
53%
Does it follow best practices?
Impact
97%
6.46xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./composio-skills/adrapid-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 be useful for skill selection. It names products/tools but fails to explain what specific tasks can be automated or when Claude should select this skill. The lack of concrete actions and explicit trigger guidance makes it difficult to distinguish from other automation-related skills.
Suggestions
Add specific concrete actions that can be performed (e.g., 'Create ad banners, generate creative variations, manage campaigns').
Add a 'Use when...' clause with explicit triggers (e.g., 'Use when the user mentions Adrapid, ad creation, banner automation, or Composio integrations').
Replace vague 'Automate Adrapid tasks' with enumerated capabilities that describe what the automation actually does.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'Automate Adrapid tasks' without specifying what concrete actions can be performed. 'Always search tools first' is procedural guidance, not a capability description. | 1 / 3 |
Completeness | The 'what' is extremely vague ('Automate Adrapid tasks') and there is no 'when' clause or explicit trigger guidance. The description fails to answer either question adequately. | 1 / 3 |
Trigger Term Quality | Contains some relevant keywords ('Adrapid', 'Rube MCP', 'Composio') but these are technical/product names rather than natural terms users would say. Missing common variations or task-oriented language. | 2 / 3 |
Distinctiveness Conflict Risk | The specific product names (Adrapid, Rube MCP, Composio) provide 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 guides Claude through Adrapid automation via Rube MCP. The workflow is clear with proper validation checkpoints, and the content respects token budget. The main weakness is that tool call examples use placeholder syntax rather than fully executable examples, though this may be intentional given the dynamic nature of tool schemas.
Suggestions
Provide at least one complete, executable example with real tool slugs and arguments (even if noting they may change) to demonstrate the full pattern
Add an example of handling pagination in the workflow section since it's mentioned as a pitfall but not demonstrated
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, avoiding unnecessary explanations of what Adrapid or Composio are. Every section serves a purpose with no padding or redundant context. | 3 / 3 |
Actionability | Provides concrete tool call patterns with parameter examples, but uses pseudo-code style rather than fully executable code. The argument placeholders like '/* schema-compliant args from search results */' require inference rather than being copy-paste ready. | 2 / 3 |
Workflow Clarity | Clear 3-step workflow with explicit sequencing (discover → check connection → execute). Includes validation checkpoint for connection status ('Confirm connection status shows ACTIVE before running any workflows') and known pitfalls section addresses error prevention. | 3 / 3 |
Progressive Disclosure | Well-structured with clear sections progressing from prerequisites to setup to workflow to pitfalls. External reference to toolkit docs is one level deep and clearly signaled. 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.