Automate API Ninjas tasks via Rube MCP (Composio). Always search tools first for current schemas.
87
85%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
N/ABased on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
Something went wrong
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 Ninjas automation via Rube MCP. The workflow is clear with proper validation steps, and the content respects token budget. The main weakness is that the tool call examples use a pseudo-code notation that may not be directly executable depending on the MCP client context.
Suggestions
Clarify the exact syntax for MCP tool calls - are these JSON payloads, function calls, or another format? Showing one complete, executable example would improve actionability.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, avoiding explanations of what API Ninjas or Composio are. Every section serves a purpose with no padding or unnecessary context. | 3 / 3 |
Actionability | Provides concrete tool call patterns with parameter structures, but uses pseudo-code 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 sequence (discover → check connection → execute). Includes validation checkpoint for connection status before proceeding, 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 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 | |
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.