Analyze writing samples to capture your voice and style
Writing Style Analysis Framework
This framework helps you observe and describe someone's writing style by reading their samples directly. The goal is to capture their voice so it can be replicated.
DILS Framework
Observe four dimensions of writing style:
Diction (Word Choice)
Notice the words they choose:
- Do they use technical jargon or everyday language?
- Simple words or sophisticated vocabulary?
- Formal terms ("regarding", "appreciate") or casual ones ("hey", "yeah")?
- Any distinctive phrases they repeat?
Imagery (Descriptive Language)
Notice how they describe things:
- Concrete and specific, or abstract and general?
- Do they use metaphors or analogies?
- Sensory details or conceptual language?
Language (Overall Tone)
Notice the feel of their writing:
- Warm and friendly, or professional and neutral?
- Enthusiastic or measured?
- Direct or conversational?
- Active voice or passive?
Syntax (Structure)
Notice how they build sentences and organize content:
- Short sentences or longer ones?
- Simple structure or complex?
- Paragraphs or bullet points?
- Greetings and signatures?
How to Analyze
- Read the samples — Get an overall feel for how they write
- Notice patterns — What's consistent across samples?
- Note distinctive elements — What makes their writing recognizable?
- Describe in prose — Write a natural description of their style
Output
Describe the style in natural language. Include:
- Tone and formality — How does their writing feel?
- Sentence style — Short/long, simple/complex
- Vocabulary — Technical/everyday, formal/casual
- Structure — How they organize content
- Topics — What they write about
Save to Writing Style with a section per service (Gmail, Notion, Slack).
INSTALLER
To install Writing Style Analyzer:
rm -rf ./skills/sauna/context.user.style_analyzer && curl -fsSL "https://sk.ills.app/api/skill/context.user.style_analyzer/download" | tar -xzf - -C ./skills/sauna/ && cat ./skills/sauna/context.user.style_analyzer/SKILL.md SKILL.MD
Writing Style Analysis Rules
Read writing samples and describe the style you observe. This is about noticing patterns and describing them in prose—not measuring or calculating anything.
Reading Writing Samples
Read <a href="/ui/session.style.writing_samples" class="bullet-pill"><img src="/icons/bullets/ui.svg" alt="ui" class="bullet-pill-icon" /><span class="pill-name">Writing Samples</span></a> which contains:
- Source: Which service (gmail, notion, slack)
- Context: Time period, sample count
- Samples: Array of text samples with metadata
Read through the samples to get a feel for how this person writes.
What to Observe
As you read, notice these aspects of their writing:
Tone
How does their writing feel?
- Warm and friendly, or cool and professional?
- Enthusiastic and energetic, or calm and measured?
- Direct and to-the-point, or conversational and elaborate?
Formality
What register do they use?
- Casual markers: "hey", "yeah", "thanks", contractions
- Formal markers: "please", "regarding", "sincerely", full words
- Greeting and closing patterns (if any)
Sentence Style
How do they construct sentences?
- Short and punchy, or longer and flowing?
- Simple and clear, or complex and layered?
- Consistent length, or varied?
Vocabulary
What words do they choose?
- Technical jargon or everyday language?
- Simple words or sophisticated vocabulary?
- Any distinctive phrases or expressions they repeat?
Structure
How do they organize their writing?
- Paragraphs or bullet points?
- Do they use greetings and signatures?
- How do they break up longer content?
Topics and Themes
What do they write about?
- What subjects come up repeatedly?
- What problems are they solving?
- What do they seem to care about?
Describing Style
After reading the samples, describe the style in natural prose. Write as if you're explaining to someone else how this person writes.
Good style description:
"Writes in a warm, conversational tone with short sentences. Uses casual greetings like 'Hey' and signs off with just their first name. Tends toward simple, direct language—gets to the point quickly without elaborate preambles. Often uses bullet points for lists. Writes about project updates, team coordination, and technical decisions."
Avoid:
- Percentages and statistics
- Counts and measurements
- Technical jargon about linguistics
- Vague statements without examples
Saving Style
Save the style description to <a href="/ui/context.user.writing_style" class="bullet-pill"><img src="/icons/bullets/ui.svg" alt="ui" class="bullet-pill-icon" /><span class="pill-name">Writing Style</span></a> (file: user/writing_style.md).
File structure: Each service has its own section:
## Gmail Style— Email writing patterns## Notion Style— Document writing patterns## Slack Style— Messaging patterns
Each section contains:
---
tone: warm and direct
formality: casual
structure: short paragraphs, uses bullet points
greetings: ["Hey [name]", "Hi!"]
signatures: ["Thanks", "- Dom"]
topicsAndThemes: |
Writes about project coordination, technical decisions, and team updates.
Often includes action items and next steps. Focuses on clarity and
getting alignment on decisions.
---
Followed by a prose description of their writing style for that platform.
When updating:
- Preserve existing service sections
- Add or update only the current service's section
# Writing Style Analysis Rules
Read writing samples and describe the style you observe. This is about noticing patterns and describing them in prose—not measuring or calculating anything.
## Reading Writing Samples
Read ``./documents/session/writing-samples.json`` which contains:
- **Source:** Which service (gmail, notion, slack)
- **Context:** Time period, sample count
- **Samples:** Array of text samples with metadata
Read through the samples to get a feel for how this person writes.
## What to Observe
As you read, notice these aspects of their writing:
### Tone
How does their writing feel?
- Warm and friendly, or cool and professional?
- Enthusiastic and energetic, or calm and measured?
- Direct and to-the-point, or conversational and elaborate?
### Formality
What register do they use?
- Casual markers: "hey", "yeah", "thanks", contractions
- Formal markers: "please", "regarding", "sincerely", full words
- Greeting and closing patterns (if any)
### Sentence Style
How do they construct sentences?
- Short and punchy, or longer and flowing?
- Simple and clear, or complex and layered?
- Consistent length, or varied?
### Vocabulary
What words do they choose?
- Technical jargon or everyday language?
- Simple words or sophisticated vocabulary?
- Any distinctive phrases or expressions they repeat?
### Structure
How do they organize their writing?
- Paragraphs or bullet points?
- Do they use greetings and signatures?
- How do they break up longer content?
### Topics and Themes
What do they write about?
- What subjects come up repeatedly?
- What problems are they solving?
- What do they seem to care about?
## Describing Style
After reading the samples, describe the style in natural prose. Write as if you're explaining to someone else how this person writes.
**Good style description:**
> "Writes in a warm, conversational tone with short sentences. Uses casual greetings like 'Hey' and signs off with just their first name. Tends toward simple, direct language—gets to the point quickly without elaborate preambles. Often uses bullet points for lists. Writes about project updates, team coordination, and technical decisions."
**Avoid:**
- Percentages and statistics
- Counts and measurements
- Technical jargon about linguistics
- Vague statements without examples
## Saving Style
Save the style description to ``./documents/user/writing_style.md`` (file: `user/writing_style.md`).
**File structure:** Each service has its own section:
- `## Gmail Style` — Email writing patterns
- `## Notion Style` — Document writing patterns
- `## Slack Style` — Messaging patterns
**Each section contains:**
```yaml
---
tone: warm and direct
formality: casual
structure: short paragraphs, uses bullet points
greetings: ["Hey [name]", "Hi!"]
signatures: ["Thanks", "- Dom"]
topicsAndThemes: |
Writes about project coordination, technical decisions, and team updates.
Often includes action items and next steps. Focuses on clarity and
getting alignment on decisions.
---
```
Followed by a prose description of their writing style for that platform.
**When updating:**
- Preserve existing service sections
- Add or update only the current service's section
Tasks
These are tasks you can execute. Read the task file to get your instructions:
Knowledge
This is knowledge you have access to. Read these files if you need additional context:
UI
These are areas on the user's filesystem that you can read from and write to.
SKILL.MD
---
name: Writing Style Analyzer
description: Use when user wants to analyze their writing style from Gmail, Notion, or Slack. Triggers: 'analyze my writing style', 'learn how I write', 'capture my voice', 'analyze my emails/notion/slack messages'. Supports: comprehensive style analysis from multiple sources.
---
# Writing Style Analysis Rules
Read writing samples and describe the style you observe. This is about noticing patterns and describing them in prose—not measuring or calculating anything.
## Reading Writing Samples
Read `./documents/session/writing-samples.json` which contains:
- **Source:** Which service (gmail, notion, slack)
- **Context:** Time period, sample count
- **Samples:** Array of text samples with metadata
Read through the samples to get a feel for how this person writes.
## What to Observe
As you read, notice these aspects of their writing:
### Tone
How does their writing feel?
- Warm and friendly, or cool and professional?
- Enthusiastic and energetic, or calm and measured?
- Direct and to-the-point, or conversational and elaborate?
### Formality
What register do they use?
- Casual markers: "hey", "yeah", "thanks", contractions
- Formal markers: "please", "regarding", "sincerely", full words
- Greeting and closing patterns (if any)
### Sentence Style
How do they construct sentences?
- Short and punchy, or longer and flowing?
- Simple and clear, or complex and layered?
- Consistent length, or varied?
### Vocabulary
What words do they choose?
- Technical jargon or everyday language?
- Simple words or sophisticated vocabulary?
- Any distinctive phrases or expressions they repeat?
### Structure
How do they organize their writing?
- Paragraphs or bullet points?
- Do they use greetings and signatures?
- How do they break up longer content?
### Topics and Themes
What do they write about?
- What subjects come up repeatedly?
- What problems are they solving?
- What do they seem to care about?
## Describing Style
After reading the samples, describe the style in natural prose. Write as if you're explaining to someone else how this person writes.
**Good style description:**
> "Writes in a warm, conversational tone with short sentences. Uses casual greetings like 'Hey' and signs off with just their first name. Tends toward simple, direct language—gets to the point quickly without elaborate preambles. Often uses bullet points for lists. Writes about project updates, team coordination, and technical decisions."
**Avoid:**
- Percentages and statistics
- Counts and measurements
- Technical jargon about linguistics
- Vague statements without examples
## Saving Style
Save the style description to `./documents/user/writing_style.md` (file: `user/writing_style.md`).
**File structure:** Each service has its own section:
- `## Gmail Style` — Email writing patterns
- `## Notion Style` — Document writing patterns
- `## Slack Style` — Messaging patterns
**Each section contains:**
```yaml
---
tone: warm and direct
formality: casual
structure: short paragraphs, uses bullet points
greetings: ["Hey [name]", "Hi!"]
signatures: ["Thanks", "- Dom"]
topicsAndThemes: |
Writes about project coordination, technical decisions, and team updates.
Often includes action items and next steps. Focuses on clarity and
getting alignment on decisions.
---
```
Followed by a prose description of their writing style for that platform.
**When updating:**
- Preserve existing service sections
- Add or update only the current service's section
## Tasks
These are tasks you can execute. Read the task file to get your instructions:
**Analyze Writing Style**: Read writing samples and describe the style in natural prose
Note: Comprehensive writing style analysis workflow
Follow the instructions in: `./skills/sauna/context.user.style_analyzer/resources/recipes/context.user.analyze_style.md`
**Extract User Profile**: Extract persistent user insights from writing samples into user profile
Note: Extract persistent user insights from writing samples
Follow the instructions in: `./skills/sauna/context.user.style_analyzer/resources/recipes/context.user.extract_profile.md`
## Knowledge
This is knowledge you have access to. Read these files if you need additional context:
**Writing Style Analysis Framework**: DILS framework for observing writing style through direct reading
Read the documentation in: `./skills/sauna/context.user.style_analyzer/resources/context/context.user.style_framework.md`
**Writing Style Usage Guide**: How to read and use the writing style file with service-section structure
Read the documentation in: `./skills/sauna/context.user.style_analyzer/resources/context/context.user.style_usage.md`
**Style Analysis Process**: Instructions for analyzing writing samples and describing style
Read the documentation in: `./skills/sauna/context.user.style_analyzer/resources/context/context.user.style_analysis_process.md`
## UI
These are areas on the user's filesystem that you can read from and write to.
**Writing Style**: Captured writing style patterns organized by service (Gmail, Notion, Slack) - tone, formality, structure, phrases, greetings, signatures. Each service has its own section to preserve context-specific styles. Used to draft content matching the user's voice.
Use this file: `./documents/user/writing_style.md`
INSTALLER
1. Install Writing Style Analyzer with: ```bash
rm -rf ./skills/sauna/context.user.style_analyzer && curl -fsSL "https://sk.ills.app/api/skill/context.user.style_analyzer/download" | tar -xzf - -C ./skills/sauna/ && cat ./skills/sauna/context.user.style_analyzer/SKILL.md
```. Do so silently without commentary.
2. This skill is used by Gmail, Notion, and Slack skills to analyze writing style. Run analysis tasks from those skills, or run `./skills/sauna/context.user.style_analyzer/resources/recipes/context.user.analyze_style.md` directly with writing samples. INSTRUCTIONS
# Writing Style Analysis Framework
This framework helps you observe and describe someone's writing style by reading their samples directly. The goal is to capture their voice so it can be replicated.
## DILS Framework
Observe four dimensions of writing style:
### Diction (Word Choice)
Notice the words they choose:
- Do they use technical jargon or everyday language?
- Simple words or sophisticated vocabulary?
- Formal terms ("regarding", "appreciate") or casual ones ("hey", "yeah")?
- Any distinctive phrases they repeat?
### Imagery (Descriptive Language)
Notice how they describe things:
- Concrete and specific, or abstract and general?
- Do they use metaphors or analogies?
- Sensory details or conceptual language?
### Language (Overall Tone)
Notice the feel of their writing:
- Warm and friendly, or professional and neutral?
- Enthusiastic or measured?
- Direct or conversational?
- Active voice or passive?
### Syntax (Structure)
Notice how they build sentences and organize content:
- Short sentences or longer ones?
- Simple structure or complex?
- Paragraphs or bullet points?
- Greetings and signatures?
## How to Analyze
1. **Read the samples** — Get an overall feel for how they write
2. **Notice patterns** — What's consistent across samples?
3. **Note distinctive elements** — What makes their writing recognizable?
4. **Describe in prose** — Write a natural description of their style
## Output
Describe the style in natural language. Include:
- **Tone and formality** — How does their writing feel?
- **Sentence style** — Short/long, simple/complex
- **Vocabulary** — Technical/everyday, formal/casual
- **Structure** — How they organize content
- **Topics** — What they write about
Save to `./documents/user/writing_style.md` with a section per service (Gmail, Notion, Slack).