CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

bart-automation

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

56

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

The content is well-structured, lean, and actionable with concrete tool-call examples and a clear sequenced workflow including a connection-status checkpoint. Its main gaps are minor: some restating of the 'search first' rule, placeholder argument values, and no explicit post-execution verification for bulk operations.

Suggestions

Add a brief post-execution verification step (e.g., check the returned status/errors and confirm pagination is exhausted) to strengthen the workflow feedback loop, especially for bulk operations via RUBE_REMOTE_WORKBENCH.

Consolidate the repeated 'always search first' guidance into a single Pitfalls entry to remove redundancy across prerequisites, tool discovery, and known pitfalls.

Include one fully-worked example with concrete argument values (beyond placeholders) so a common case is copy-paste ready end-to-end.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, avoiding explanations of basic concepts; the only trimmable redundancy is 'Always search first' restated across prerequisites, tool discovery, and known pitfalls, which keeps it just below a 5.

4 / 5

Actionability

Provides concrete, copy-paste-ready tool-call blocks with exact parameter names (RUBE_SEARCH_TOOLS, RUBE_MULTI_EXECUTE_TOOL) and a Quick Reference table; not a 5 because argument values use placeholders ('TOOL_SLUG_FROM_SEARCH', '/* schema-compliant args */') rather than a worked example.

4 / 5

Workflow Clarity

Clear sequenced workflow (Discover -> Check Connection -> Execute) with an explicit ACTIVE-status checkpoint and an auth-link recovery loop in Setup; not a 5 because there is no post-execution result-verification step for batch/bulk operations.

4 / 5

Progressive Disclosure

Well-organized into clearly labeled sections with no nested references and a single external doc link; no bundle files exist, so the self-contained structure is appropriate, though at ~80 lines it is slightly above the under-50-lines threshold that would warrant a 5 on structure alone.

4 / 5

Total

16

/

20

Passed

Description

53%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 states what the skill does and names a distinct service, but it lacks an explicit 'Use when' trigger clause and offers only one concrete action, capping completeness and specificity. Trigger-term coverage is thin beyond the 'Bart' keyword.

Suggestions

Add an explicit 'Use when...' clause stating when Claude should invoke this skill (e.g., 'Use when the user asks to automate Bart operations or interact with the Bart toolkit via Composio').

List 1-2 more concrete actions beyond 'search tools first' (e.g., execute Bart tool calls, manage the Bart connection, handle paginated Bart responses).

Include natural trigger synonyms users might say (e.g., 'Bart workflows', 'Bart integration', 'Composio Bart') to improve keyword coverage.

DimensionReasoningScore

Specificity

Names the domain ('Automate Bart tasks via Rube MCP') and one concrete action ('Always search tools first for current schemas'), but 'automate' is generic and coverage is not comprehensive; not a 4 because only a single concrete action is listed.

3 / 5

Completeness

Has a clear 'what' (automate Bart tasks via Rube MCP) but no 'Use when...' trigger clause; per the rubric a missing explicit trigger caps completeness at 3, and 'Always search tools first' is a process instruction rather than a when-condition.

3 / 5

Trigger Term Quality

Includes the natural keyword 'Bart tasks' and 'automate', but 'Rube MCP (Composio)' is technical jargon and common variations/synonyms are missing; not a 4 due to thin keyword coverage.

3 / 5

Distinctiveness Conflict Risk

The named service 'Bart' plus 'Rube MCP (Composio)' carve a fairly distinct niche with low conflict risk; not a 5 because it could still overlap with sibling Composio/Rube toolkit skills.

4 / 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/bart-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.