AI Client Onboarding — Original SKILL.md

Prompt

---
name: client-onboarding
description: Turn a newly signed client into the client-facing onboarding package you actually send and run — a welcome email, the intake questions to ask before work starts, a time-boxed kickoff agenda, a first-30-days plan with owners, the risks most likely to derail it, and the gaps to settle first. Use this when the user says a client just signed, onboard this client, or write a welcome email for a new client.
---

# Client Onboarding

When this skill runs, turn the details of a newly signed client into the client-facing onboarding package the user will actually send and run.

## Process

1. Identify the client, what they bought, and what outcome they are expecting, from the material provided.
2. Write a welcome email under 120 words. It must do four things: confirm what they bought, name their point of contact, give them the one thing they need to do this week, and tell them when they will next hear from you. No filler enthusiasm.
3. Write the intake questions the user needs answered before work starts. Prioritise the questions that prevent scope and timeline problems later: who signs off, what "done" looks like, what assets exist, what dates cannot move.
4. Write a kickoff call agenda with time boxes. The kickoff must confirm and align — it is not a second discovery call.
5. Build a first 30 days plan with milestones. For each milestone, say who owes what. Only use dates and durations the user actually provided.
6. Identify the risks most likely to derail this specific engagement, based on what the user described.
7. List the gaps — anything vague or missing that must be settled before this package is client-ready.

## Rules

- Use only what the user provides. Never invent pricing, payment terms, scope, deliverables, revision limits, deadlines, team names, or contract terms.
- You cannot see the user's CRM, contract, proposal, project tool, calendar, or files. You know nothing about their business beyond what is pasted in. Never imply otherwise.
- Do not write contract or legal language. You are not drafting an agreement. If something belongs in a contract — liability, IP, termination, payment enforcement — say so and leave it out.
- When something is vague ("then we get started"), do not smooth it into professional-sounding filler. Put it in Gaps and ask the exact question. **A confident-sounding invented deliverable is how scope disputes start.**
- Write for the client to read. Plain, warm, specific. No jargon, no corporate padding.
- Focus on what the user does with the client. Do not produce an internal step-by-step process document — that is a different job.
- Do not send anything. Produce drafts for human review only.

## Output format

### Welcome Email (Draft)
Under 120 words. Ready to review and send.

### Ask Before You Start
The intake questions, most important first. Mark the ones that are scope or timeline risks.

### Kickoff Call Agenda
Time-boxed. With the goal of the call stated in one line.

### First 30 Days
Milestones with owners. Only dates the user actually gave you.

### Watch Out For
The risks most likely to derail this engagement, and when to raise each one.

### Gaps To Fill
Direct questions. What is missing before this is client-ready — and what you deliberately left out rather than invent.

If the user has not described the client or what they bought, ask for that before writing anything.