abstract-automation

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

2.37x

Quality

51%

Does it follow best practices?

Impact

88%

2.37x

Average score across 3 eval scenarios

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./composio-skills/abstract-automation/SKILL.md

Quality

Content

65%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is well-structured and actionable with concrete Rube MCP tool-call examples and a clear connection-validation checkpoint, but it carries some redundancy between the discovery/setup sections and lacks a post-execution verification loop for its batch execute step. Progressive disclosure is strong given the simple, self-contained scope.

Suggestions

Merge the standalone 'Tool Discovery' section into 'Step 1' to remove the duplicated RUBE_SEARCH_TOOLS block and tighten the body.

Add an explicit post-execution verification step after RUBE_MULTI_EXECUTE_TOOL (e.g., check returned status/errors and retry or surface failures) to satisfy the batch-operation feedback-loop expectation.

Consolidate 'Prerequisites' and 'Setup' which currently restate the connection and search-first guidance.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and free of concept over-explanation, but the 'Tool Discovery' section and 'Step 1: Discover Available Tools' duplicate the same RUBE_SEARCH_TOOLS block, and 'Prerequisites' overlaps with 'Setup'; it could be tightened, matching the 'mostly efficient but includes some unnecessary explanation' anchor.	3 / 5
Actionability	Concrete tool-call blocks with named parameters (RUBE_SEARCH_TOOLS, RUBE_MANAGE_CONNECTIONS, RUBE_MULTI_EXECUTE_TOOL) give mostly executable guidance, with only minor gaps such as the placeholder 'arguments: {/* schema-compliant args */}', fitting the 'mostly executable guidance with minor gaps' anchor.	4 / 5
Workflow Clarity	The Discover -> Check connection -> Execute sequence is clear with a connection-ACTIVE checkpoint, but the batch RUBE_MULTI_EXECUTE_TOOL step lacks an explicit post-execution verification/feedback loop, so the destructive/batch cap holds it at 3 rather than 4.	3 / 5
Progressive Disclosure	This is a single-purpose skill under/around the simple-skill threshold with no bundle files (references/, scripts/, assets/ absent) and no nested file references; its well-organized sections (Prerequisites, Setup, Tool Discovery, Core Workflow, Pitfalls, Quick Reference) earn the simple-skill exception for progressive disclosure.	5 / 5
	Total	15 / 20 Passed

Description

37%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description names the domain and integration mechanism but uses generic action language, omits an explicit 'Use when' trigger, and relies on technical jargon over natural user phrases. It is distinguishable but at risk of overlapping with sibling Composio toolkit skills.

Suggestions

Add an explicit trigger clause such as 'Use when the user asks to automate Abstract design-version tasks or manage Abstract comments/files'.

Replace the generic 'Automate Abstract tasks' with concrete actions (e.g., 'list, retrieve, and comment on Abstract files and collections').

Include natural synonyms users say (e.g., 'Abstract design files', 'Abstract collections', 'version control') to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	The phrase 'Automate Abstract tasks via Rube MCP (Composio)' names the domain and mechanism but the action ('Automate Abstract tasks') is generic with no concrete operations listed, matching the 'names the domain but actions are minimal or generic' anchor rather than the 3-anchor which requires 1-2 concrete actions.	2 / 5
Completeness	It states a clear 'what' ('Automate Abstract tasks via Rube MCP (Composio)') but provides no 'Use when...' trigger clause, so per the missing-trigger cap it cannot exceed 3 and matches the 'clear what but when missing' anchor.	3 / 5
Trigger Term Quality	Keywords are largely technical jargon ('Rube MCP', 'Composio', 'current schemas') with only the generic phrase 'Abstract tasks' as a natural term; it is missing the common variations or synonyms a user would naturally say, fitting the 'one or two generic keywords' anchor better than the 3-anchor's 'some relevant keywords'.	2 / 5
Distinctiveness Conflict Risk	The product name 'Abstract' combined with 'Rube MCP (Composio)' is somewhat specific, but this is one of a family of near-identical Composio toolkit skills and the bare word 'Abstract' is ambiguous, so it 'could still overlap with similar skills' rather than being clearly distinct.	3 / 5
	Total	10 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: ComposioHQ/awesome-claude-skills
Path: composio-skills/abstract-automation/SKILL.md
Commit: be2a406

Reviewed: 28 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.