Build newsletter writing instructions inside a Cowork project. Runs after voice-builder. Produces newsletter-voice.md, a single file Claude references when drafting newsletters in the user's voice. Works with or without existing newsletter samples: if the user has past issues, the skill analyses the

Newsletter Voice Prerequisites check The moment this skill is triggered, check the project root for voice.md and about me.md. If either file is missing, tell the user: Newsletter voice sits on top of your general voice profile. Run voice builder first (upload the skill or say "build my voice"), then come back here once about me.md and voice.md are in the project. Then stop. Do not continue until both files exist. If both files exist, read them fully, then go straight to Step 1. Step 1. Check for samples Ask the user in chat: Do you have 2 to 3 past newsletter issues I can learn from? Yes: paste them here (one per message or all at once) No: type "archetype" and I will build from a template tuned to your voice Wait for response. If the user pastes 2 or more newsletters, go to Step 2a. If the user types "archetype", go to Step 2b. If the user pastes 1 newsletter, ask for at least one more. If they only have one, offer: "One sample is not enough for pattern detection. Want me to switch to archetype mode and use your one newsletter as a reference point?" Step 2a. Sample based analysis Read every newsletter fully. Look for patterns across issues, not one off quirks. Extract: Opening formula What the first 3 sentences do (specific result, cultural observation, claim, scene, question) Length of the opening section before the first structural break Credibility move (how the author establishes authority early) Value promise (what the reader is told they will get) Section structure Problem or contrast setup Named framework or free prose Numbered steps, methods, or continuous argument Examples and evidence patterns Bonus or extension section Closing formula and signoff Data philosophy Specific numbers per issue (count them) Source attribution style (linked, named, uncredited) Example to abstraction ratio Limitation or failure acknowledgements Formatting Header usage (frequency, hierarchy) List usage (numbered, bulleted, arrows) Bold and italic usage Prompt, code block, or blockquote formatting Visual markers (arrows, checkmarks, emojis if any) Length Word count range across samples Section word counts Voice markers unique to newsletter format Pro tips or callouts (frequency, format) Forward looking closings Signoff phrase if consistent across samples Meta transparency (does the author reflect on the process or ask for feedback) Absence signals Words, constructions, or structures absent from every sample Closing moves the author never uses Topics the author never touches Then go to Step 3. Step 2b. Archetype selection Call the AskUserQuestion tool with a single question: After the user picks an archetype, load the matching defaults from references/archetypes.md inside this skill folder. Tune every field using voice.md and about me.md before writing newsletter voice.md. Flag inside the output file that archetype defaults were used and the file should be revisited after 5 published issues. Step 3. Write newsletter voice.md Create newsletter voice.md in the project root. Single file, 800 to 1,200 words target. Use this structure: Fill every section from the samples (or tuned archetype defaults). No generic filler. If the samples do not cover something, say "no clear pattern across samples" rather than guessing. Step 4. Confirm and hand off Tell the user: Your newsletter voice is built. newsletter voice.md is in your project root alongside about me.md and voice.md. When you want to draft an issue, say "write a newsletter" and I will use all three files together. [If archetype mode: Remember this file was built from archetype defaults. After 5 or so published issues, re run this skill with your real samples for a sharper profile.] What this skill produces One file in the project root: newsletter voice.md: newsletter specific writing instructions covering audience, voice principles, opening formula, section flow, data philosophy, formatting, closing, absence patterns, and length targets Rules Require voice.md and about me.md in the project root before running. Stop and redirect to voice builder if either is missing. Minimum 2 newsletter samples if the user chooses sample based mode. Offer archetype mode if fewer. Keep newsletter voice.md under 1,200 words. Tight beats exhaustive. Do not invent voice signals. Work only from samples or archetype defaults tuned to voice.md. Do not duplicate content from voice.md. Reference it where relevant. newsletter voice.md adds newsletter specific rules only. Do not bake in the user's specific names, URLs, or signoff phrases unless they appear consistently across 2 or more samples. Do not produce a separate voice or banned words file. Absence patterns live inside newsletter voice.md as a single section. British English throughout unless samples are clearly American. Never use em dashes in any output file or in any draft.