axonaut-automation

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

Quality

53%

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/axonaut-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. It names the platform (Axonaut) but fails to specify what actions are possible or when Claude should use this skill. The operational instruction about searching tools first doesn't help with skill selection.

Suggestions

Add specific concrete actions like 'Create contacts, manage invoices, track deals, update company records in Axonaut'

Add a 'Use when...' clause with trigger terms like 'Axonaut', 'CRM automation', 'invoice management', 'contact sync'

Include natural user language variations users might say when needing this skill (e.g., 'customer management', 'sales pipeline', 'billing')

Dimension	Reasoning	Score
Specificity	The description says 'Automate Axonaut tasks' which is extremely vague - it doesn't specify what tasks can be automated (contacts, invoices, deals, etc.). No concrete actions are listed.	1 / 3
Completeness	The 'what' is vague ('automate tasks') and there is no 'Use when...' clause or explicit trigger guidance. The instruction to 'search tools first' is operational guidance, not a trigger condition.	1 / 3
Trigger Term Quality	Includes 'Axonaut' and 'Rube MCP' as specific terms, but lacks natural user language. Users might say 'CRM', 'invoices', 'contacts', or specific Axonaut features rather than 'Axonaut tasks'.	2 / 3
Distinctiveness Conflict Risk	'Axonaut' and 'Rube MCP (Composio)' provide some distinctiveness, but 'automate tasks' is generic enough to potentially conflict with other automation or CRM-related 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 Axonaut automation through Rube MCP. It excels at workflow clarity with explicit validation steps and provides good progressive disclosure. The main weakness is that tool call examples use placeholder syntax rather than fully concrete, executable examples with realistic parameter values.

Suggestions

Replace placeholder comments like '/* schema-compliant args from search results */' with a concrete example showing actual Axonaut-specific parameters (e.g., creating a contact or invoice)

Add one complete end-to-end example showing a real Axonaut task from search through execution with actual field values

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient, avoiding explanations of what Axonaut or Composio 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 and comments like '/* schema-compliant args */' reduce copy-paste readiness.	2 / 3
Workflow Clarity	Clear 3-step workflow with explicit sequence (discover → check connection → execute). Setup section includes validation checkpoint (confirm ACTIVE status before proceeding). Known pitfalls section reinforces validation requirements.	3 / 3
Progressive Disclosure	Well-organized with clear sections progressing from prerequisites to setup to workflow to pitfalls. External reference to Composio docs is one level deep. 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: 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.