apitemplate-io-automation

Automate Apitemplate IO tasks via Rube MCP (Composio). Always search tools first for current schemas.

Install with Tessl CLI

npx tessl i github:ComposioHQ/awesome-claude-skills --skill apitemplate-io-automation

What are skills?

Review — 46%

Does it follow best practices?

If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:

npx tessl skill review --optimize ./path/to/skill

Learn more

Validation — 10 / 11 Passed

Validation for skill structure

SKILL.md

Review

Evals

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 (Apitemplate IO via Rube MCP/Composio) but fails to explain what specific tasks can be automated or when Claude should choose this skill. The operational instruction about searching tools first doesn't help with skill selection.

Suggestions

Add specific capabilities: replace 'Automate tasks' with concrete actions like 'Generate PDFs from templates, create documents, fill form fields, batch produce certificates or invoices'

Add a 'Use when...' clause with natural trigger terms: 'Use when the user mentions PDF generation, document templates, Apitemplate, or needs to create documents from data'

Include common user phrases and file types that would trigger this skill, such as 'PDF templates', 'document generation', 'batch documents', '.pdf creation'

Dimension	Reasoning	Score
Specificity	The description uses vague language like 'Automate tasks' without specifying what concrete actions can be performed. No specific capabilities like 'generate PDFs', 'create templates', or 'fill documents' 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	Includes 'Apitemplate IO', 'Rube MCP', and 'Composio' as technical terms, but lacks natural user keywords. Users might say 'generate PDF from template' or 'create document' rather than these product names.	2 / 3
Distinctiveness Conflict Risk	The specific product names (Apitemplate IO, Rube MCP, Composio) provide some distinctiveness, but 'automate tasks' is generic enough to potentially conflict with other automation or MCP-related skills.	2 / 3
	Total	6 / 12 Passed

Implementation

70%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill provides a solid structural framework for Apitemplate IO automation with clear workflow sequencing and good organization. However, it lacks concrete, real-world examples of actual Apitemplate IO operations (like generating PDFs or images) and relies on placeholder values rather than executable examples. The content would benefit from at least one complete, specific use case.

Suggestions

Add a concrete example showing a real Apitemplate IO operation (e.g., generating a PDF from a template) with actual tool slugs and argument values

Remove redundancy between the 'Tool Discovery' section and 'Step 1' of the Core Workflow Pattern - consolidate into one location

Include an example response from RUBE_SEARCH_TOOLS showing what actual Apitemplate IO tool schemas look like

Dimension	Reasoning	Score
Conciseness	The content is reasonably efficient but includes some redundancy - the workflow pattern repeats information already covered in Setup and Tool Discovery sections. The Quick Reference table adds value but some explanatory text could be tightened.	2 / 3
Actionability	Provides concrete tool call examples with parameter structures, but these are pseudocode-style representations rather than actual executable commands. The arguments use placeholders like 'your specific Apitemplate IO task' rather than concrete examples.	2 / 3
Workflow Clarity	Clear 3-step workflow with explicit sequencing (discover → check connection → execute). Includes validation checkpoint (verify ACTIVE status before executing) and the Known Pitfalls section provides error prevention guidance.	3 / 3
Progressive Disclosure	Well-structured with clear sections progressing from prerequisites to setup to workflow to pitfalls. External reference to Composio docs is one level deep and clearly signaled. Content length is appropriate for inline presentation.	3 / 3
	Total	10 / 12 Passed

Validation

90%

Warnings & errors only

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

Reviewed: 9 days ago

Table of Contents

Discovery Implementation Validation

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.