CtrlK
BlogDocsLog inGet started
Tessl Logo

diagnose-activation

Diagnose where new users fail to activate, identify the aha moment, measure time-to-value, and build a sized plan to move activation rate. Use when a PM needs to understand why signups don't convert to active users, find the aha moment, reduce time-to-value, or improve onboarding.

74

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

A tightly structured, highly actionable activation-diagnosis prompt with clear sequencing and validation checkpoints. Its only weakness is mild redundancy between the description, the bold summary, and the intro paragraph.

Suggestions

Collapse the bold opener and the intro paragraph into a single concise framing line to avoid restating the description.

Trim explanatory asides inside the prompt (e.g. the 90%-on-100-vs-70%-on-10000 illustration) where the instruction already conveys the principle.

DimensionReasoningScore

Conciseness

Mostly efficient domain-specific guidance with little generic concept padding, but the bold opener ("Find where new users fall off...") and the following intro paragraph largely restate the description, and the prompt template runs long enough that it could be tightened without losing clarity.

2 / 3

Actionability

Gives concrete, executable instruction with real math ("Signups x Step 1 Rate x Step 2 Rate = Activated Users") and contrastive examples ("Add a guided template selector as step 2" vs. "improve the onboarding experience"), fully actionable for an instruction-only skill.

3 / 3

Workflow Clarity

A precise 5-step sequence (Define Activation → Measure Funnel → Identify Blockers → Model Impact → Recommend Play) with explicit validation checkpoints ("stress-test it... If the answer is unclear or no, the definition is wrong") and a closing open-questions deliverable.

3 / 3

Progressive Disclosure

No bundle files exist, and the content is cleanly sectioned (Prompt Template, Steps 1–5, Output Format, Tips) with no material that needs splitting out; the single inline prompt template is the core deliverable and is appropriately kept whole.

3 / 3

Total

11

/

12

Passed

Description

100%

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, third-person, and complete, with an explicit trigger clause full of natural terms. It cleanly separates activation diagnosis from adjacent growth skills.

DimensionReasoningScore

Specificity

Names multiple concrete actions — "Diagnose where new users fail to activate, identify the aha moment, measure time-to-value, and build a sized plan to move activation rate" — matching the multi-action anchor rather than the single-domain level below.

3 / 3

Completeness

Explicitly answers both what (diagnose activation, find aha moment, measure time-to-value, build a sized plan) and when via an explicit "Use when a PM needs to..." trigger clause, satisfying the top anchor.

3 / 3

Trigger Term Quality

The "Use when..." clause surfaces natural phrasings a PM would actually say — "signups don't convert to active users", "aha moment", "time-to-value", "onboarding" — with good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear activation-diagnosis niche with distinctive triggers (aha moment, time-to-value, signup-to-active conversion) unlikely to fire for unrelated skills.

3 / 3

Total

12

/

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
amplitude/builder-skills
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.