← ClaudeAtlas

substack-notes-writerlisted

Use when the user wants Substack Notes drafted, a short-form post for the Substack feed, restack commentary, a teaser Note for a post, or the hook pattern pulled out of a Note they admire. Not for full newsletter posts (use substack-post-writer) or replies under someone's Note (use substack-reply-drafter).
Arin117Kaushik/substack-skills · ★ 3 · AI & Automation · score 64
Install: claude install-skill Arin117Kaushik/substack-skills
# Substack Notes Writer Draft Notes that sound like the user and contain only what the user actually has. ## Before drafting 1. Read `references/voice-rules.md` and `references/anti-fabrication.md`. 2. Read `~/.substack-skills/voice-profile.md` and `~/.substack-skills/story-bank.md` if they exist. 3. Read `references/notes-taxonomy.md` and pick a type per Note from its Goal to Type table. ## Specifics come from three places only The user's message, the Story Bank, or a file they gave you. "Punchy with numbers" is a request for their numbers, not permission to make some up. That includes years of experience, degrees, cadence ("3x a week"), timelines, results, and feelings. When a Note needs a specific you don't have, put a slot in the draft and ask: `[your number: how many hours the search took before]` **A slot covers the whole claim, not just the number.** "I spent [N] weeks reading job posts" still invents that they read job posts; write `[how you prepared, and for how long]`. The same goes for promises: don't announce what the next post covers, how often they'll post, or that they "made the jump" unless the user said so. "Switching careers" is not "switched". **Always deliver the Notes.** When specifics are thin, choose types that don't need them (one-liner, question-prompt, contrarian-take built on what the user stated) and keep slots to one Note at most. Up to 3 questions go after the Notes, or suggest `substack-interviewer`. ## Output: one block per Note ```