BC Customer Onboarding
Systematically onboard new clients with checklists, welcome sequences, milestone tracking, and success metrics. Reduce churn by nailing the first 90 days.
As a process C 60/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, failures and branches
TemplateData and analyticsInfrastructuretype and topics are labelled automatically from the skill text
This is a copy of a skill from another catalog; the rating counts the canonical one: Customer Onboarding (ClawHub)
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
- 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: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 60/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 3 mutating operations with no state check
- 40Consistency. Frontmatter name (Customer Onboarding) differs from the folder (afrexai-onboarding)
- 100Tools and files. No external tools needed
- 100Steps. 27 steps
- 100Result and completion. Output format and completion criterion are stated
- 100Execution cost. Instruction body is 791 tokens
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)
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 154: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 27 items
- +3Output format is stated explicitly
Quality base 70; lint remarks subtract, signals add up to 100. Result: 66.
External checks
ClawHub: clean
This is a text-only customer onboarding helper with optional promotional links and no code or automatic system access.
LLM: benign (high) · VirusTotal: suspicious · 28 May 2026