aero-workflow-automation

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

15.83x

Quality

53%

Does it follow best practices?

Impact

95%

15.83x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./composio-skills/aero-workflow-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 and implementation-focused to effectively guide skill selection. It names specific products but fails to explain what tasks can be automated or when Claude should choose this skill. The instruction about searching tools is internal guidance that doesn't help with skill selection.

Suggestions

Add specific concrete actions that can be performed (e.g., 'Create workflows, manage approvals, track task status, assign team members').

Add a 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when the user mentions Aero, workflow automation, task management, or Composio integration').

Remove implementation details ('Always search tools first') and replace with user-facing capability descriptions.

Dimension	Reasoning	Score
Specificity	The description uses vague language like 'Automate Aero Workflow tasks' without specifying what concrete actions are possible. 'Search tools first for current schemas' is an implementation detail, not a capability description.	1 / 3
Completeness	The 'what' is extremely vague ('Automate tasks') and there is no 'Use when...' clause or equivalent trigger guidance. The instruction to 'search tools first' is operational guidance, not selection criteria.	1 / 3
Trigger Term Quality	Contains some relevant keywords ('Aero Workflow', 'Rube MCP', 'Composio') but these are technical/product names rather than natural terms users would say. Missing common variations or task-oriented language.	2 / 3
Distinctiveness Conflict Risk	The specific product names (Aero Workflow, 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

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 teaches Aero Workflow automation through Rube MCP. It excels at workflow clarity with explicit validation steps and provides good progressive disclosure. The main weakness is that the tool call examples are pseudo-code patterns rather than executable code in a specific language, though this may be intentional given the MCP context.

Suggestions

Consider showing one complete executable example in a specific language/client (e.g., Python with MCP client) to make the patterns more concrete and copy-paste ready

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient, avoiding explanations of basic concepts. Every section serves a purpose with no padding or unnecessary context about what Aero Workflow or Composio are.	3 / 3
Actionability	Provides concrete tool call patterns with specific parameters, but uses pseudo-code style rather than actual executable code. The examples show structure but aren't copy-paste ready for any specific programming language or MCP client.	2 / 3
Workflow Clarity	Clear 3-step workflow with explicit sequence (discover → check connection → execute). Includes validation checkpoint (verify ACTIVE status before executing) and the Known Pitfalls section provides error prevention guidance.	3 / 3
Progressive Disclosure	Well-organized with clear sections progressing from prerequisites to setup to core patterns. External reference to toolkit docs is one level deep and clearly signaled. Quick reference table provides efficient navigation for common operations.	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.