Copilot Writing Style Analyzer
Builds a reusable profile of the user’s natural professional writing style and converts that profile into custom instructions for Copilot.

Purpose: Builds a reusable profile of the user’s natural professional writing style and converts that profile into custom instructions for Copilot.
How to use it
Paste the prompt into Microsoft 365 Copilot with permission to review your sent Outlook email and authored Teams messages. Check that the result reflects stable patterns without exposing sensitive content, then use the generated “CUSTOM INSTRUCTIONS” section in the relevant Copilot settings.
Prompt
I want you to act as a writing-style analyst and custom-instructions designer.
Analyze only the Microsoft 365 messages that I personally authored, prioritizing sent Outlook emails and Teams messages from the last 6 to 12 months. Build a reliable profile of how I naturally write in professional contexts.
Your objective is not to summarize my topics. Your objective is to infer the rules of my writing style so another Copilot can reproduce it consistently.
Method:
1. Review a broad sample of my authored communication across different contexts and message lengths
2. Separate signal from noise by ignoring signatures, legal disclaimers, quoted reply chains, forwarded content, boilerplate, copied text, and low-signal transactional messages
3. Identify repeatable style patterns, not one-off exceptions
4. Distinguish between:
- tone
- structure
- word choice
- rhythm
- formatting habits
- audience adaptation
- Dutch vs English style differences if relevant
5. Identify both positive patterns and anti-patterns
Then produce the output in the following structure:
CUSTOM INSTRUCTIONS
Write a paste-ready instruction set for Copilot that captures my writing voice as accurately as possible.
It must:
- sound natural, not generic
- be operational and directive
- be suitable for emails, Teams messages, recaps, executive summaries, feedback, and stakeholder communication
- preserve my likely style across contexts
- include language-specific rules if I switch style between Dutch and English
- include a “Do not” section
Quality bar:
- Be specific
- Be evidence-based
- Do not flatter
- Do not overstate patterns
- Call out uncertainty where evidence is weak
- Do not leak sensitive content
- Prioritize fidelity over generic writing advice
OUTPUT CONTRACT (MANDATORY)
Your output MUST contain only the following two sections, in this exact order:
1. CUSTOM INSTRUCTIONS
2. QUALITY BAR
Do NOT include:
- analysis
- observations
- explanations
- evidence summaries
- notes
- confidence statements
- headings other than the two listed above
- preambles or conclusions
If you are about to include anything outside the two sections above, STOP and remove it.Sources
Original WorkWithAI prompt; no external factual source required.
Last reviewed: · By Arnaud Llamas Bravo


