CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

astica-ai-automation

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

52

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./composio-skills/astica-ai-automation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 a lean, well-structured overview with concrete RUBE MCP invocations, a clear sequenced workflow, and real validation checkpoints for the connection step. Its main weakness is repeated 'search first' messaging and placeholder slots in the execute step rather than fully concrete examples.

Suggestions

Consolidate the 'always search tools first' guidance into a single stated rule instead of repeating it across Prerequisites, Tool Discovery, Known Pitfalls, and Quick Reference.

Show one concrete end-to-end execute example with a real discovered tool slug and populated arguments so Step 3 is copy-paste ready rather than placeholder-driven.

Add a brief failure-recovery note for tool execution errors (e.g., re-search schemas, re-check connection) to close the validation feedback loop.

DimensionReasoningScore

Conciseness

The body is mostly efficient with concise code blocks and no concept explanations, but 'search tools first' is restated in Prerequisites, Tool Discovery, Known Pitfalls, and Quick Reference, which is removable repetition that could be tightened.

3 / 5

Actionability

Concrete RUBE_* calls with real parameter fields are given throughout, but Step 3 leaves the tool slug as 'TOOL_SLUG_FROM_SEARCH' and arguments as a placeholder comment, so it is mostly executable with minor gaps rather than fully copy-paste ready.

4 / 5

Workflow Clarity

The Setup and Core Workflow Pattern give a clear sequenced process with validation checkpoints ('Confirm connection status shows ACTIVE before running any workflows', 'Verify... ACTIVE status before executing tools'), satisfying the batch-operation validation rule, though no explicit execute-failure feedback loop is specified.

4 / 5

Progressive Disclosure

The body is well-organized into clearly labeled sections (Prerequisites, Setup, Tool Discovery, Core Workflow, Known Pitfalls, Quick Reference) with no nested references and a single external toolkit-docs link; it is a clean self-contained overview with only minor organization gaps.

4 / 5

Total

15

/

20

Passed

Description

48%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 a clear niche and mechanism but relies on the generic verb 'Automate... tasks' without concrete capabilities or a 'Use when' trigger clause. It is distinctive but light on specificity and trigger guidance.

Suggestions

Replace 'tasks' with 2-3 concrete Astica AI operations (e.g., 'transcribe, analyze, and moderate audio/video') so the capability is specific.

Add an explicit trigger clause such as 'Use when the user asks to automate Astica AI operations or work with the astica_ai toolkit' to satisfy the 'when' half of completeness.

Include natural synonyms or file/use-case terms users might say to broaden trigger-term coverage beyond the product name.

DimensionReasoningScore

Specificity

The phrase 'Automate Astica AI tasks' names the domain and mechanism (Rube MCP/Composio) but the only action is the generic 'Automate... tasks' with no concrete operations listed; it sits at the 'names domain, actions minimal/generic' anchor rather than the 3-anchor which requires 1-2 concrete actions.

2 / 5

Completeness

It states a clear 'what' ('Automate Astica AI tasks via Rube MCP (Composio)') but offers no 'Use when...' or equivalent trigger guidance, and the rubric explicitly caps completeness at 3 when that clause is missing.

3 / 5

Trigger Term Quality

'Astica AI', 'Automate', 'tasks' are relevant product-aligned keywords a user would say, but there are no synonyms or natural phrase variations beyond the product name, matching the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

Astica AI plus Rube MCP/Composio is a clear niche with distinct triggers and minimal conflict risk, but it could overlap with sibling Composio/Rube automation skills, placing it just below the fully-distinct 5 anchor.

4 / 5

Total

12

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

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/astica-ai-automation/SKILL.md

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.