astica-ai-automation
Automate Astica AI tasks via Rube MCP (Composio). Always search tools first for current schemas.
Install with Tessl CLI
npx tessl i github:ComposioHQ/awesome-claude-skills --skill astica-ai-automation75
Quality
70%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Optimize this skill with Tessl
npx tessl skill review --optimize ./composio-skills/astica-ai-automation/SKILL.mdDiscovery
N/ABased on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
Something went wrong
Implementation
70%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a solid structure for Astica AI automation with clear workflow sequencing and good organization. However, it relies on placeholder-style examples rather than concrete, executable code, and contains some redundancy between sections. The Known Pitfalls section is valuable but the core examples could be more actionable.
Suggestions
Replace placeholder arguments like '/* schema-compliant args from search results */' with a concrete example showing actual Astica AI parameters (e.g., image analysis with specific fields)
Consolidate the 'Tool Discovery' and 'Core Workflow Pattern Step 1' sections to eliminate redundancy
Add a complete end-to-end example showing a real Astica AI task (e.g., analyzing an image) with actual tool slugs and arguments
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some redundancy - the 'Core Workflow Pattern' section largely repeats information from Setup and Tool Discovery sections. The quick reference table adds value but some explanatory text could be tightened. | 2 / 3 |
Actionability | Provides concrete tool call patterns with parameter examples, but uses pseudocode-style notation rather than actual executable code. The arguments are shown as placeholders (e.g., '/* schema-compliant args from search results */') rather than concrete examples. | 2 / 3 |
Workflow Clarity | Clear 3-step workflow with explicit sequencing (discover → check connection → execute). Includes validation checkpoint ('Confirm connection status shows ACTIVE before running any workflows') and the Known Pitfalls section addresses error prevention. | 3 / 3 |
Progressive Disclosure | Well-structured with clear sections progressing from prerequisites to setup to workflow to pitfalls. External reference to toolkit docs is one level deep and clearly signaled. Quick reference table provides scannable summary. | 3 / 3 |
Total | 10 / 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.