amplitude-automation

Automate Amplitude tasks via Rube MCP (Composio): events, user activity, cohorts, user identification. Always search tools first for current schemas.

Quality

51%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/antigravity-amplitude-automation/SKILL.md

Quality

Discovery

40%

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 and distinct niche (Amplitude automation via Rube MCP/Composio) which minimizes conflict risk, but it lacks a 'Use when...' clause and provides only terse noun-phrase capabilities rather than concrete actions. The trigger terms cover the core domain but miss natural user language variations around analytics and tracking.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Amplitude analytics, tracking events, viewing user activity, managing cohorts, or identifying users.'

Expand trigger terms to include natural user language like 'analytics', 'product analytics', 'tracking', 'funnel', 'retention', and 'Amplitude dashboard'.

Convert noun phrases into concrete verb-driven actions, e.g., 'Track and query events, look up user activity, create and manage cohorts, identify and resolve users.'

Dimension	Reasoning	Score
Specificity	Lists domain-specific actions (events, user activity, cohorts, user identification) but they are terse noun phrases rather than concrete verb-driven actions. It names the domain (Amplitude via Rube MCP/Composio) and some capabilities but lacks detail on what specific operations are performed.	2 / 3
Completeness	It describes what the skill does (automate Amplitude tasks) but has no explicit 'Use when...' clause or equivalent trigger guidance. The instruction to 'always search tools first' is an implementation detail, not a trigger condition. Missing 'when' caps this at 2, but the 'what' is also quite thin, bringing it to 1.	1 / 3
Trigger Term Quality	Includes relevant keywords like 'Amplitude', 'events', 'user activity', 'cohorts', 'user identification', 'Composio', and 'Rube MCP'. However, it misses common user variations like 'analytics', 'tracking', 'product analytics', 'funnel', or 'retention' that users might naturally say.	2 / 3
Distinctiveness Conflict Risk	The combination of 'Amplitude', 'Rube MCP', and 'Composio' creates a very specific niche that is unlikely to conflict with other skills. This is clearly distinguishable from general analytics or data processing skills.	3 / 3
	Total	8 / 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.

The skill provides solid workflow structure with clear tool sequences, prerequisite identification, and async operation handling. However, it suffers from repetition (pitfalls stated twice), lacks truly executable examples (mostly pseudocode steps), and could be more concise by eliminating redundant explanations and boilerplate sections. The content is functional but could be tightened significantly.

Suggestions

Replace pseudocode tool sequences with actual tool invocation examples showing realistic parameter values (e.g., a complete RUBE_SEARCH_TOOLS call with expected response structure).

Consolidate pitfalls into a single section rather than repeating them in both individual workflows and the 'Known Pitfalls' section—reference the central section from workflows instead.

Remove the boilerplate 'When to Use' and 'Limitations' sections at the bottom, which add no actionable information beyond what the description and prerequisites already convey.

Trim explanatory text that Claude already knows (e.g., 'Events are processed asynchronously; successful API response does not mean data is immediately queryable') to keep focus on Amplitude-specific gotchas.

Dimension	Reasoning	Score
Conciseness	The skill is reasonably structured but contains significant repetition—pitfalls are stated in individual workflows and then repeated in the 'Known Pitfalls' section. The 'Common Patterns' section re-explains ID resolution already covered in workflow #2. The boilerplate 'When to Use' and 'Limitations' sections add little value. Some explanations (e.g., what event categories are) are unnecessary for Claude.	2 / 3
Actionability	Tool names and parameter lists are concrete and useful, but the code examples are pseudocode-style numbered steps rather than executable commands. The JSON example for user properties is helpful but is the only truly concrete snippet. The skill describes tool sequences but doesn't show actual tool invocation syntax with realistic parameter values.	2 / 3
Workflow Clarity	Multi-step workflows are clearly sequenced with explicit tool ordering, prerequisite steps are marked, and the async cohort pattern includes a proper feedback loop (repeat status check until complete/error). Each workflow has a clear 'when to use' trigger and pitfalls that serve as validation guidance.	3 / 3
Progressive Disclosure	The content is well-organized with clear sections and a quick reference table, but it's a monolithic document with no references to external files. At ~180 lines, the detailed pitfalls and common patterns sections could be split out. However, with no bundle files provided, there's nothing to reference, which partially justifies the inline approach.	2 / 3
	Total	9 / 12 Passed

Validation

90%

Warnings & errors only

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: boisenoise/skills-collections
Commit: 95574f3

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

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.