api-labz-automation
Automate API Labz 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/api-labz-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 and lacks essential components for effective skill selection. It names specific tools/products but fails to explain what concrete actions the skill performs or when it should be triggered. The description reads more like an internal note than a functional skill description.
Suggestions
Add a 'Use when...' clause specifying trigger conditions, such as 'Use when the user mentions API Labz, Composio integration, or needs to automate API workflows'
Replace 'Automate API Labz tasks' with specific concrete actions like 'Create API endpoints, manage authentication, execute API calls, handle webhooks'
Move procedural guidance ('Always search tools first') to the skill body and use the description space for capability and trigger information
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'Automate API Labz tasks' without specifying what concrete actions are performed. 'Always search tools first' is procedural guidance, not a capability description. | 1 / 3 |
Completeness | The 'what' is extremely vague ('Automate API Labz tasks') and there is no 'Use when...' clause or equivalent trigger guidance explaining when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Contains some relevant keywords ('API Labz', 'Rube MCP', 'Composio') but these are technical/product-specific terms. Missing natural language terms users might actually say when needing this skill. | 2 / 3 |
Distinctiveness Conflict Risk | The specific product names (API Labz, 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 API Labz 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 concrete, executable examples.
Suggestions
Replace placeholder comments like '/* schema-compliant args from search results */' with a concrete example showing actual field names and values for a common API Labz operation
Add a complete end-to-end example showing a real API Labz task from search through execution with actual response handling
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, avoiding explanations of basic concepts. Every section serves a purpose with no padding or unnecessary context about what APIs or MCP are. | 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 */' require inference rather than being copy-paste ready. | 2 / 3 |
Workflow Clarity | Clear 3-step workflow with explicit validation checkpoint (check connection shows ACTIVE before proceeding). Setup section includes verification steps and the 'Known Pitfalls' section provides error prevention guidance. | 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 aids navigation. | 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.