CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

apipie-ai-automation

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

56

Quality

70%

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/apipie-ai-automation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 an efficient, well-structured automation guide with concrete MCP call examples, a clear sequenced workflow, and explicit connection-state checkpoints. It falls just short of top marks due to minor section duplication, placeholder arguments, and the absence of an explicit error-recovery feedback loop.

Suggestions

Consolidate the duplicated search-tool guidance between 'Tool Discovery' and 'Step 1' into a single source of truth.

Add an explicit validate->fix->retry feedback loop for execution failures (e.g., on schema errors, re-call RUBE_SEARCH_TOOLS and retry).

Include one fully-resolved end-to-end example with concrete argument values to lift actionability from placeholder-based to copy-paste ready.

DimensionReasoningScore

Conciseness

The body is lean and code-driven with no padding or explanation of concepts Claude already knows; the only trimmable redundancy is the overlap between the 'Tool Discovery' section and 'Step 1: Discover Available Tools', plus pitfalls restating prerequisites.

4 / 5

Actionability

Provides concrete, near-copy-paste MCP calls with parameter shapes (RUBE_SEARCH_TOOLS queries/session, RUBE_MULTI_EXECUTE_TOOL tools/arguments), but uses runtime placeholders like 'TOOL_SLUG_FROM_SEARCH' and 'your_session_id' rather than fully worked examples.

4 / 5

Workflow Clarity

A clear sequenced workflow (Setup -> Discover -> Check Connection -> Execute) with explicit ACTIVE-status checkpoints; the destructive/batch cap does not apply since verification is present, but no explicit validate->fix->retry feedback loop is spelled out beyond pitfall hints.

4 / 5

Progressive Disclosure

Well-organized single-file skill with a Quick Reference table and one clearly signaled external doc link; no nested references and no bundle files, but at ~85 lines it exceeds the under-50-line simple-skill exception that would allow a 5.

4 / 5

Total

16

/

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 identifies a specific niche (Apipie AI via Composio's Rube MCP) and gives one concrete behavioral directive, but it omits any explicit 'use when' trigger guidance and relies on generic verb + jargon rather than comprehensive natural trigger terms.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user wants to automate Apipie AI operations or mentions Apipie/integrations via Composio.'

Replace the generic 'Automate Apipie AI tasks' with 2-3 specific operations the skill performs to raise specificity.

Surface natural user-facing terms (e.g. 'Apipie AI integration', 'Composio connection') alongside the technical 'Rube MCP' jargon.

DimensionReasoningScore

Specificity

Names the domain ('Apipie AI tasks') and a concrete action ('search tools first for current schemas'), but the main verb 'Automate ... tasks' is generic rather than a list of specific operations, matching the '1-2 concrete actions, not comprehensive' anchor.

3 / 5

Completeness

The 'what' is clear ('Automate Apipie AI tasks via Rube MCP'), but there is no 'Use when...' trigger clause; per the guideline, a missing explicit trigger caps completeness at 3.

3 / 5

Trigger Term Quality

Includes the natural product term 'Apipie AI', but leans on technical jargon ('Rube MCP (Composio)') and offers few common variations or synonyms, fitting 'some relevant keywords but missing common variations'.

3 / 5

Distinctiveness Conflict Risk

'Apipie AI' carves a clear niche with minimal conflict risk, but the 'via Rube MCP (Composio)' pattern is templated across many Composio toolkits, so overlap with sibling skills is only mostly avoided.

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.

Validation — 15 / 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

Path

composio-skills/apipie-ai-automation/SKILL.md

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.