api2pdf-automation
Automate Api2pdf tasks via Rube MCP (Composio). Always search tools first for current schemas.
87
Quality
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 teaches the Rube MCP workflow pattern for Api2pdf automation. The content is concise, has clear workflow steps with validation checkpoints, and good organization. The main weakness is that actionability could be improved with more concrete Api2pdf-specific examples rather than generic placeholders.
Suggestions
Add 1-2 concrete Api2pdf examples (e.g., converting HTML to PDF) with actual tool slugs and argument schemas to make the skill more immediately actionable
Include an example of what a successful RUBE_SEARCH_TOOLS response looks like so users know what to expect
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, avoiding explanations of what Api2pdf or Composio are. Every section provides actionable information without padding or unnecessary context. | 3 / 3 |
Actionability | Provides concrete tool call patterns with parameter examples, but the examples are pseudo-code style rather than fully executable. The actual Api2pdf operations are abstracted behind 'your specific Api2pdf task' placeholders. | 2 / 3 |
Workflow Clarity | Clear 3-step workflow with explicit sequencing (discover → check connection → execute). Prerequisites and setup include validation checkpoints like confirming ACTIVE status before proceeding. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections, a quick reference table, and external link to toolkit docs. Content is appropriately structured for a single-file skill without unnecessary nesting. | 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.