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:Lingjie-chen/MT5 --skill amplitude-automation

What are skills?

Review — 60%

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/skill

Learn more

Validation — 10 / 11 Passed

Validation for skill structure

SKILL.md

Review

Evals

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 domain (Amplitude automation via specific tooling) and lists capability categories, making it distinguishable from other skills. However, it lacks explicit trigger guidance ('Use when...') and could benefit from more specific action verbs and natural user language variations to improve discoverability.

Suggestions

Add an explicit 'Use when...' clause with trigger terms like 'when the user asks about Amplitude analytics, tracking events, or managing cohorts'

Include natural language variations users might say: 'analytics', 'product analytics', 'user tracking', 'behavioral data'

Make actions more concrete: instead of 'events', specify 'track events, query event data, create custom events'

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 specific actions like 'create cohorts' or 'track user events'.	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', 'user activity', 'cohorts', but missing common variations users might say like 'analytics', 'tracking', 'product analytics', or 'behavioral data'.	2 / 3
Distinctiveness Conflict Risk	The combination of 'Amplitude', 'Rube MCP', and 'Composio' creates a clear niche that is unlikely to conflict with other skills. The specific platform mentions make it distinctly identifiable.	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 documentation of pitfalls. However, it's verbose with repeated information across sections, and lacks concrete executable examples showing actual tool invocations with complete parameters. The structure is good but the content could be more concise.

Suggestions

Add complete, executable tool call examples showing actual parameter structures (e.g., full RUBE_SEARCH_TOOLS and AMPLITUDE_SEND_EVENTS invocations with realistic data)

Consolidate repeated pitfall information (user ID resolution is explained 3+ times) into a single 'Common Pitfalls' section

Consider moving detailed workflow documentation to separate files (e.g., WORKFLOWS.md) and keeping SKILL.md as a concise overview with the quick reference table

Dimension	Reasoning	Score
Conciseness	The skill is reasonably efficient but includes some redundancy - pitfalls are repeated across sections (user ID resolution mentioned multiple times), and some explanations could be tighter. The quick reference table at the end 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 parameter structures.	2 / 3
Workflow Clarity	Workflows are clearly sequenced with numbered steps, explicit tool sequences marked as [Required]/[Optional]/[Prerequisite], and includes async operation patterns with proper feedback loops (check status until complete/error). The ID resolution patterns are well-documented.	3 / 3
Progressive Disclosure	Content is well-organized with clear sections, but it's a monolithic document that could benefit from splitting detailed workflow documentation into separate files. The quick reference table is good, but 200+ lines of content in one file is borderline excessive.	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

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