Name: amplitude
Rating: 56.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

amplitude

Amplitude integration. Manage Users, Events. Use when the user wants to interact with Amplitude data.

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/amplitude/SKILL.md

Quality

Content

68%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable with complete, copy-paste-ready CLI commands and well-organized sections, but it is held back by an unnecessary intro paragraph, a loose step numbering scheme, and missing verification steps for its batch data operations.

Suggestions

Add a verification/retry step after batch and export actions (e.g. re-query or check the response status) so batch workflows include an explicit feedback loop.

Fix the step numbering: label 'Step 2' explicitly (or remove the 'skip to Step 2' reference) and add a '1a' to pair with the '1b' subsection.

Trim the opening paragraph that explains what Amplitude is and who uses it, plus the filler line 'Use action names and parameters as needed.'

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient command examples and tables, but the opening paragraph over-explains what Amplitude is and who uses it, and 'Use action names and parameters as needed.' is vague filler that could be trimmed.	3 / 5
Actionability	Provides copy-paste-ready commands for every common case (install, login, connection ensure, action list/run, request) with full flag tables and a popular-actions table, fully executable and covering the common cases.	5 / 5
Workflow Clarity	There is a clear sequence with a connection-state feedback loop, but batch operations (track-events 'in batch', export-events) lack verification steps, and the batch-cap guideline caps workflow clarity at 3; the 'skip to Step 2' reference with no labeled Step 2 or '1a' also loosens the sequence.	3 / 5
Progressive Disclosure	No bundle files exist; the ~155-line body is well-organized into clear headed sections with easy navigation, but it is monolithic (popular-actions and proxy-flag tables inline) and over 50 lines, so it sits at good structure with minor gaps rather than the simple-skill 5.	4 / 5
	Total	15 / 20 Passed

Description

62%Weight 40%Scale 1-5

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 successfully answers both what and when with a distinct brand trigger, but it is generic in its action verbs and omits the analytics-specific keywords (funnels, cohorts, segmentation) that characterize real Amplitude use cases.

Suggestions

Replace the generic 'Manage Users, Events' with concrete Amplitude actions such as 'run funnel and segmentation analyses, export events, and query cohorts and user activity'.

Expand the 'Use when...' clause with concrete triggers, e.g. 'Use when the user wants to query Amplitude analytics, run funnel or segmentation reports, export events, or look up cohorts and user activity.'

Add natural analytics keywords (funnel, cohort, segmentation, charts, dashboards) so the description matches phrases users actually say.

Dimension	Reasoning	Score
Specificity	Names the domain ('Amplitude integration') and two actions ('Manage Users, Events'), but 'Manage' is a generic verb and coverage is not comprehensive, matching the '1-2 concrete actions' anchor rather than the 'several specific actions' anchor at 4.	3 / 5
Completeness	Explicitly states both what ('Amplitude integration. Manage Users, Events.') and when ('Use when the user wants to interact with Amplitude data.'), but the 'when' clause is generic rather than listing concrete triggers, so it stops short of the anchor 5 example.	4 / 5
Trigger Term Quality	Includes relevant keywords ('Amplitude', 'Users', 'Events', 'Amplitude data') but omits core analytics terms (funnel, cohort, segmentation, analytics) that the body's popular actions reveal, fitting 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	The 'Amplitude' brand is a clear niche with minimal conflict risk, yet the generic 'Manage Users, Events' portion could overlap with user-management or CRM skills, placing it at 'mostly distinct; minor overlap risk' rather than a clean 5.	4 / 5
	Total	14 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/amplitude/SKILL.md
Commit: f484c82

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.