accelo-automation

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

5.71x

Quality

53%

Does it follow best practices?

Impact

80%

5.71x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./composio-skills/accelo-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 effectively guide skill selection. While it names specific tools (Accelo, Rube MCP, Composio), it fails to describe what concrete actions can be performed and provides no explicit trigger guidance. The operational instruction about searching tools first is misplaced in a description meant for skill selection.

Suggestions

Add specific capabilities that Accelo automation supports (e.g., 'Create and manage projects, track time entries, handle invoicing, manage contacts and companies').

Add a 'Use when...' clause with natural trigger terms like 'Use when the user mentions Accelo, needs to automate project management, CRM tasks, or professional services automation'.

Move the operational instruction 'Always search tools first for current schemas' to the skill body rather than the description, as it's guidance for execution, not selection.

Dimension	Reasoning	Score
Specificity	The description says 'Automate Accelo tasks' which is extremely vague - it doesn't specify what tasks can be automated (e.g., create projects, manage contacts, track time). The only concrete action mentioned is 'search tools first' which is a meta-instruction, not a capability.	1 / 3
Completeness	The 'what' is extremely weak (just 'automate tasks'), and there is no 'Use when...' clause or equivalent trigger guidance. The instruction to 'search tools first' is operational guidance for Claude, not selection criteria.	1 / 3
Trigger Term Quality	Includes 'Accelo', 'Rube MCP', and 'Composio' as specific product names that users familiar with these tools would use. However, it lacks natural task-oriented keywords users might say like 'project management', 'CRM', 'invoicing', or 'time tracking'.	2 / 3
Distinctiveness Conflict Risk	The specific mention of 'Accelo' and 'Rube MCP (Composio)' provides some distinctiveness from generic automation skills. However, 'automate tasks' is generic enough that it could conflict with other automation or integration skills.	2 / 3
	Total	6 / 12 Passed

Implementation

85%

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 guides Claude through Accelo automation via Rube MCP. The workflow is clear with proper validation checkpoints, and the content respects token budget. The main weakness is that tool call examples use placeholder syntax rather than fully concrete, executable examples with realistic argument values.

Suggestions

Replace placeholder comments like '/* schema-compliant args from search results */' with a concrete example showing actual Accelo-specific arguments (e.g., creating a task or fetching contacts)

Add one complete end-to-end example showing a real Accelo operation from search through execution with actual response handling

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient, avoiding explanations of what Accelo or MCP are. Every section provides actionable information without padding or unnecessary context.	3 / 3
Actionability	Provides concrete tool call patterns with parameter examples, but uses pseudo-code style rather than fully executable code. The argument placeholders like '/* schema-compliant args */' require inference rather than being copy-paste ready.	2 / 3
Workflow Clarity	Clear 3-step workflow with explicit sequencing (discover → check connection → execute). Setup section includes validation checkpoint ('Confirm connection status shows ACTIVE before running any workflows'). Known pitfalls section addresses error prevention.	3 / 3
Progressive Disclosure	Well-organized with clear sections progressing from prerequisites to setup to workflow to pitfalls. Quick reference table provides at-a-glance navigation. External link to toolkit docs is appropriately one level deep.	3 / 3
	Total	11 / 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: 29 days 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.