CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

bigml-automation

Automate Bigml 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/bigml-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 body delivers concrete, mostly executable tool-call guidance with a clear sequenced workflow and good organization. Its main weakness is the absence of an explicit post-execution validation/retry feedback loop for batch operations.

Suggestions

Add a post-execution validation step to the Core Workflow, e.g. "Step 4: Verify results — inspect responses for errors, retry failed tools, and continue pagination until complete".

Include one concrete end-to-end example with a real Bigml operation (e.g., create a dataset from a source and train a model) so the pattern is fully copy-paste ready.

Consolidate the "search tools first" guidance into one authoritative section to remove cross-section repetition.

DimensionReasoningScore

Conciseness

The body is lean with compact tool-call blocks and no over-explanation of concepts Claude already knows; the only mild redundancy is the "search first" guidance repeated across Prerequisites, Tool Discovery, and Known Pitfalls.

4 / 5

Actionability

Concrete tool invocations with their parameters (RUBE_SEARCH_TOOLS, RUBE_MANAGE_CONNECTIONS, RUBE_MULTI_EXECUTE_TOOL) are provided; placeholders like "your_session_id" and "TOOL_SLUG_FROM_SEARCH" are justified by dynamic discovery, but no concrete end-to-end real-operation example is shown.

4 / 5

Workflow Clarity

A clear 3-step Core Workflow (Discover → Check Connection → Execute) with a connection-status checkpoint exists, but there is no post-execution validate→fix→retry feedback loop, and the batch RUBE_MULTI_EXECUTE_TOOL / bulk-ops context caps workflow clarity at 3 per the feedback-loops note.

3 / 5

Progressive Disclosure

The self-contained body (no bundle files present) is well-organized with clear section headers and a Quick Reference navigation table; minor gaps only, with no external references needed.

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 identifies a specific platform and integration path but uses generic action language and omits an explicit 'when to use' trigger clause. It is reasonably distinct but underspecified on capabilities.

Suggestions

Replace "Automate Bigml tasks" with concrete capabilities, e.g. "Create and manage Bigml datasets, train models, and run predictions".

Add an explicit trigger clause such as "Use when the user wants to automate Bigml machine-learning workflows or mentions Bigml datasets, models, or predictions."

Include natural synonyms/extensions (e.g., "BigML", "Bigml models", ".csv sources") to broaden trigger coverage.

DimensionReasoningScore

Specificity

The phrase "Automate Bigml tasks via Rube MCP (Composio)" names the domain and the integration mechanism, but the action "Automate Bigml tasks" is generic and does not list concrete operations (e.g., create datasets, train models, generate predictions).

2 / 5

Completeness

There is a clear-enough 'what' (automate Bigml via Rube MCP) but no 'Use when…' trigger clause, which per the judging guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

"Bigml" is a natural keyword a user would say, but it is surrounded by technical jargon ("Rube MCP", "Composio", "schemas") and lacks common variations or synonyms.

3 / 5

Distinctiveness Conflict Risk

Bigml is a specific niche platform giving a clear niche, with only minor overlap risk against a broader generic Composio/Rube automation skill.

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