Automate Asin Data API 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/asin-data-api-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 (Asin Data API via Rube MCP/Composio) but fails to specify what actions can be performed or when Claude should use this skill. The lack of concrete capabilities and explicit trigger conditions makes it difficult to distinguish from other API automation skills.
Suggestions
Add specific concrete actions the skill performs (e.g., 'Fetch Amazon product details, pricing history, reviews, and seller information using ASIN codes').
Add an explicit 'Use when...' clause with natural trigger terms (e.g., 'Use when the user asks about Amazon product data, ASIN lookups, or needs to retrieve product information from Amazon').
Include common user-facing terms alongside technical names (e.g., 'Amazon product data', 'product lookup', 'ASIN search') to improve trigger term coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'Automate...tasks' without specifying what concrete actions are performed. No specific capabilities like 'fetch product data', 'retrieve pricing', or 'extract reviews' are mentioned. | 1 / 3 |
Completeness | The 'what' is extremely vague ('Automate...tasks') and there is no 'Use when...' clause or equivalent trigger guidance. The instruction to 'search tools first' is operational guidance, not a usage trigger. | 1 / 3 |
Trigger Term Quality | Contains some relevant keywords ('Asin Data API', 'Rube MCP', 'Composio') but these are technical/product names rather than natural terms users would say. Missing common variations like 'Amazon product data', 'ASIN lookup', or 'product information'. | 2 / 3 |
Distinctiveness Conflict Risk | The specific mention of 'Asin Data API' and 'Rube MCP (Composio)' provides some distinctiveness, but the generic 'tasks' framing could overlap with other API or 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 Claude how to automate Asin Data API tasks through Rube MCP. The workflow is clear with proper validation checkpoints, and the content respects token budget by avoiding unnecessary explanations. The main weakness is that the tool call examples use a pseudo-notation rather than showing actual executable syntax for the MCP tool calls.
Suggestions
Show actual MCP tool call syntax (e.g., the exact JSON structure or function call format) rather than the current pseudo-notation to make examples truly copy-paste ready
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, avoiding unnecessary explanations of what APIs or MCP servers are. Every section serves a purpose and assumes Claude's competence with the underlying concepts. | 3 / 3 |
Actionability | Provides concrete tool call patterns with specific parameters, but uses pseudo-code style notation rather than actual executable code. The examples show structure but aren't copy-paste ready for any specific runtime. | 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-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.