Automate Apipie AI tasks via Rube MCP (Composio). Always search tools first for current schemas.
67
Quality
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/apipie-ai-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 specific tools/platforms but fails to explain what tasks can be automated or when this skill should be chosen. The lack of concrete actions and explicit trigger conditions makes it difficult for Claude to know when to select this skill over others.
Suggestions
Add specific concrete actions this skill enables (e.g., 'Create API integrations, manage workflows, connect services').
Add an explicit 'Use when...' clause with trigger terms users would naturally say (e.g., 'Use when the user mentions Apipie, Composio integrations, or needs to connect AI services').
Replace 'automate tasks' with specific task types this skill handles to improve both specificity and distinctiveness.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'automate 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 tasks') and there is no 'Use when...' clause or equivalent guidance on when Claude should select this skill. The second sentence is implementation guidance, not trigger criteria. | 1 / 3 |
Trigger Term Quality | Includes some relevant keywords ('Apipie AI', 'Rube MCP', 'Composio') but these are technical/product names rather than natural terms users would say. Missing common variations or task-oriented triggers. | 2 / 3 |
Distinctiveness Conflict Risk | The specific product names (Apipie AI, Rube MCP, Composio) provide some distinctiveness, but 'automate tasks' is generic enough to potentially conflict with other automation-related 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 Apipie AI 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 examples, which slightly reduces immediate actionability.
Suggestions
Provide at least one complete, concrete example with actual tool slugs and real argument values (even if hypothetical) to demonstrate the full pattern end-to-end
Consider adding a brief example of handling pagination tokens mentioned in Known Pitfalls to make that guidance more actionable
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, avoiding explanations of concepts Claude already knows. Every section serves a purpose with no padding or unnecessary context about what Apipie AI is or how APIs work. | 3 / 3 |
Actionability | Provides concrete tool call patterns with specific parameters, but the examples are pseudocode-like structures rather than fully executable code. The argument placeholders and comments like '/* schema-compliant args from search results */' reduce copy-paste readiness. | 2 / 3 |
Workflow Clarity | Clear 3-step workflow with explicit sequencing (discover → check connection → execute). Includes validation checkpoint ('Confirm connection status shows ACTIVE before running any workflows') and the Known Pitfalls section provides error prevention guidance. | 3 / 3 |
Progressive Disclosure | Well-organized 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 | |
2790447
Table of Contents
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.