How Freelancers Can Use Claude Skills to Turn a Client Intake Form Into a Project Kickoff Brief

If Claude Skills is new to you

Claude Skills are reusable folders that Claude can load when a task matches the Skill description. A custom Skill usually includes a Skill.md file with metadata, instructions, examples, and optional supporting files. Anthropic's current help says Skills are available on Free, Pro, Max, Team, and Enterprise plans when code execution is enabled.

For this workflow, you will create one private Skill, upload it in Claude under Customize > Skills, enable it, run a quick trigger test, and then use it on your intake material. The Claude Skills tool hub is useful further reading, but this page includes enough setup detail to run the workflow.

Problem and who this is for

A client intake form usually answers part of the project question, not all of it. The real job is to turn intake answers, email clarifications, onboarding notes, and your standard project rules into one kickoff brief that aligns you and the client before work begins.

This workflow is for freelancers, consultants, and small agencies who need a usable kickoff brief before delivery starts. The deliverable is a practical alignment document, not a proposal, contract, or statement of work.

What skill you will use in this workflow

You will build a private custom Skill called kickoff-brief-from-intake. The Skill tells Claude how to turn a client intake form and scattered onboarding notes into a concise kickoff brief with goals, confirmed scope, constraints, dependencies, open questions, and first actions.

This task is repetitive enough to deserve a Skill because your kickoff brief should use the same section structure every time. The Skill can encode the brief sections, the distinction between confirmed scope and assumptions, and the guardrail against inventing approvals, deadlines, or deliverables. Before using it, prepare the intake export, follow-up notes, delivery rules, and any open questions.

Prerequisites

• Claude with Skills available and code execution enabled.
• The client intake form export, whether that is a form result, DOCX, PDF, spreadsheet excerpt, or pasted text.
• Any follow-up emails or notes that clarified scope, timing, approvals, assets, access, or constraints.
• Your own default delivery rules, such as review cycles, handoff format, client responsibilities, response-time assumptions, and approval process.
• A list of open items that still need client answers.
• A human review pass before you treat the kickoff brief as the working source of truth.

How to gather the source material

1. Export the intake results into one clean file. If they live in a form tool, spreadsheet, and email thread, collapse the important parts into one source pack first.
2. Copy key follow-up answers into a plain text note if you do not want to upload whole email threads.
3. Create one short file called delivery-rules.txt with your standard process, revision limits, handoff format, response-time assumptions, and client responsibilities.
4. Create one short file called open-items.txt with questions that still need answers. Include vague client language that should not become confirmed scope yet.
5. Save the intake form, follow-up notes, delivery rules, and open items as TXT, DOCX, or PDF in one working folder.
6. Remove credentials, unrelated budget details, unrelated client history, and any information that does not help create the kickoff brief.

Build the custom skill for this workflow

Create a folder named kickoff-brief-from-intake. Inside it, create a file named Skill.md. Paste the starter content below into that file, then adjust the sections and guardrails for your own onboarding process.

After the folder is ready, zip the kickoff-brief-from-intake folder itself so the ZIP contains the skill folder at its root. Do not zip loose files by themselves. In Claude, go to Customize > Skills, upload the ZIP file, and enable the Skill. Then run the trigger test below before using it on a live client intake.

---
name: kickoff-brief-from-intake
description: Turn a client intake form and scattered onboarding notes into a concise kickoff brief with goals, scope, constraints, dependencies, and first actions.
---

# Kickoff Brief From Intake

Use this skill when the user wants to turn a client intake form, onboarding answers, and scattered kickoff notes into a clear kickoff brief.

## Required sections
- Project goal
- Confirmed scope
- Constraints and dependencies
- Open questions
- First actions

## Guardrails
- Do not invent approvals, deadlines, or deliverables.
- Distinguish clearly between confirmed information and assumptions.
- Keep open items visible.
- Write for alignment, not legal finality.

## Examples
- Turn this intake form into a project kickoff brief.
- Use my kickoff workflow on this onboarding form and notes.
- Draft a kickoff brief and separate confirmed scope from open items.

Treat this as a starter template. Add your own preferred section names, client-facing or internal tone rules, and any non-negotiable onboarding checks, such as required access, asset handoff, review windows, or approval owners.

Optional official Anthropic skill

Anthropic's official doc-coauthoring Skill is the closest public shortcut when you want help drafting a structured document from source material. It can be useful for a one-time kickoff brief or for studying how a document-focused Skill is organized.

For repeated freelance onboarding, the private kickoff-brief-from-intake Skill is the better fit. It can hold your recurring sections, house rules, handoff expectations, and guardrails against turning vague intake answers into confirmed scope.

Skill-creator helper

Anthropic's official skill-creator Skill can help draft or refine this private kickoff Skill. Use it to improve the description, trigger examples, and guardrails, then keep your own client-specific onboarding rules in the private Skill.

Why this should be a custom skill, not a one-off prompt

