amplitude-automation

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

Quality

60%

Does it follow best practices?

Impact

Pending

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

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 and distinct niche (Amplitude automation via Rube MCP/Composio) which minimizes conflict risk, but falls short on specificity of actions and completeness. The listed capabilities are category-level rather than concrete actions, and the description lacks an explicit 'Use when...' clause to guide skill selection.

Suggestions

Add a 'Use when...' clause such as 'Use when the user asks about Amplitude analytics, tracking events, querying user activity, managing cohorts, or identifying users in Amplitude.'

Make actions more concrete by specifying verbs, e.g., 'Query event data, look up user activity, create and manage cohorts, identify users' instead of just listing nouns.

Include natural trigger terms users might say, such as 'analytics', 'track', 'funnel', 'segment', or 'Amplitude dashboard'.

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 instruction to 'always search tools first' is operational guidance rather than a trigger condition. Per rubric, missing 'Use when' caps completeness at 2.	2 / 3
Trigger Term Quality	Includes relevant keywords like 'Amplitude', 'events', 'user activity', 'cohorts', and 'user identification', but these are somewhat generic analytics terms. Missing natural user phrases like 'track events', 'analytics', 'funnel', 'segment users', or file/format references 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	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 solid skill that clearly documents Amplitude workflows with good sequencing and helpful pitfall callouts. Its main weaknesses are redundancy (pitfalls repeated in multiple places), lack of fully executable examples with concrete parameter values, and being a single long file that could benefit from splitting detailed reference material into separate documents.

Suggestions

Consolidate pitfalls into a single section or keep only workflow-specific pitfalls inline and remove the duplicated 'Known Pitfalls' section to reduce redundancy.

Add at least one fully concrete tool invocation example per core workflow showing actual parameter values (e.g., a complete RUBE tool call with realistic event data).

Consider extracting the detailed per-workflow documentation and common patterns into a separate reference file, keeping SKILL.md as a concise overview with the quick reference table and setup instructions.

Remove the empty 'When to Use' section at the bottom—it adds no information beyond what the description already provides.

Dimension	Reasoning	Score
Conciseness	The skill is reasonably well-structured but includes some redundancy—pitfalls are repeated across individual workflows and then again in the 'Known Pitfalls' section (e.g., user ID resolution, timestamps). The 'When to Use' footer adds no value. Some explanations could be tightened, but overall it's not excessively verbose.	2 / 3
Actionability	Tool sequences and key parameters are clearly listed, which is helpful. However, there are no fully executable code/command examples—the 'Common Patterns' section uses pseudocode-style numbered steps rather than actual tool invocations with concrete parameter values. The JSON example for user properties is a good start but is the only concrete data structure shown.	2 / 3
Workflow Clarity	Multi-step workflows are clearly sequenced with explicit ordering (e.g., FIND_USER before GET_USER_ACTIVITY). The async cohort pattern includes a proper feedback loop (repeat status check until complete/error). Prerequisite steps are labeled, and the ID resolution pattern is well-documented as a required preliminary step.	3 / 3
Progressive Disclosure	The content is well-organized with clear sections and a quick reference table, but it's a long monolithic document (~180 lines of substantive content) with significant repetition. The pitfalls, common patterns, and per-workflow pitfalls could be split into separate reference files. There are no references to external files for deeper content.	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: 636b862

Reviewed: 3 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.