CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

autobound-automation

Automate Autobound 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/autobound-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 with concrete, mostly-executable tool-call examples and a clear workflow, but it repeats the 'search first' directive across sections and lacks an explicit error-recovery feedback loop for batch operations.

Suggestions

Consolidate the repeated 'always search tools first' guidance into a single Prerequisites or Known Pitfalls entry instead of restating it in Tool Discovery, Core Workflow, and Pitfalls.

Add an explicit validate-then-retry feedback loop after RUBE_MULTI_EXECUTE_TOOL (e.g., inspect the response for errors, fix arguments per the schema, re-run), since bulk execution is a batch operation.

Trim or move the inline Quick Reference table content that overlaps the Core Workflow steps to reduce redundancy and tighten the token budget.

DimensionReasoningScore

Conciseness

Mostly efficient with no over-explanation of concepts Claude knows, but the 'always search tools first' directive is repeated across Prerequisites, Tool Discovery, Core Workflow Pattern, and Known Pitfalls, adding padding that could be consolidated.

3 / 5

Actionability

Provides concrete code blocks with real field names for RUBE_SEARCH_TOOLS, RUBE_MANAGE_CONNECTIONS, and RUBE_MULTI_EXECUTE_TOOL; placeholders like 'TOOL_SLUG_FROM_SEARCH' are justified by the dynamic-schema design rather than lazy pseudocode.

4 / 5

Workflow Clarity

A clear 3-step Core Workflow Pattern exists with a connection-ACTIVE checkpoint, but it lacks an explicit validate-on-error feedback loop for batch execution via RUBE_MULTI_EXECUTE_TOOL/RUBE_REMOTE_WORKBENCH, which caps batch-operation workflow clarity at 3.

3 / 5

Progressive Disclosure

Well-organized into Prerequisites, Setup, Tool Discovery, Core Workflow, Known Pitfalls, and a Quick Reference table with no nested references; content is appropriately self-contained though slightly over the lean length that would warrant a 5.

4 / 5

Total

14

/

20

Passed

Description

57%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 names a distinct niche (Autobound via Rube MCP) but relies on generic 'tasks' language and technical jargon, and lacks an explicit 'Use when' trigger clause. It is adequate but not exemplary.

Suggestions

Add a 'Use when...' clause with concrete trigger phrases (e.g., 'Use when automating Autobound sales-enablement tasks, managing Autobound campaigns, or the user mentions Autobound').

Replace generic 'Automate Autobound tasks' with 2-3 specific operations the skill performs (e.g., 'create and update Autobound profiles, generate prospect content').

Surface a natural-language keyword or synonym a non-technical user would actually say, rather than leaning on 'Rube MCP (Composio)'.

DimensionReasoningScore

Specificity

Names the domain (Autobound) and one concrete action ('Automate Autobound tasks') plus 'search tools first', but 'tasks' is generic and it stops short of listing several specific operations.

3 / 5

Completeness

Has a clear 'what' (automate Autobound tasks via Rube MCP) but no 'Use when...' or equivalent trigger clause, which caps completeness at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

'Autobound tasks' and 'Autobound' are reasonable natural terms for users of the product, but the description leans on technical jargon ('Rube MCP', 'Composio') and omits common variations/synonyms.

3 / 5

Distinctiveness Conflict Risk

Tied to a specific named product (Autobound via Rube MCP/Composio), giving it a clear niche with minimal conflict risk against unrelated skills.

5 / 5

Total

14

/

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