apiflash-automation
Automate Apiflash 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/apiflash-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 assumes the reader already knows what Apiflash is. It lacks concrete actions, natural trigger terms users would say, and explicit guidance on when to use this skill. The description reads more like an internal note than a useful skill selector.
Suggestions
Add specific capabilities that Apiflash provides (e.g., 'Capture website screenshots, generate page thumbnails, convert URLs to images')
Add a 'Use when...' clause with natural trigger terms like 'screenshot', 'capture webpage', 'URL to image', 'website thumbnail'
Explain what Apiflash is briefly so Claude can match user requests that don't mention the product name directly
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'Automate Apiflash tasks' without specifying what concrete actions can be performed. No specific capabilities like 'capture screenshots', 'generate thumbnails', or 'convert pages' are mentioned. | 1 / 3 |
Completeness | The 'what' is extremely vague ('Automate Apiflash tasks') and there is no 'Use when...' clause or explicit trigger guidance. The instruction to 'search tools first' is operational guidance, not a usage trigger. | 1 / 3 |
Trigger Term Quality | Contains 'Apiflash', 'Rube MCP', and 'Composio' as keywords, but these are technical/product names rather than natural terms users would say. Missing common variations like 'screenshot', 'webpage capture', 'URL to image'. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'Apiflash' and 'Rube MCP (Composio)' provides some distinctiveness through product names, but without describing what Apiflash actually does, it could conflict with other screenshot or web capture tools. | 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 Apiflash 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 Apiflash-specific arguments (e.g., a screenshot capture workflow) rather than generic placeholders
Show a sample response from RUBE_SEARCH_TOOLS so Claude knows what to expect and how to extract tool slugs and schemas
| 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 Apiflash or Composio are. | 3 / 3 |
Actionability | Provides concrete tool call patterns with specific field names and structures, but the examples are pseudocode-like representations rather than actual executable code. The argument placeholders 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). Setup section includes validation checkpoint (confirm ACTIVE status before proceeding). 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 | |
- 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.