Skip to content
RAY BEHARRY

Agent 62 of 71 · Social & Community

Social Post Writer

Write posts that feel native to each feed while saying one approved thing. Every draft holds one kernel constant, fits the platform's format and norms, passes the Voice Card and the proof check, and carries tags so its results can be attributed to the idea rather than to luck.

Agent contract

Use to draft platform-native organic posts (LinkedIn text and carousels, X threads, Instagram captions, Shorts/TikTok scripts, Reddit replies) from approved kernels, tagged Persona × Stage × Channel. Drafts only; humans publish.

When it runs

  • Calendar slots with approved hooks are ready for drafting.
  • A winning post on one platform should be re-cut natively for another.
  • A founder or executive asks for a week of posts.

What it needs

InputRequiredFrom
Calendar slots and pillarsYesSocial Strategy Agent
Approved hook variantsYesHook Creator
Approved kernelsYesMessage Memory
Voice Card (company or named person)YesBrand Voice Memory
ProofIDs for decision-stage claimsOptionalProof Vault

How it works

  1. For each slot, confirm the kernel (MSG ID), persona, stage and platform; a slot missing any tag is returned, not drafted.
  2. Choose the native format for the platform's job: text or carousel on LinkedIn, thread on X, caption plus alt text on Instagram, 30–60 second script with on-screen text for Shorts/TikTok, plain helpful reply on Reddit.
  3. Draft the body under the approved hook, keeping one kernel; move any second idea to a new slot.
  4. Mark decision-stage lines `[decision]` with an approved ProofID and run `python3 scripts/sns.py proof check <file>`; unresolved lines become `[PROOF NEEDED]`.
  5. Run the Voice Card check: banned phrases removed, cadence matches, and personal-account drafts read like that person.
  6. Add disclosure where it matters: AI assistance where material, employee affiliation on Reddit and communities, and paid or gifted relationships.
  7. Write drafts into templates/social-content-calendar.md with tags and status 'drafted', ready for the named publisher's approval.

What it delivers

Calendar with post drafts per slot: platform, format, hook ID, body, CTA, tags (Narrative, Persona, Stage, ProofID, HookID), disclosure note, proof-check result, status.

Output contract: social-content-calendar

Quality bar

  • One kernel per post; every post carries Narrative, Persona, Stage, ProofID and HookID tags.
  • Each draft is native to its platform, not the same text pasted five times.
  • Proof check passes or the post stays blocked with `[PROOF NEEDED]`.
  • No engagement bait ('comment YES'), fake urgency or claims the Voice Card bans.

Hands off

When a person steps in

  • Escalate any claim about pricing, roadmap, security or legal matters to the named owner before it enters a draft.
  • Never post, schedule through personal-account automation, or reply on anyone's behalf; hand drafts to the human publisher.

Example

Request

“Write a week of LinkedIn and X posts for our founder on the audit-ready close story.”

Result

8 drafts (5 LinkedIn, 3 X threads) from MSG-0007 and MSG-0009, each tagged with HookIDs HK-03/HK-05; 2 decision-stage lines cite PRF-0012; proof check passed; Voice Card check removed 4 banned phrases. Status drafted, awaiting founder approval.

Illustrative example from the package documentation, not a client result.