abstract-automation
Automate Abstract tasks via Rube MCP (Composio). Always search tools first for current schemas.
Install with Tessl CLI
npx tessl i github:haniakrim21/everything-claude-code --skill abstract-automation60
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
0%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 fails on all dimensions. It provides no concrete capabilities, uses technical jargon instead of user-facing language, lacks any trigger guidance, and is too generic to distinguish from other automation skills. The phrase 'Abstract tasks' appears to be a placeholder or typo rather than meaningful content.
Suggestions
Replace 'Automate Abstract tasks' with specific concrete actions this skill can perform (e.g., 'Create calendar events, send emails, manage tasks across connected apps').
Add a 'Use when...' clause with natural trigger terms users would actually say (e.g., 'Use when the user wants to automate workflows, connect apps, or trigger actions across services').
Remove or explain technical terms like 'Rube MCP' and 'Composio' - describe capabilities in user-facing language rather than implementation details.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'Automate Abstract tasks' without specifying what concrete actions can be performed. 'Abstract tasks' is meaningless without context. | 1 / 3 |
Completeness | The 'what' is extremely vague ('Automate Abstract tasks') and there is no 'Use when...' clause or explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Contains technical jargon ('Rube MCP', 'Composio', 'schemas') that users would not naturally say. No common user-facing keywords are present. | 1 / 3 |
Distinctiveness Conflict Risk | 'Automate Abstract tasks' is so generic it could conflict with virtually any automation-related skill. The only distinguishing element is the tool name 'Rube MCP (Composio)' which users wouldn't know to reference. | 1 / 3 |
Total | 4 / 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 Abstract automation via 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 structural templates rather than fully executable code for specific Abstract operations, though this may be intentional given the dynamic nature of tool discovery.
Suggestions
Consider adding one concrete end-to-end example showing a specific Abstract operation (e.g., creating a project) with actual tool slugs and arguments that would be returned from RUBE_SEARCH_TOOLS
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, avoiding unnecessary explanations of what Abstract or Composio are. Every section serves a purpose and assumes Claude understands MCP concepts and API patterns. | 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 for any specific Abstract operation. | 2 / 3 |
Workflow Clarity | Clear 3-step workflow with explicit validation checkpoint (check connection status shows ACTIVE before proceeding). The Known Pitfalls section provides error prevention guidance and the sequence is unambiguous. | 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%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 | |
- Reviewed
Table of Contents
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.