CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

api-labz-automation

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

48

Quality

60%

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/api-labz-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 content is well-structured and operational, providing concrete Rube MCP call templates and a clear setup-to-execution workflow. Its main gaps are repeated 'search first' emphasis, absent execution-error feedback loops for batch operations, and placeholder-laden examples that are not fully copy-paste ready.

Suggestions

Consolidate the repeated 'always search first / check connection' guidance into a single authoritative checkpoint to reduce redundancy.

Add an explicit error-recovery feedback loop after RUBE_MULTI_EXECUTE_TOOL (e.g., on schema/auth errors, re-run RUBE_SEARCH_TOOLS and retry) to satisfy the batch-operations validation bar.

Provide at least one fully-resolved copy-paste example with a concrete tool_slug and sample arguments alongside the templated placeholders.

DimensionReasoningScore

Conciseness

The body avoids explaining concepts Claude already knows, but 'search tools first' and 'check connection' recur three to four times across Prerequisites, Tool Discovery, Setup, and Known Pitfalls, adding repetition that could be tightened.

3 / 5

Actionability

Concrete tool-call templates with real parameter structures (queries, session, tool_slug, arguments, memory) are provided, but placeholders like 'TOOL_SLUG_FROM_SEARCH' and 'schema-compliant args from search results' keep it from being fully copy-paste ready.

4 / 5

Workflow Clarity

A clear Discover -> Check Connection -> Execute sequence exists with an explicit ACTIVE-status checkpoint, but batch/execute operations (RUBE_MULTI_EXECUTE_TOOL, RUBE_REMOTE_WORKBENCH, pagination) lack error-recovery feedback loops, so the batch-operations cap applies.

3 / 5

Progressive Disclosure

No bundle files exist and the single-file body is well-sectioned (Prerequisites, Setup, Tool Discovery, Core Workflow, Known Pitfalls, Quick Reference) with a navigation table, but at ~85 lines it slightly exceeds the lean single-file threshold, keeping it below the maximal anchor.

4 / 5

Total

14

/

20

Passed

Description

41%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 its niche (API Labz automation via Rube MCP) but lacks explicit 'use when' trigger guidance and leans on technical jargon over natural user phrasing. Capability phrasing is generic ('Automate...tasks') rather than enumerating concrete actions.

Suggestions

Add an explicit 'Use when...' clause naming concrete trigger phrases (e.g., 'Use when the user wants to automate API Labz operations or run API Labz workflows').

Replace the generic 'Automate API Labz tasks' with specific concrete actions the skill performs (e.g., 'discover, connect to, and execute API Labz tools').

Surface a couple of natural user-facing keywords or synonyms alongside the brand jargon so users would naturally say the trigger terms.

DimensionReasoningScore

Specificity

The phrase 'Automate API Labz tasks' names the domain but the action is generic, and 'Always search tools first for current schemas' is a behavioral directive rather than a concrete capability, matching the anchor 'Names the domain but actions are minimal or generic' rather than the multi-action anchor above.

2 / 5

Completeness

It gives a clear 'what' ('Automate API Labz tasks via Rube MCP') but no 'Use when...' trigger clause, and the rubric caps completeness at 3 when explicit trigger guidance is missing.

3 / 5

Trigger Term Quality

The description is dominated by technical jargon ('Rube MCP (Composio)', 'schemas'); 'API Labz' is the only natural user-facing term and no synonyms or variations are offered, leaving it below the 'some relevant keywords' anchor.

2 / 5

Distinctiveness Conflict Risk

Being scoped to the specific Composio 'API Labz' toolkit via Rube MCP gives it a clear niche with minimal overlap risk, though the generic 'Automate...tasks' phrasing keeps it just shy of the maximal-distinctiveness anchor.

4 / 5

Total

11

/

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/api-labz-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.