CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

apiverve-automation

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

52

Quality

66%

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

Quality

Content

68%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 content is an efficient, actionable single-file workflow guide with concrete Rube MCP tool calls and a helpful quick-reference table. Its main gap is the absence of an explicit validate-results feedback loop for batch tool execution, which caps workflow clarity.

Suggestions

Add an explicit post-execution validation step to the Core Workflow (e.g., inspect RUBE_MULTI_EXECUTE_TOOL response for errors/failed tools, retry or surface failures before proceeding).

Consolidate the duplicate connection-status guidance from Setup and Step 2 into a single source to tighten conciseness.

Document a pagination/retry feedback loop as a numbered sub-step rather than only a Known Pitfall bullet, since bulk operations depend on it.

DimensionReasoningScore

Conciseness

The body is lean with code blocks and a compact quick-reference table, assuming Claude's intelligence; only minor duplication (connection guidance appears in both Setup and Core Workflow) could be trimmed.

4 / 5

Actionability

Concrete tool calls with exact field names (RUBE_SEARCH_TOOLS, RUBE_MANAGE_CONNECTIONS, RUBE_MULTI_EXECUTE_TOOL) plus a slug-mapping table are mostly executable; args use placeholders like "TOOL_SLUG_FROM_SEARCH" and delegate schemas to search results, leaving minor gaps.

4 / 5

Workflow Clarity

The Discover→Connect→Execute sequence is clear with an ACTIVE-status checkpoint, but this skill involves batch execution (RUBE_MULTI_EXECUTE_TOOL, RUBE_REMOTE_WORKBENCH bulk ops) and lacks an explicit result-validation/error-recovery feedback loop, which caps workflow clarity at 3.

3 / 5

Progressive Disclosure

No bundle files exist and the single ~85-line file is well-sectioned (Prerequisites, Setup, Tool Discovery, Core Workflow, Pitfalls, Quick Reference) with no nested references; structure is good but inherently monolithic for this narrow topic.

4 / 5

Total

15

/

20

Passed

Description

48%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 is clear and distinct about what it automates but generic in capability phrasing and missing explicit "when to use" trigger guidance. Adding concrete actions and a trigger clause would lift the weaker dimensions.

Suggestions

Add a 'Use when...' clause stating when Claude should invoke this skill (e.g., 'Use when automating Apiverve API tasks or when the user mentions Apiverve operations').

Replace the generic 'Automate Apiverve tasks' with 2-3 concrete actions (e.g., 'discover, execute, and chain Apiverve API tools').

Include natural synonyms/users' phrasings (e.g., 'Apiverve APIs', 'Apiverve endpoints', 'Composio Apiverve toolkit').

DimensionReasoningScore

Specificity

"Automate Apiverve tasks via Rube MCP" names the domain but the only concrete action is the procedural directive "Always search tools first"; capabilities remain generic rather than enumerated.

2 / 5

Completeness

The "what" is clear (automate Apiverve via Rube MCP) but the "when" is absent — there is no explicit trigger guidance, which caps completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

"Apiverve" and "automation" are real natural keywords, but coverage is narrow with no synonyms or common variations, and there is no "Use when..." trigger phrasing.

3 / 5

Distinctiveness Conflict Risk

Naming the specific "Apiverve" toolkit via "Rube MCP (Composio)" gives it a distinct niche, but sibling Composio toolkit skills likely share the same Rube template, creating minor overlap risk.

4 / 5

Total

12

/

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/apiverve-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.