CtrlK
BlogDocsLog inGet started
Tessl Logo

apitemplate-io-automation

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

52

Quality

57%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./composio-skills/apitemplate-io-automation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%Weight 40%Scale 1-5

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

The body is well-structured and gives concrete, executable MCP tool-call examples with a clear core workflow. Its main weaknesses are repeated 'search first' guidance, a duplicated discovery section, and the absence of validation/feedback loops for batch execution.

Suggestions

Collapse the standalone 'Tool Discovery' section into 'Step 1: Discover Available Tools' to remove the duplication and tighten conciseness.

Add a validation/feedback step after RUBE_MULTI_EXECUTE_TOOL (check results, handle errors, retry on failure) to support batch operations and lift workflow clarity above 3.

State the 'search tools first' rule once in Known Pitfalls and reference it elsewhere rather than restating it verbatim multiple times.

DimensionReasoningScore

Conciseness

The body is mostly efficient and avoids explaining concepts Claude already knows, but the 'search tools first' rule is repeated across the prerequisites, Tool Discovery section, Step 1, and Known Pitfalls, and the Tool Discovery section substantially overlaps Step 1, so it could be tightened.

3 / 5

Actionability

Provides concrete, copy-paste-ready MCP tool call blocks with parameters (RUBE_SEARCH_TOOLS, RUBE_MANAGE_CONNECTIONS, RUBE_MULTI_EXECUTE_TOOL), with only minor gaps where arguments use placeholders like TOOL_SLUG_FROM_SEARCH, which is justified by dynamic schemas.

4 / 5

Workflow Clarity

The Discover -> Check connection -> Execute sequence is clear, but RUBE_MULTI_EXECUTE_TOOL and RUBE_REMOTE_WORKBENCH are batch operations with no result-verification or error-recovery feedback loop, so the batch-operation cap of 3 applies.

3 / 5

Progressive Disclosure

A single-file skill (~80 lines) with no bundle files, organized into well-labeled sections (Prerequisites, Setup, Tool Discovery, Core Workflow, Pitfalls, Quick Reference); the only organization gap is the duplicated discovery guidance, keeping it just below 5.

4 / 5

Total

14

/

20

Passed

Description

53%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description clearly identifies the target product and the search-first procedural rule but omits any "Use when..." trigger guidance and lists no concrete Apitemplate IO capabilities. It is mostly distinct but generic in its action verb.

Suggestions

Add a 'Use when...' clause naming concrete Apitemplate IO operations (e.g., generating images, rendering PDFs from templates) to lift completeness and trigger-term quality.

Replace the generic 'Automate Apitemplate IO tasks' with 2-3 specific capabilities a user would actually request.

Include natural user phrases or file extensions (e.g., 'template', 'image generation', 'PDF render') alongside the product name.

DimensionReasoningScore

Specificity

Names the domain ("Apitemplate IO tasks") and one concrete procedural action ("search tools first for current schemas"), but "Automate ... tasks" is generic and no specific Apitemplate IO capabilities (e.g., generate image, render PDF from template) are listed, matching the anchor that names the domain with only 1-2 concrete actions.

3 / 5

Completeness

It clearly states what the skill does ("Automate Apitemplate IO tasks via Rube MCP") but provides no "Use when..." trigger guidance, so per the missing-trigger cap the score cannot exceed 3.

3 / 5

Trigger Term Quality

Contains the product name "Apitemplate IO" and framework terms ("Rube MCP", "Composio") but lacks the natural task phrases a user would say (e.g., "generate an image", "create a PDF from a template"), fitting the anchor with some relevant keywords but missing common variations.

3 / 5

Distinctiveness Conflict Risk

The explicit toolkit name "apitemplate_io" carves out a clear niche with minimal conflict risk against unrelated skills; the only overlap risk is with sibling Composio/Rube skills, which is minor.

4 / 5

Total

13

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
ComposioHQ/awesome-claude-skills
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.