Build a smooth client-onboarding process that starts projects on the right foot — clear expectations, the info you need, and a professional first impression that prevents problems later.
SkillScore50Maintained
Automatic
◆Customer Success pack
Last verified 8/31/2026
What it changes
Passed 11 of 22 test cases with the skill, and 7 of 22 without it.
Without skill32%
With skill50%
Checks it passed that the model alone missed
The kickoff agenda outlines the specific project plan
The expectations phase explicitly defines payment terms
The expectations section explicitly addresses payment terms
and 5 more in the full report
5 fixed6 passed either way10 still failing1 broke
Pass-rate lift
+18 pp
Tokens
+41%
Agent turns
0%
Response time
+8%
Model gemini-3.6-flashMeasured 8/31/2026v111 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 5
Prompt
I run a boutique PR firm for tech startups. The founders usually want me to guarantee TechCrunch coverage, so I need to manage expectations strictly right after they sign. Outline the onboarding flow, the intro email, the materials to gather, the ground rules for the engagement, and the kickoff call structure.
What was checked, without and with the skill
Checked
Without skill
With skill
The expectations section explicitly details timelines
Passed
Passed
The intake section explicitly demands necessary assets
Passed
Passed
The kickoff agenda designates time specifically for goals alignment
Missed
Passed
case-09 · gemini-3.6-flash · 8/31/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md63 linessingle file
Client-Onboarding Kit
How a project starts largely determines how it goes. Sloppy onboarding — unclear scope, missing info, mismatched expectations — is where most client problems are born. A clean, repeatable onboarding process sets expectations, gathers what you need, and signals professionalism from day one. This builds that flow so every new client starts the same, smooth way.
What This Skill Produces
A welcome & kickoff flow — the sequence from signed deal to project start (welcome, intake, kickoff, first steps)
The intake — the exact information, access, and assets you need to begin (so you're not chasing it later)
Expectation-setting — clear alignment on scope, communication norms, timeline, milestones, and payment terms
A kickoff-meeting agenda — a structured first meeting that aligns everyone and builds confidence
Reusable templates — the welcome message, intake form, and kickoff agenda to reuse every time
Problem-prevention — the boundaries (scope, comms cadence, revisions) set now that prevent disputes later
Required Inputs
Ask for these if not provided:
Your service — what you deliver and a typical project shape
Client type — size/sophistication (tunes formality)
Current process — what you do now (or nothing)
Pain points — where projects usually go wrong (scope, comms, delays, payment)
Tools — what you use for comms, files, contracts, payments
Framework: Set The Frame Before The Work
Welcome and reassure. A prompt, warm welcome after signing sets the tone and confirms they made the right choice.
Gather everything up front. A structured intake for the info, access, assets, and decisions you need — so the work isn't stalled chasing details.
Align expectations explicitly. Scope (and what's out of scope), communication channels and cadence, timeline/milestones, revisions, and payment terms — stated now, not assumed.
Run a real kickoff. A structured kickoff meeting confirms goals, roles, and the plan, and gives the client confidence.
Make it repeatable. Templatize the welcome, intake, and agenda so every client gets the same professional start with less effort each time.
Prevent the usual problems. The clarity set here (especially scope and comms) is what heads off scope creep and friction later.
Output Format
Client onboarding: [service] · client type [x]
Flow: signed → welcome → intake → kickoff → first steps.
Welcome message: [warm, next-steps, what to expect].
Intake (gather up front): [info · access · assets · decisions needed].
Set expectations: scope (+ out of scope) · comms channel & cadence · timeline/milestones · revisions · payment terms.
Kickoff agenda: [goals · roles · plan · Q&A · next steps].
Write a structured clinical case summary or case presentation. Use when asked to write a clinical case summary, case presentation, patient case report, or clinical handover. Produces a structured summary using SBAR or SOAP format. For educational and documentation purposes only — not a substitute for clinical judgement.