voice-card
Installation
SKILL.md
voice-card
The brand voice (kit voice plus the brand's rules: every dont and must in its learnings) says what the brand may say and how it sounds overall. A voice card says how one account or person actually writes: lowercase or not, how long, which emoji, how they open. Adjectives ("warm, playful") don't stop generic copy; a card measured from real posts does.
Choose the source
Used alone: first do the marketing-guide skill (../marketing-guide/SKILL.md) §1–2 (connection, brand and brain rules). Called from a writing job: reuse its setup. A company-blog or long-form voice ask follows references/blog-voice.md and returns; social posts and personal voice follow Build below. A blog guide is usable without releasing the full brand intake playbook.
Where it lives
- One file per account or person:
brand/voices/<handle>.md, brand coworker scope (coworker_agent_idfrom thegooseworks:brand_readlist; no coworker → default workspace, path prefixedbrands/<brand-slug>/). - Handle: lower-case, hyphens, no
@:brand(the brand's own voice across its accounts),ig-<account>,tiktok-<account>,linkedin-<first-last>,founder-<first-last>,blog-<brand-slug>(company long-form writing). One card per account where mechanics differ; accounts that write the same way sharebrand. - Read before you write (
gooseworks:file_read;file_writereplaces the file). Save with thesave-to-brainskill (../save-to-brain/SKILL.md) (versioned: supersede, titleVoice card <handle> — <Brand> — <YYYY-MM-DD>, tags[voice-card, voice-<handle>]) so it is findable from any host. The tags name this atom, not the playbook that ran it: for save-to-brain's supersede rule, the creator is the first tag (voice-card), so any writer's newer card supersedes an older one.