A kickoff brief is repeatable operational work. A Skill keeps the same sections, scope boundaries, open-items handling, and first-action framing available each time you onboard a client. That reduces prompt rewriting and makes it harder for important constraints or open questions to disappear.

Skill trigger test

After enabling the Skill, test it with a small sample intake before using it on a real client project. These prompts should cause Claude to use the kickoff-brief-from-intake Skill:

• Turn this client intake form into a kickoff brief.
• Use my kickoff workflow and show open questions clearly.
• Draft a kickoff brief from these onboarding notes without inventing scope.
• Use the kickoff brief Skill and separate confirmed scope from assumptions.

If Claude does not appear to use the Skill, tighten the Skill description and examples with phrases like "kickoff brief," "client intake form," "confirmed scope," and "open questions."

Numbered workflow steps

1. Gather and normalize the intake material

Put the intake form, follow-up notes, delivery-rules.txt, and open-items.txt in one working folder. Normalize the source material before you ask Claude to draft anything: remove duplicates, trim unrelated conversation, and label which items are confirmed versus still unclear.

Do not ask Claude to decide scope from vague client language. If a client wrote "maybe include a landing page," put that in open items unless the client approved it elsewhere.

2. Create or enable the custom Skill for this workflow

If this is your first run, build the kickoff-brief-from-intake folder, add the Skill.md file, zip the folder, upload it in Customize > Skills, and enable it. If you already built the Skill, confirm it is enabled before you start.

The Skill should encode your brief sections: goals, confirmed scope, constraints, dependencies, open questions, and first actions. It should also encode the guardrail that Claude must not invent approvals, deadlines, or deliverables.

3. Run a quick trigger test

Use a small sample intake or sanitized excerpt first. Try:

Turn this client intake form into a kickoff brief. Use my kickoff workflow, separate confirmed scope from open questions, and do not invent deadlines or approvals.

Check that Claude uses the Skill structure and keeps open items visible. If the output turns assumptions into commitments, tighten the Skill guardrails before using it on a real client project.

4. Draft the actual kickoff brief with the Skill active

Attach or paste the full intake source pack, including follow-up notes, delivery-rules.txt, and open-items.txt. Ask Claude to use the kickoff brief Skill and draft the brief from only the provided material.

Use a prompt like:

Use the kickoff-brief-from-intake Skill on this intake form, follow-up notes, delivery rules, and open-items list. Draft a kickoff brief with goals, confirmed scope, constraints, dependencies, open questions, and first actions.

If the source pack is messy, ask Claude to first return a short intake map with confirmed facts, assumptions, and open items. Review that map before asking for the final brief.

5. Review open items, boundaries, and sensitive wording

Before you use the brief, review every section. Confirm that scope is actually approved, deadlines are actually stated, dependencies are visible, and first actions are tasks you can start without overstepping the agreement.

Pay special attention to phrases that sound contractual. The kickoff brief should support alignment, not silently become a new scope promise.

6. Save, send, or reuse the result

Save the reviewed kickoff brief in your project folder, project management tool, or client workspace. If you share it with the client, mark open questions clearly and ask for confirmation before treating them as scope. After a few projects, update the Skill with section wording that consistently works for your business.

Tool-specific instructions

Use Claude Skills for the repeatable parts of the kickoff workflow: section order, scope separation, open-items handling, dependency checks, and first-action framing. The page-specific kickoff-brief-from-intake Skill should come first because it reflects how you onboard clients and how you define a usable kickoff brief.

For broader setup context, see the Claude Skills hub. For one-off structured drafting, Anthropic's doc-coauthoring Skill may help, but keep your recurring onboarding workflow in your private Skill. For drafting or refining that private Skill, use Anthropic's skill-creator as a helper.

Quality checks

1. The brief separates confirmed scope from assumptions and open items.
2. All deadlines, dependencies, access needs, and approval owners are explicit.
3. The first actions are concrete enough to start work.
4. Nothing in the brief quietly promises work that the client only hinted at.
5. The brief reads like an alignment document, not a sales pitch or legal contract.
6. Open questions remain visible enough to send back to the client.

Common failure modes and fixes

The brief is too salesy

Fix: tell the Skill that the audience is the delivery side or kickoff alignment, not sales persuasion. Remove claims about outcomes unless the client already approved them.

Open items disappear

Fix: require a dedicated open-questions section and add a guardrail that Claude must not resolve unclear items by guessing.

Claude invents scope or deadlines

Fix: add stricter wording to the Skill: "Only list scope, dates, approvals, and deliverables when the source material states them. Put everything else in Open questions or Assumptions."

Too many source files

Fix: collapse the key information into one simple source pack before using the Skill. Keep raw email threads and old discovery notes out unless they clarify the kickoff brief.

The Skill does not trigger

Fix: update the Skill description so it includes the exact phrases you use, such as "kickoff brief," "client intake form," "confirmed scope," and "open questions." Then run the trigger test again.