alchemy-automation
Automate Alchemy 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 alchemy-automation62
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
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 and lacks essential components for effective skill selection. It names specific tools (Alchemy, Rube MCP, Composio) but fails to explain what actions can be performed or when the skill should be triggered. The procedural instruction about searching tools is misplaced in a description field.
Suggestions
Add specific concrete actions that can be performed with Alchemy (e.g., 'Deploy smart contracts, query blockchain data, manage webhooks').
Add a 'Use when...' clause with natural trigger terms like 'blockchain', 'web3', 'smart contract', 'Alchemy API', or whatever user scenarios apply.
Remove the procedural instruction ('Always search tools first') as this belongs in the skill body, not the description.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'Automate Alchemy tasks' without specifying what concrete actions can be performed. 'Always search tools first' is procedural guidance, not a capability description. | 1 / 3 |
Completeness | The 'what' is extremely vague ('Automate Alchemy tasks') and there is no 'Use when...' clause or equivalent trigger guidance. The description fails to answer either question adequately. | 1 / 3 |
Trigger Term Quality | Contains some relevant keywords ('Alchemy', 'Rube MCP', 'Composio') but these are technical/product names rather than natural terms users would say. Missing common variations or user-facing language. | 2 / 3 |
Distinctiveness Conflict Risk | The specific product names (Alchemy, Rube MCP, Composio) provide 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 communicates how to automate Alchemy tasks via Rube MCP. The workflow is clear with proper validation steps, and the content respects token budget. The main weakness is that tool call examples are more template-like than fully executable, though this may be intentional given the dynamic nature of tool discovery.
Suggestions
Consider adding one complete end-to-end example with realistic argument values to make the workflow more immediately actionable
The tool call examples could include expected response structure to help Claude validate successful execution
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, avoiding explanations of basic concepts. Every section serves a purpose with no padding or unnecessary context about what Alchemy or Composio are. | 3 / 3 |
Actionability | Provides concrete tool call patterns with specific parameters, but examples are pseudo-code style rather than fully executable. The tool calls show structure but lack complete, copy-paste ready examples with realistic values. | 2 / 3 |
Workflow Clarity | Clear 3-step workflow with explicit sequencing (discover → check connection → execute). Includes validation checkpoint (verify ACTIVE status before executing) and the Known Pitfalls section provides error prevention guidance. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections progressing from prerequisites to setup to workflow to pitfalls. Quick reference table provides scannable summary. External link to toolkit docs is one level deep and clearly signaled. | 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.