Verified Agent Skill record

Setup Writing Style

A writing skill that learns the user's writing voice from their own sent messages and documents and saves a personal voice profile (the my-writing-style skill) so future drafts sound like them rather than generic AI. It runs a consent-first seven-step flow: consent, sample gathering into temporary files, stylometric analysis, profile creation, and optional review/refinement steps.

Tasks

Build a personal voice profile from the user's own sent messages and documents, saved as a my-writing-style skill
Gather samples per surface (email, Slack, DM, doc) with audience-prefixed filenames, strip quoted material, and transcribe complete messages or ~1,500-word doc slices

Inputs

User-authored, sent messages and documents (e.g., Gmail sent mail, Slack messages the user posted, their own Drive docs, or pasted samples of 5-15 pieces)
Explicit user consent naming exactly which sources will be read

Outputs

A saved my-writing-style profile skill
Temporary sample files organized under $WORK/samples/<surface>/ with files named <audience>__<slug>__<YYYY-MM-DD>__<NNN>.txt, deleted automatically when the flow ends

Limitations and checks

Not for drafting text the user will send as anyone other than themselves, and not for Claude's own replies
Profile must never contain PII or secrets; if the corpus is too thin to support a trait, the skill says so rather than manufacturing a voice
Corpus capped at roughly 300K characters and up to ~100 samples; sample text is treated as data, never instructions
Confirm consent was given before any search or read, and that only user-authored sent writing is gathered with quoted replies, forwards, and signatures stripped
Verify no PII or secrets (names, email addresses, phone numbers, account numbers, health/financial details, deal terms, project names) appear in the saved profile
Verify sample filenames use the fixed audience prefixes and that slugs are derived in code (lowercase, [a-z0-9-], truncated) rather than raw channel or person names, to avoid command-injection and path-traversal risk
Confirm the working directory for samples is outside any git repository and its path was disclosed to the user