amplitude-automation

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

1.25x

Quality

60%

Does it follow best practices?

Impact

68%

1.25x

Average score across 3 eval scenarios

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 adequately identifies its niche (Amplitude automation via a specific MCP) and lists relevant task categories, making it reasonably distinctive. However, it lacks concrete action verbs, misses common user-facing trigger terms like 'analytics' or 'tracking', and doesn't include an explicit 'Use when...' clause to guide skill selection.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Amplitude analytics, event tracking, cohort analysis, or product metrics.'

Include more natural trigger terms users would say: 'analytics', 'tracking', 'product analytics', 'user behavior', 'funnel analysis'

Replace category nouns with specific action verbs: 'Track events, query user activity, create and manage cohorts, identify users'

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 categories than concrete actions. Missing specific verbs like 'track', 'query', 'create', 'export'.	2 / 3
Completeness	Describes what it does (automate Amplitude tasks) and includes a procedural note ('Always search tools first'), but lacks an explicit 'Use when...' clause. The when is only implied through the task categories listed.	2 / 3
Trigger Term Quality	Includes relevant keywords like 'Amplitude', 'events', 'cohorts', 'user activity' that users might say. However, 'Rube MCP' and 'Composio' are technical/internal terms unlikely to be used by end users, and common variations like 'analytics', 'tracking', 'product analytics' are missing.	2 / 3
Distinctiveness Conflict Risk	Clearly targets Amplitude specifically, which is a distinct product analytics platform. The mention of 'Rube MCP (Composio)' further narrows the scope. Unlikely to conflict with other skills unless there are multiple Amplitude-related 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 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 most operations, and could be more concise by assuming Claude's familiarity with concepts like async patterns and API conventions.

Suggestions

Add complete, executable tool call examples showing actual parameter structures rather than abstract descriptions (e.g., show a full RUBE_SEARCH_TOOLS call followed by AMPLITUDE_SEND_EVENTS with real parameters)

Consolidate the 'Known Pitfalls' section with workflow-specific pitfalls to reduce redundancy - currently user ID confusion is explained in multiple places

Consider splitting detailed workflow documentation into a separate WORKFLOWS.md file, keeping SKILL.md as a quick-start overview with the reference table

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 lists, 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 one file. The skill is quite long (~200 lines) and could benefit from splitting detailed workflow documentation into separate files, keeping SKILL.md as a concise overview.	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: 5c5ae21

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.