BC nex-onboarding
Comprehensive client onboarding workflow management system for web agencies, design studios, and service providers. Manage complete client setup processes from contract signing through go-live with structured checklists (opstarten), task progress tracking, and bottleneck detection. Create onboarding workflows covering administrative tasks (contract, payment processing, afronding), technical setup (domain configuration, DNS transfers, SSL certificates, email setup), design and branding (logo requests, brand guidelines), content gathering, and communication milestones (welcome emails, kickoff calls, training, feedback collection). Track progress with completion percentages, visual checklists, and status indicators. Mark steps complete, skip steps when clients handle them independently, or block steps when waiting on client input. Identify most commonly blocked steps to improve workflow efficiency. Assign onboarding steps to team members, export progress data for reporting, and view onboarding statistics across multiple active clients. Support different engagement tiers (starter, standard, premium, enterprise) with customizable templates. Perfect for Belgian agency operators who need systematic client onboarding to reduce errors, improve client satisfaction, and scale client acquisition.
As a process C 63/100 · Has gaps — weak spots: result and completion, running it twice, progress reporting
How to improve
- Shorten the description to 1024 characters.
- 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: 10. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- error
description-longdescription is 1305 chars, limit 1024
Process rating: all ten parameters 63/100
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 3 mutating operations with no state check
- 55Failures and branches. 1 branches
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 49 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1577 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)
- +3Description length 1305: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +4Structure: 33 headings
- +3Step-by-step instructions: 49 items
- +4Has examples (20 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 57.