CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

botsonic-automation

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

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

A well-structured, lean, single-file skill body with concrete tool-call patterns, explicit pre-flight checkpoints, and a useful pitfalls/quick-reference section. The main improvement opportunities are removing the triple repetition of the search-first rule and adding a short worked example with realistic argument values.

Suggestions

State 'Always call RUBE_SEARCH_TOOLS first' once (e.g., in Pitfalls) and remove the duplicates in Prerequisites and Tool Discovery to tighten the body toward a 5 on conciseness.

Add one small end-to-end worked example with realistic placeholder values (a concrete use_case string and a discovered tool_slug) to push actionability from mostly to fully executable.

Add a brief post-execution validation note (check the response status/errors from RUBE_MULTI_EXECUTE_TOOL before proceeding) to complete the feedback loop for workflow clarity.

DimensionReasoningScore

Conciseness

The body is lean with no explanations of concepts Claude already knows and every section earns its place. Minor trimmable redundancy: 'Always call RUBE_SEARCH_TOOLS first' appears in Prerequisites, Tool Discovery, and again in Pitfalls, and Setup overlaps Prerequisites slightly — matching 'efficient; minor instances that could be trimmed' rather than the 5 anchor's 'every token earns its place'.

4 / 5

Actionability

Concrete tool-call blocks show exact parameter names and structure (e.g., 'RUBE_SEARCH_TOOLS / queries: [{use_case: ...}] / session: {generate_id: true}') plus a Quick Reference table. Minor gaps keep it below 5: arguments are placeholders ('TOOL_SLUG_FROM_SEARCH', '/* schema-compliant args */') and no end-to-end worked example is shown — justified by the schema-changes-often caveat, but still not fully copy-paste ready.

4 / 5

Workflow Clarity

A clear 3-step sequence (discover tools → check connection → execute) with explicit checkpoints: 'Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds' and 'Confirm connection status shows ACTIVE before running any workflows', plus a Pitfalls section covering error avoidance and pagination. It sits at 'clear sequence with most checkpoints present; minor validation gaps' — no explicit post-execution validation/retry loop — rather than 5's full feedback loops.

4 / 5

Progressive Disclosure

No bundle files exist, and the ~85-line body is appropriately self-contained with well-organized sections (Prerequisites, Setup, Tool Discovery, Workflow, Pitfalls, Quick Reference) and no nested or buried references. It misses 5 only because the under-50-lines simple-skill exception doesn't apply and the Quick Reference's mention of RUBE_GET_TOOL_SCHEMAS/RUBE_REMOTE_WORKBENCH could be slightly better signaled.

4 / 5

Total

16

/

20

Passed

Description

52%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 short and unambiguous about its niche but under-sells it: no concrete Botsonic capabilities and no 'Use when...' trigger clause, which caps both specificity and completeness. Adding one sentence listing 2-3 concrete operations and a trigger clause would raise it substantially.

Suggestions

Add a 'Use when...' clause, e.g., 'Use when the user mentions Botsonic, chatbot training, or needs to automate Botsonic workflows.'

Replace the generic 'Automate Botsonic tasks' with 2-3 concrete capabilities (e.g., 'train chatbots, manage knowledge bases, deploy and test Botsonic widgets').

Include natural synonyms/variations users might say (chatbot builder, KB, widget) to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

"Automate Botsonic tasks" names the domain but 'tasks' is generic — no concrete capabilities (e.g., chatbot management, KB training, deployment) are listed, matching the 'names the domain but actions are minimal or generic' anchor. It is not a 3 because unlike 'Processes PDF files and extracts content' it never enumerates even 1-2 specific actions.

2 / 5

Completeness

The 'what' is clear ("Automate Botsonic tasks via Rube MCP (Composio)"), but there is no 'Use when...' clause or equivalent trigger guidance — the rubric explicitly caps completeness at 3 for this. Not 2 because the 'what' is specific and the operational rule ('Always search tools first for current schemas') adds genuine signal.

3 / 5

Trigger Term Quality

"Botsonic", "Rube MCP", and "Composio" are relevant keywords a user needing this skill would say, but there are no variations, synonyms, or task-level phrases (chatbot, knowledge base, widget deployment). Matches the 'some relevant keywords but missing common variations or synonyms' anchor rather than 4's 'good keyword coverage with a few natural terms missing'.

3 / 5

Distinctiveness Conflict Risk

Botsonic is a distinct product niche and the description only claims that domain, so it would rarely trigger for the wrong skill — 'clear niche with distinct triggers; minimal conflict risk'. Not 4 because there is no real overlap risk with closely related skills; the product name is unambiguous.

5 / 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/botsonic-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.