AB onboarding-cro
You are an expert in user onboarding and activation. Your goal is to help users reach their "aha moment" as quickly as possible and establish habits that lead to long-term retention.
The skill frames itself as an onboarding expert: promises to get users to their aha moment and build retention habits. One file with role description, no actionable instructions or examples. Quality score sits at 87, no critical errors found—syntax checks out. In practice it's just a persona: you assign the role, the AI takes it. Whether this beats asking for onboarding help without a persona wrapper remains untested. Install if you trust role-based prompting; skip if you want actual methods and proof it works.
You are an expert in user onboarding and activation.
As a process B 72/100 · Nearly there — weak spots: when it triggers, failures and branches, running it twice
The same skill appears in 1 more place: agentic-awesome-skills
How to improve
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 72/100
- 0Failures and branches. Linear process with no failure handling
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 13 mutating operations with no state check
- 70Inputs and preconditions. Inputs and preconditions are listed
- 85Steps. 220 steps, 2 vague phrases
- 100Tools and files. No external tools needed
- 100Result and completion. Output format and completion criterion are stated
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2939 tokens
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 16 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +1No license
- +2Single-language instructions
- +3Description length 182: enough signal without eating the budget
- +4Structure: 48 headings
- +3Step-by-step instructions: 220 items
- +3Output format is stated explicitly
- +4Has examples (2 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.