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.

56

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

62%

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

The content is well-sequenced with strong validation checkpoints, but loses points to redundant pitfalls, schema-deferred concrete values, and a monolithic inline structure with no progressive disclosure.

Suggestions

Deduplicate pitfalls: keep them once per workflow or consolidate solely in 'Known Pitfalls' rather than both.

Replace schema-deferral notes ('check schema for max events', 'parse defensively') with concrete default values or explicit bounds where known.

Consider moving per-workflow parameter detail into reference files linked from the overview to improve progressive disclosure.

DimensionReasoningScore

Conciseness

The body is mostly lean and assumes competence, but pitfalls are repeated across workflows and again in 'Known Pitfalls', the 'Quick Reference' table duplicates tool/param info, and the closing 'When to Use'/'Limitations' sections are low-value boilerplate that could be tightened.

2 / 3

Actionability

Tool sequences, parameter lists, and a concrete JSON example are provided, but guidance repeatedly defers concrete values to the schema ('check schema for maximum events', 'parse defensively'), so it is not fully copy-paste ready.

2 / 3

Workflow Clarity

Workflows are clearly sequenced with numbered tool steps and include explicit validation checkpoints ('Confirm connection status shows ACTIVE') and a feedback loop ('Repeat until status is complete or error') for async cohort operations.

3 / 3

Progressive Disclosure

No bundle files exist and the skill is a single well-organized but ~225-line document with all per-workflow API detail inline and no external references, matching the anchor where content that could be separate stays inline.

2 / 3

Total

9

/

12

Passed

Description

67%

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 specific and clearly niche but is capped by a missing explicit 'when to use' trigger clause and only moderate natural-term coverage.

Suggestions

Add a 'Use when...' clause with explicit trigger phrasings (e.g., 'Use when sending Amplitude events, finding users, or managing cohorts').

Include more natural user variations such as 'find a user', 'send events', and 'list cohorts' to broaden trigger coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete capability areas — 'events, user activity, cohorts, user identification' — tied to a specific domain, matching the anchor for listing several specific concrete actions rather than merely naming a domain.

3 / 3

Completeness

It clearly states what the skill does but lacks any 'Use when...' clause or equivalent explicit trigger guidance, which the rubric caps at 2.

2 / 3

Trigger Term Quality

Relevant analytics terms are present ('events', 'user activity', 'cohorts') but common user phrasings like 'send events', 'find a user', or 'cohort list' are missing, so coverage is partial rather than comprehensive.

2 / 3

Distinctiveness Conflict Risk

'Amplitude tasks via Rube MCP (Composio)' is a specific niche with distinct triggers unlikely to collide with other skills.

3 / 3

Total

10

/

12

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
boisenoise/skills-collections
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.