amplitude-automation
Automate Amplitude tasks via Rube MCP (Composio): events, user activity, cohorts, user identification. Always search tools first for current schemas.
Install with Tessl CLI
npx tessl i github:sickn33/antigravity-awesome-skills --skill amplitude-automation67
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
57%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 identifies a clear niche (Amplitude automation via specific tooling) which makes it distinctive, but lacks the explicit trigger guidance needed for Claude to know when to select it. The capabilities listed are more categorical than action-specific, and the description would benefit from natural user language variations.
Suggestions
Add a 'Use when...' clause with trigger terms like 'Amplitude analytics', 'track events', 'product analytics', 'user behavior tracking'
Replace category nouns with specific action verbs: 'track events, query user activity, create/manage cohorts, identify users'
Include common synonyms users might say: 'analytics', 'tracking', 'behavioral data', 'product metrics'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Amplitude) and lists some actions (events, user activity, cohorts, user identification), but these are more like categories than concrete actions. Missing specific verbs like 'track', 'query', 'create', 'analyze'. | 2 / 3 |
Completeness | Describes what it does (automate Amplitude tasks) but lacks an explicit 'Use when...' clause. The instruction to 'search tools first' is operational guidance, not trigger guidance for when to select this skill. | 2 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Amplitude', 'events', 'cohorts', 'user activity' that users might say, but missing common variations like 'analytics', 'tracking', 'product analytics', or 'behavioral data'. | 2 / 3 |
Distinctiveness Conflict Risk | Clearly specific to Amplitude via Rube MCP/Composio - this is a distinct niche that wouldn't conflict with other analytics or automation skills due to the specific platform naming. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides comprehensive coverage of Amplitude operations with clear workflow sequences and good pitfall documentation. However, it's verbose for a skill file, lacks executable code examples for tool calls, and could be more concise by assuming Claude's understanding of basic concepts like async operations and API patterns.
Suggestions
Add concrete, executable tool call examples showing actual parameter values (e.g., a complete AMPLITUDE_SEND_EVENTS call with realistic event data)
Consolidate repeated pitfalls into a single section rather than duplicating across workflows (e.g., user_id vs internal ID is mentioned multiple times)
Consider splitting detailed workflow documentation into separate files, keeping SKILL.md as a concise overview with quick reference and links to detailed guides
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundancy (pitfalls repeated across sections, verbose explanations of concepts like async operations that Claude understands). The quick reference table duplicates information already covered in workflows. | 2 / 3 |
Actionability | Provides tool names and parameter descriptions but lacks executable code examples. The 'Example structure' JSON snippet is helpful, but most workflows describe steps abstractly rather than showing actual tool calls with complete parameters. | 2 / 3 |
Workflow Clarity | Multi-step processes are clearly sequenced with explicit prerequisites, tool sequences marked as [Required]/[Optional], and async operation patterns include proper status-checking loops. The ID resolution patterns provide clear feedback loops. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but everything is in a single monolithic file. The skill is quite long (~200 lines) and could benefit from splitting detailed workflow documentation into separate files with the main SKILL.md as an overview. | 2 / 3 |
Total | 9 / 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.