How Freelancers Can Use Claude Skills to Turn a Client Questionnaire Into a Messaging 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, test it with a small source package, and then use it to draft the messaging brief. The Claude Skills tool hub is useful further reading, but the setup steps you need are included here.

Problem and who this is for

A client questionnaire usually gives you fragments: how the client describes the business, what they think makes them different, what customers struggle with, and what they want buyers to believe. A messaging brief turns those fragments into a source-grounded working document you can write from.

This workflow is for copywriters, strategists, consultants, and freelancers who need to turn existing client inputs into a messaging brief. It is not a full brand strategy process, positioning overhaul, or final copywriting pass.

What skill you will use in this workflow

You will build a private custom Skill called messaging-brief-from-questionnaire. The Skill tells Claude how to turn a client questionnaire and existing website or brand copy into a practical messaging brief with audience, pain points, proof points, tone, claims to avoid, and open questions.

This task is repetitive enough to deserve a Skill because messaging briefs need the same discipline across clients: source hierarchy, proof checks, careful claim language, and a clear separation between client-provided facts and strategist interpretation. Before using it, prepare the questionnaire, a small sample of current site or brand copy, any proof notes, and the brief purpose.

Prerequisites

• Claude with Skills available and code execution enabled.
• The filled-in client questionnaire.
• Existing website copy, offer descriptions, brand copy, or one recent proposal.
• Any proof notes, testimonials, product facts, compliance wording, or claim restrictions that must stay exact.
• A short note on what the brief is for. Example: homepage rewrite, service page, launch page, or sales deck.
• A human review pass for regulated claims, positioning language, and anything stronger than the source supports.

How to gather the source material

1. Export the questionnaire results into a clean text document, DOCX, or PDF.
2. Copy a small sample of the client's current website or brand copy into one working document. Use enough to establish tone and current claims without uploading every page.
3. Create one file called proof-notes.txt for testimonials, product facts, compliance wording, customer evidence, or claims that must be verified before publication.
4. Create one file called brief-purpose.txt with the intended deliverable and audience.
5. Label source priority before you run the workflow. For example: proof notes override questionnaire guesses, current website copy shows existing language, questionnaire answers show client intent.
6. Remove duplicated answers, filler, credentials, or unrelated client history before you upload the source package.

Build the custom skill for this workflow

Create a folder named messaging-brief-from-questionnaire. Inside it, create a file named Skill.md. Paste the starter content below into that file, then adjust it for your messaging process, client type, and claim-review needs.

After the folder is ready, zip the messaging-brief-from-questionnaire 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 real client project.

---
name: messaging-brief-from-questionnaire
description: Turn a client questionnaire and existing website or brand copy into a messaging brief with audience, pain points, proof points, tone, and claims to avoid.
---

# Messaging Brief From Questionnaire

Use this skill when the user wants to turn a client questionnaire and existing brand materials into a practical messaging brief.

## Required sections
- Audience
- Core problems or pain points
- Proof points
- Tone and voice
- Claims to avoid or verify
- Open questions

## Guardrails
- Do not invent positioning claims.
- Do not upgrade a weak claim into a strong promise.
- Prefer client-provided language when it is clear and accurate.
- Flag anything that needs verification before publication.

## Examples
- Turn this client questionnaire into a messaging brief.
- Use my messaging workflow on this questionnaire and website copy.
- Draft a messaging brief and flag claims that need verification.

Treat this as a starter template. Add your own source hierarchy, preferred section names, regulated-claim rules, tone expectations, or client niche language before using it on live work.

Skill-creator helper

Do not force a same-purpose public Skill into this workflow. Anthropic's official skill-creator Skill can help draft or refine the private messaging-brief-from-questionnaire Skill, especially the description, trigger examples, source hierarchy, and guardrails.

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

A messaging brief is repetitive, but the risk is subtle. A one-off prompt can forget your source hierarchy or turn soft client language into strong claims. A Skill keeps the same audience, proof, tone, claims-to-avoid, and verification sections available every time, which lowers prompt rewrite friction and keeps the brief tied to evidence.

Skill trigger test

After enabling the Skill, test it with one questionnaire and a small sample of site copy before the first real run. These prompts should cause Claude to use the messaging-brief-from-questionnaire Skill:

