abyssale-automation

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

16.66x

Quality

53%

Does it follow best practices?

Impact

100%

16.66x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./composio-skills/abyssale-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 fails to explain what Abyssale is, what specific tasks can be automated, or when Claude should choose this skill. The technical jargon (Rube MCP, Composio) won't match natural user requests.

Suggestions

Add specific capabilities: what can Abyssale actually do? (e.g., 'Generate dynamic images, create personalized banners, automate visual content creation')

Add a 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when the user needs to create dynamic images, personalized graphics, or automated visual content')

Briefly explain what Abyssale is for users unfamiliar with the platform to improve trigger matching

Dimension	Reasoning	Score
Specificity	The description uses vague language like 'Automate Abyssale tasks' without specifying what concrete actions can be performed. No specific capabilities are listed beyond generic 'tasks'.	1 / 3
Completeness	The 'what' is extremely vague ('Automate Abyssale tasks') and there is no 'Use when...' clause or explicit trigger guidance. The instruction to 'search tools first' is operational guidance, not a usage trigger.	1 / 3
Trigger Term Quality	Includes 'Abyssale', 'Rube MCP', and 'Composio' as technical terms, but lacks natural user language. Users might say 'Abyssale' but unlikely to mention 'Rube MCP' or 'Composio' in requests.	2 / 3
Distinctiveness Conflict Risk	The mention of 'Abyssale' and 'Rube MCP (Composio)' provides 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 guides Claude through Abyssale 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 Abyssale-specific arguments (e.g., template ID, output format)

Add one complete end-to-end example showing a real Abyssale task (e.g., generating an image from a template) with actual tool slugs and arguments

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient, avoiding explanations of what Abyssale or MCP are. Every section provides actionable information without padding or unnecessary context.	3 / 3
Actionability	Provides concrete tool call patterns with field names, but examples use pseudo-syntax rather than actual executable code. The argument placeholders like '/* schema-compliant args */' reduce copy-paste readiness.	2 / 3
Workflow Clarity	Clear 3-step workflow with explicit sequencing (discover → check connection → execute). Includes validation checkpoint for connection status before proceeding, and the 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 toolkit docs linked appropriately without deep nesting.	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.