amplitude-automation
Automate Amplitude tasks via Rube MCP (Composio): events, user activity, cohorts, user identification. Always search tools first for current schemas.
53
60%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/antigravity-awesome-skills-claude/skills/amplitude-automation/SKILL.mdQuality
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 a specific MCP tool) and lists relevant domain terms, making it reasonably distinctive. However, it lacks concrete action verbs describing what it actually does with events/cohorts/etc., and critically omits an explicit 'Use when...' clause that would help Claude know when to select this skill.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Amplitude analytics, tracking events, querying user activity, managing cohorts, or identifying users.'
Replace category labels with concrete actions, e.g., 'Query event data, look up user activity, create and manage cohorts, identify users' instead of just listing nouns.
Include additional natural trigger terms users might say, such as 'analytics', 'tracking', 'funnel analysis', or 'Amplitude data'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Amplitude via Rube MCP/Composio) and lists some actions (events, user activity, cohorts, user identification), but these are more like category labels than concrete actions. It doesn't specify what it does with events or cohorts (create, query, delete?). | 2 / 3 |
Completeness | The 'what' is partially addressed (automate Amplitude tasks), but there is no explicit 'Use when...' clause or equivalent trigger guidance. The description only implies when it should be used. Per rubric guidelines, missing 'Use when...' caps completeness at 2. | 2 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Amplitude', 'events', 'user activity', 'cohorts', and 'user identification', which are natural terms. However, it's missing common variations users might say like 'analytics', 'tracking', 'funnel', 'retention', or 'Amplitude API'. | 2 / 3 |
Distinctiveness Conflict Risk | The description is quite distinctive by specifying Amplitude via Rube MCP (Composio), which is a very specific integration. It's unlikely to conflict with other skills given the narrow tool and platform combination. | 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 is a competent skill file with clear workflow sequencing and good coverage of Amplitude operations via Rube MCP. Its main weaknesses are repetition (pitfalls stated in individual workflows and again in a summary section) and lack of concrete executable examples for MCP tool calls. The content would benefit from deduplication and splitting detailed parameter references into separate files.
Suggestions
Deduplicate pitfalls: consolidate user ID, timestamp, and async operation warnings into the 'Known Pitfalls' section only, and reference it from individual workflows instead of repeating.
Add concrete, copy-paste-ready MCP tool call examples (with actual parameter values) for at least the Send Events and Find User workflows instead of pseudocode steps.
Consider extracting the detailed parameter lists and pitfalls into a separate REFERENCE.md file, keeping SKILL.md as a concise overview with links to details.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably structured but contains significant repetition—pitfalls about user IDs, timestamps, and async operations are stated multiple times across individual workflows and then again in the 'Known Pitfalls' section. The 'When to Use' and 'Limitations' boilerplate at the end adds little value. Some explanations (e.g., what event categories are) are unnecessary for Claude. | 2 / 3 |
Actionability | Tool names and parameters are clearly specified, and the JSON example for user properties is helpful. However, most 'tool sequences' are described in pseudocode-like numbered lists rather than showing actual MCP tool call syntax with concrete parameter examples. The common patterns section uses plain text steps rather than executable examples. | 2 / 3 |
Workflow Clarity | Multi-step workflows are clearly sequenced with explicit prerequisite steps (e.g., FIND_USER before GET_USER_ACTIVITY). The async cohort pattern includes a proper feedback loop (repeat status check until complete/error). The setup section has a clear verification sequence. Validation checkpoints are present where needed. | 3 / 3 |
Progressive Disclosure | The content is well-organized with clear sections and a quick reference table, but it's a monolithic document (~180 lines) with no references to external files. The repeated pitfalls and detailed parameter lists for each workflow could be split into separate reference files, keeping SKILL.md as a leaner 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 | |
- Repository
- sickn33/antigravity-awesome-skills
- Commit
a4d3e3a
- 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.