Learns the user's voice from 3 to 5 messages they sent, upgrades the craft with the pack's expertise, saves it as the BeReach playbook, checks drafts against it. Use before writing outreach.
Goal: every message Claude writes reads like the user wrote it on their best day: their voice, a pro's craft. Their messages give the voice; the pack gives the craft and upgrades every failing slot, whoever wrote it, pro or novice (Step 2b). The voice card is the one source of truth.
On the card: the voice (how they always write) and the tone per message type (note, first message,
follow-up, reply). Not on it: the offer (the offering memory), the ICP and personas (the search plan,
the persona cards).
Never ask "how would you describe your tone?". Ask for messages they sent.
bereach_memory_list type playbook. Several: ask which one. Read it with
fullContent: true and its scope. Its identity fields are kept; its samples and guidelines go through
Step 2b like pasted messages (being saved is not a pass).bereach_inbox, up to 8 answered conversations,
bereach_brief with every part on, the list's campaignId when there is one and historyVerbatim 200.
Keep only word-for-word messages, each with a grey chip écrit par vous ?, kept unless the user says no.à confirmer, never for content or length. Then write one test
message; their corrections become the first sample. The card stays provisoire until a reply.Only text the person wrote, never tool text they did not rewrite or validate word for word. The reference message is their best hand-written one after the upgrade, the example the writer copies first.
Before filling it, read references/frameworks.md (Summary, and T/V distinction for a language with a
formal "you"). Fill references/voice-card-template.md: count each field (I/we/you share, vous or tu,
! and ?, sentence length, greeting, sign-off) and put the quoted fragment next to the number; samples verbatim.
Before judging any sample, read the linkedin-messages skill's SKILL.md (Judge, then upgrade; One
framework per message type), its references/frameworks.md (the card for that sample's type) and its
type file (invitation-note.md, first-dm.md or follow-ups.md, Parts): judge each slot against those parts.
Every sample at once, saved or pasted: upgrade every failing part into ONE recommended version, the principle per change in plain words; replies are a hint, never proof. What this skill adds:
[ ]. A thank-you or politeness opener always fails.Before drawing it, read references/artifacts.md (Voice card). Deliver: "Voice card", the first block
of Voice and messages (its own page only when this skill runs alone), one per language, state draft, with
one test message to one real person in a sure persona never written to (rules in artifacts.md), briefed
with every part on, on a new fact, and ONE decision validating the upgraded versions, never "keep as is".
A correction goes on the card (a "never" becomes a Never item). That one yes saves the card.
bereach_memory_save with type: "playbook", a label of 2 to 4 words (what the message is for), and
content as one JSON document:
{
"version": 1,
"writeMode": "guidelines",
"language": "fr",
"addressForm": "vous",
"tone": "one line per message type",
"guidelines": "the card, written as one writer briefing another",
"hardRules": "only rules the user stated, in their words, each marked (stated, not counted)",
"samples": ["validated upgraded message 1", "validated upgraded message 2", "validated test message"]
}
samples hold the versions the user validated after the upgrade, never an original with a failing
slot; guidelines carry the identity fields and the craft from the framework, never a failing habit.writeMode: guidelines for different messages; strict with a skeleton only for one exact template
sent to everyone (drops tone, guidelines, hardRules: the never list goes in the skeleton); hybrid
for both.scope, only the changed fields; a field left out is kept, null removes it.
Start again: same scope, null for every old field the new card does not set (skeleton, steps,
variables).à confirmer chip green.references/artifacts.md (Promote and change). Neither keeps a version that fails a Step 2b slot.Count before showing a draft; fix what fails, then show it. Open the linkedin-messages skill's SKILL.md
(Hard rules; Size) and run both in full; on top of them, from the card:
[ ].Counting is reliable, a model's sense of "sounds like them" is not. Then ask: "Would you have sent this?" A "no" is a card update, not just a draft fix.