• Turn this questionnaire and website copy into a messaging brief.
• Use my messaging workflow and keep weak claims visible.
• Draft a messaging brief from these client answers without inventing positioning.
• Use the messaging brief Skill and flag claims that need verification.

If Claude does not appear to use the Skill, tighten the Skill description and examples with phrases like "messaging brief," "client questionnaire," "website copy," "proof points," and "claims to avoid."

Numbered workflow steps

1. Gather and clean the source material

Put the questionnaire, site-copy sample, proof-notes.txt, and brief-purpose.txt in one working folder. Remove duplicated answers and label the source hierarchy before you ask Claude to draft anything.

Keep the job narrow. You are not asking Claude to invent a full brand strategy. You are asking it to organize existing inputs into a messaging brief you can review and write from.

2. Create or enable the custom Skill for this workflow

If this is your first run, build the messaging-brief-from-questionnaire 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 the sections that matter for this job: audience, problems, proof points, claims to avoid, tone, open questions, and source hierarchy. It should also encode the guardrail that weak claims stay weak until the source supports stronger language.

3. Run a quick trigger test

Use one questionnaire and a small site-copy sample first. Try:

Turn this questionnaire and website copy into a messaging brief. Use my messaging workflow, keep weak claims visible, and do not invent positioning.

Check that Claude uses the Skill structure, flags claims that need proof, and avoids polished final copy. If it starts writing homepage sections instead of a brief, tighten the Skill instructions before the first real run.

4. Run the actual workflow with the Skill active

Attach or paste the full source package: questionnaire, website or brand copy sample, proof-notes.txt, and brief-purpose.txt. Ask Claude to use the messaging brief Skill and build the brief from the source hierarchy.

Use a prompt like:

Use the messaging-brief-from-questionnaire Skill on this questionnaire, website copy, proof notes, and brief-purpose note. Draft a practical messaging brief with audience, pain points, proof points, tone, claims to avoid, and open questions.

If the source material is messy, ask Claude to first produce a short source map: exact client language, supported facts, weak claims, proof notes, and open questions. Review that map before drafting the final brief.

5. Do a human review for claim strength and positioning

Review the brief before using it in client work. Check regulated claims, health or financial language, product promises, results claims, and anything that sounds stronger than the source evidence supports.

Also check positioning language. If Claude turns "we care about service" into "industry-leading service," soften it or move it to claims to verify.

6. Save, send, or reuse the result

Save the reviewed messaging brief in your project folder, copy deck, or client workspace. If you share it with the client, keep proof-needed items visible and ask for verification before those claims move into final copy. After several projects, update the Skill with section wording and claim rules that consistently improve the brief.

Tool-specific instructions

Use Claude Skills for the repeatable parts of the messaging workflow: source hierarchy, audience extraction, pain-point grouping, proof handling, tone notes, and claims-to-avoid rules. The page-specific messaging-brief-from-questionnaire Skill should come first because this workflow depends on your evidence standards and the kind of messaging brief you deliver.

For broader setup context, see the Claude Skills hub. For help drafting or improving the private Skill, use Anthropic's official skill-creator as a helper, not as a replacement for your messaging brief Skill.

Quality checks

1. The brief contains only claims the source material supports.
2. Proof-needed items are clearly labeled.
3. Weak claims stay weak until the client provides evidence.
4. The tone section reflects existing client language without copying vague filler.
5. The output reads like a working messaging brief, not final homepage copy.
6. Regulated or sensitive claims are marked for human review before publication.

Common failure modes and fixes

The brief overclaims

Fix: add stricter proof rules to the Skill and require claims to be labeled as supported, weak, or needs verification.

The output sounds like finished copy

Fix: add a guardrail that Claude should write a working brief, not final web copy, headlines, or campaign language.

Client language is vague

Fix: ask Claude to separate exact client language from strategist interpretation before drafting the brief.

The source hierarchy is unclear

Fix: add source priority to the prompt and the Skill. For example: proof notes outrank questionnaire opinions, and exact product facts outrank older website copy.

The Skill does not trigger

Fix: update the Skill description so it includes the exact phrases you use, such as "messaging brief," "client questionnaire," "website copy," "proof points," and "claims to avoid." Then run the trigger test again.