An agent skill for new client kickoff is a reusable set of instructions that turns a signed contract into a complete kickoff pack — client brief, task list, timeline, and first deliverable draft — with no retyping. Build it once as a SKILL.md file, and one prompt runs the whole handoff from “signed” to “work started.”
The gap between a signed contract and real work is where small businesses lose time and goodwill: the welcome email waits days, the brief lives in someone’s head, and tasks get created late, twice, or not at all. Nobody is lazy — the handoff is manual, and manual handoffs break under pressure. A kickoff skill fixes the handoff, not the people.
What the kickoff skill actually does
One skill, six jobs in order. It reads the signed contract and pulls out what matters — client name, scope, price, dates, deliverables, contact. It builds a one-page brief in your format, creates the task list with owners and due dates, drafts the welcome email in your brand voice, sets the timeline from the contract dates, and starts the first deliverable, so work begins before the kickoff call ends. No code needed: a basic skill is a folder with a Markdown file, plus templates you already use.
Prerequisites
- A claude.ai paid plan (Pro, Max, Team, or Enterprise) with code execution enabled, or Claude Code.
- Your signed contract (PDF or Word) plus a CRM record or spreadsheet with the client’s details.
- One welcome email and one client brief you have used before.
- About one hour to build, 15 minutes per kickoff.
Step 1: Map the kickoff on paper
Write down the six jobs in your own words, in order, with the decisions at each step — for example: “Copy scope, price, and dates from the contract, never from memory. Create tasks only for signed scope; extras go on a separate list for client approval. Send the welcome email within one business day.” This page is the skill — SKILL.md is just a typed-up version of it. If you cannot describe a step in one sentence, it is too vague, and Claude will guess.
Step 2: Create the folder and the frontmatter
Every skill is a folder containing a SKILL.md file — create one named new-client-kickoff. It starts with YAML frontmatter, two fields required. Per Anthropic’s documentation, the name is at most 64 characters — lowercase, numbers, and hyphens only — and the description is at most 1,024 characters, saying what the skill does and when to use it.
---
name: new-client-kickoff
description: Runs our new-client kickoff: reads the signed contract, builds the brief, creates tasks, drafts the welcome email, starts the first deliverable. Use when a client signs or a project starts.
---
# New-Client Kickoff
## Workflow
1. Read the signed contract. Extract client name, scope, price, start date, deliverables, and contact. Ask if any are missing — never guess.
2. Build the one-page client brief from assets/brief-template.md.
3. Create the kickoff task list: owner and due date per task.
4. Draft the welcome email from templates/welcome-email.md. Draft only; never send.
5. Set the project timeline from the contract dates.
6. Start the first deliverable as a draft, following the scope exactly.
## Rules
- Never invent a scope item, a price, or a date.
- Never send anything. Draft only; the user reviews and sends.
- Work outside the signed scope goes on a separate "needs approval" list.
The description is the trigger: Claude reads only the name and description at startup — about 100 tokens per skill — and loads the rest only when your request matches. Use the exact phrases you will type, such as “kick off the new client.”
Step 3: Write the workflow in plain language
Below the frontmatter, write the instructions as if onboarding a careful new hire — the six jobs in order, plus your rules. Add the edge cases you already know: no start date, two contacts, a service you no longer sell. Keep the file short — under 5,000 tokens, per Anthropic’s documentation — and keep templates in separate files, so the instructions stay readable.
Step 4: Add your templates and contract as reference files
Keep data out of the instructions: save your welcome email and brief templates in the same folder, with the signed contract alongside them. Claude loads reference files only when needed — Anthropic calls this progressive disclosure — so a long contract costs nothing until a kickoff runs. Date every task list: a task without a due date is a wish, and a kickoff without dates drifts within a week.
Step 5: Install it where you work
Install the skill separately on each surface — custom skills do not sync. In Claude Code, copy the folder into ~/.claude/skills/ (personal) or the project’s .claude/skills/ folder (team). On claude.ai, zip the folder and upload it under Customize > Skills, with code execution enabled. Our meeting-prep skill uses the same install pattern, and our event-planning skill shows the same layout on a different workflow.
Step 6: Test it on a past client
Do not debut it on a real signing. Re-run a past kickoff and compare the brief, tasks, and welcome email with what you actually sent. Check: does it fire on kickoff questions, does the brief carry the right scope and price, does it flag gaps instead of guessing? If it fires on the wrong tasks, the description is too broad; if it never fires, it is too narrow. Fix the description first.
Tips and common mistakes
- Keep a human in the send loop: the skill drafts, you review and send. That checkpoint stops a wrong price, a misspelled name, or a scope item you never agreed to.
- Only install skills from sources you trust. Anthropic warns a skill is like installing software: its instructions can do things its description never mentions.
- Review the skill every quarter: prices and templates change, and a skill quoting last year’s process is worse than no skill. If you hire, it is also how you onboard new employees faster — the process is written down.
FAQ
Do I need to code to build a kickoff skill?
No. A basic skill is a folder with a Markdown file, your contract, and your templates.
Will the skill send the welcome email by itself?
No. It drafts the email, brief, and task list for you to review and send — the send step stays with a human on purpose.
What if the contract is missing a date or a deliverable?
The skill flags the gap and asks you — never guesses. A missing start date is a question for the client, not a detail for the AI to invent.
Does this work for service businesses with different scopes?
Yes — the skill reads what was signed, so a design project, a retainer, and a one-off job all run through the same six jobs. Only the templates change.
Conclusion
A signed contract should start work, not start admin. A kickoff skill captures the repeatable part and leaves the judgment to you. Build it once, test it on a past client, and the next signature starts with a prompt, not a scramble.



