CtrlK
BlogDocsLog inGet started
Tessl Logo

amplitude-automation

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

78

1.23x
Quality

72%

Does it follow best practices?

Impact

83%

1.23x

Average score across 3 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/all-skills/skills/amplitude-automation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 a well-structured, actionable reference with concrete tool sequences, parameters, pitfalls, and an async validation loop; its main limitations are recurring pitfall duplication and missing full example payloads for most workflows.

DimensionReasoningScore

Conciseness

The body is action-oriented and assumes Claude's competence (no primers on what Amplitude/events/cohorts are); the only trim opportunity is that pitfall content recurs across per-workflow sections, 'Common Patterns', and 'Known Pitfalls'.

4 / 5

Actionability

Each workflow gives a numbered tool sequence plus named, typed key parameters and one concrete JSON example for IDENTIFY, but most workflows lack a full example payload, leaving minor gaps.

4 / 5

Workflow Clarity

Steps are explicitly sequenced with validation in setup ("Confirm connection status shows ACTIVE") and an async feedback loop for cohort updates ("Repeat step 2 until status is 'complete' or 'error'"), though event-ingestion batch sends have no verification checkpoint.

4 / 5

Progressive Disclosure

A single well-organized file with clear section headers and a Quick Reference table for navigation; no nested references, though at ~220 lines it is slightly long for a monolithic SKILL.md with no bundle files to offload detail into.

4 / 5

Total

16

/

20

Passed

Description

70%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 is distinctive and lists concrete Amplitude capabilities, but it omits an explicit activation/trigger clause, which caps completeness and leaves the "when to use" question unanswered.

Suggestions

Add a 'Use when...' clause with concrete trigger phrases, e.g. 'Use when the user wants to send or query Amplitude analytics, inspect a user's activity, or manage cohorts'.

Lead with specific verbs per capability (e.g. 'Send events, retrieve user activity, manage cohorts, set user properties') instead of the generic 'Automate Amplitude tasks'.

Include natural synonyms such as 'product analytics', 'event tracking', and 'user segments' to broaden trigger coverage.

DimensionReasoningScore

Specificity

Enumerates four concrete capability areas ("events, user activity, cohorts, user identification") but the governing verb is generic ("Automate Amplitude tasks"), leaving minor coverage gaps versus a comprehensive action list.

4 / 5

Completeness

The "what" is clear ("Automate Amplitude tasks via Rube MCP (Composio): events, user activity, cohorts, user identification") but there is no "Use when..." clause or equivalent explicit trigger guidance, so completeness is capped at 3.

3 / 5

Trigger Term Quality

"Amplitude", "events", "cohorts", and "user activity" are natural terms a user would say, but common synonyms such as "product analytics", "event tracking", or "user segments" are absent.

4 / 5

Distinctiveness Conflict Risk

"Amplitude" plus "Rube MCP (Composio)" carves out a narrow, unambiguous niche with minimal overlap risk against other skills.

5 / 5

Total

16

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
davepoon/buildwithclaude
Reviewed

Table of Contents

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.