bart-automation

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

Quality

49%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./composio-skills/bart-automation/SKILL.md

Quality

Discovery

22%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This description is too vague to be effective for skill selection. It fails to explain what specific tasks can be automated, what Bart actually is, or when Claude should use this skill. The technical product names provide minimal distinctiveness but users unfamiliar with these tools won't know when to invoke this skill.

Suggestions

Add a 'Use when...' clause specifying trigger scenarios, e.g., 'Use when the user mentions Bart, Composio integrations, or needs to automate [specific task types]'

Replace 'Automate Bart tasks' with specific concrete actions, e.g., 'Create tickets, sync data, manage workflows in Bart'

Include natural language terms users might say when needing this skill, not just product names

Dimension	Reasoning	Score
Specificity	The description uses vague language like 'Automate Bart tasks' without specifying what concrete actions are possible. 'Always search tools first' is procedural guidance, not a capability description.	1 / 3
Completeness	The 'what' is extremely vague ('Automate Bart tasks') and there is no 'Use when...' clause or equivalent trigger guidance explaining when Claude should select this skill.	1 / 3
Trigger Term Quality	Contains some relevant keywords ('Bart', 'Rube MCP', 'Composio') but these are technical/product names that users may not naturally use. Missing common task-oriented terms users would actually say.	2 / 3
Distinctiveness Conflict Risk	The specific product names (Bart, Rube MCP, Composio) provide some distinctiveness, but 'automate tasks' is generic enough to potentially conflict with other automation skills.	2 / 3
	Total	6 / 12 Passed

Implementation

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a well-structured skill that efficiently communicates how to automate Bart tasks via Rube MCP. The workflow is clear with proper validation checkpoints, and the Known Pitfalls section adds valuable guardrails. The main weakness is that tool call examples are illustrative rather than fully executable, which slightly reduces actionability.

Suggestions

Convert the pseudo-code tool call examples into fully executable format (e.g., actual JSON payloads or function calls) that can be directly used

Consider adding a concrete end-to-end example showing a complete Bart task from discovery through execution with actual response handling

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient, avoiding unnecessary explanations of what Bart or MCP are. Every section serves a purpose and assumes Claude's competence with the underlying concepts.	3 / 3
Actionability	Provides concrete tool call patterns with specific parameters, but uses pseudo-code style rather than fully executable examples. The tool calls show structure but aren't copy-paste ready in any specific language or format.	2 / 3
Workflow Clarity	Clear 4-step setup sequence with explicit validation (check connection status shows ACTIVE before proceeding). The 3-step core workflow pattern includes proper sequencing with connection verification as a checkpoint.	3 / 3
Progressive Disclosure	Content is well-organized with clear sections and a quick reference table, but everything is inline in one file. The external link to Composio docs is appropriate, but the skill could benefit from separating detailed examples or edge cases into referenced files.	2 / 3
	Total	10 / 12 Passed

Validation

90%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: ComposioHQ/awesome-claude-skills
Commit: 2790447

Reviewed: 2 months ago

Table of Contents

Discovery Implementation Validation

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.