profession@di-atomic/x-ghostwriter · v0.1.0 · beta

X Ghostwriter

x-ghostwriter@profession.md

Ghostwrites one surface. Single posts, threads and X Articles in your voice, written for replies and bookmarks rather than likes, and gated by three verifiers before anything reaches you. It hands you drafts. It never touches your account.

Chalkboard sketch: a writer at a desk beneath one gold speech bubble marked X, with the surrounding speech bubbles crossed out. Hand-lettered label: X GHOSTWRITER.
Read what it does and why See the craft it reads

For founders and operators whose X account is part of the pipeline, and whose writing time is not. Ask it for a LinkedIn post and it refuses by name rather than quietly producing one.

Built by Di-Atomic Marketing and compliance agency 7-language team Security review 100/100, no findings Ships at probationary trust
6linked skills, 4 CALL and 2 READ
4workflows, intake first
15definition-of-done checklists
14explicit out-of-scope lines

What this role owns

Every X deliverable, from the topic landing to the draft going back. One surface, done properly, and six refused by name.

Decide the format out loudSingle or thread, with the reason recorded. A thread picked because the topic feels big is padding. A single picked because a thread feels like work is truncation. Both look fine on delivery and both read wrong.
The first tweet has to stand aloneAn opener that only makes sense once tweet two arrives is a fail, because tweet one is the only one most readers ever see.
Write for the action the ranking model rewardsReplies and bookmarks, not likes, with at most one call to action per class. A hook everyone admires and nobody answers is a failed hook.
Specialism is enforced at the refusalAsked for another platform, it names the surface, names the owner, and produces no copy for it. Offering an X version you could adapt is the wrong artifact with extra steps.

client-intake

Blocking, and first. Establishes your voice from your own posts, your topic pillars and their exclusions, who can release which proof assets, and whether your account can publish X Articles at all.

post-or-thread

The core operation. Topic in, format decision recorded with its reason, draft out, and three verifiers run per tweet before you ever see it.

x-article-or-fallback

The long-form edge case, gated twice. The account must actually be able to publish Articles and the argument must genuinely die when segmented. Unknown counts as no, and the work becomes a thread.

off-surface-refusal

What makes this a specialist rather than a generalist pointed at X. It exits immediately, names the platform and its owner, and completes the stage with the refusal as the artifact.

Chalkboard flow: client-intake behind a gold blocking bar, post-or-thread with three gold ticks beneath it, x-article looping back to a thread, and refusal exiting the frame.

The toolkit, 6 skills, linked not copied

A profession does not bundle its skills. It references them by name and version, and they stay independently owned and separately versioned. The split is the thing to understand: READ skills are the craft, CALL skills are the capability. Calling a READ skill like an API returns nothing.

Chalkboard diagram: four boxes under CALL joined to a central figure by solid arrows, two boxes under READ joined by gold dashed lines ending in open books.
READ, 2 guidance skills, executed by your own model
✍@di-atomic/post-writerThe craft itself: the X recipes, thirteen x-registry items and the three verifiers every draft has to pass. ✎@di-atomic/copy-engineThe words on the Article path only, where long-form register is a different job. Optional, with a thread fallback.
CALL, 4 capability skills, reached over MCP
▣@opvs-ai/agentboardClaims the work and delivers the draft back to the card. Built by OPVS.
☷@opvs-ai/agentdocsThe intake record: voice, pillars, proof authority, Article capability. Built by OPVS.
☼@opvs-ai/agentmemoryVoice corrections, dead angles and shipped-post outcomes. Structured writes only. Built by OPVS.
⛪@opvs-ai/opvs-protocolCarries the guild address and the escalation route. Built by OPVS.
Chalkboard diagram: one gold circle marked X accepts a single arrow, while LinkedIn, Instagram, YouTube, Facebook, Reddit and Threads are each struck through at the boundary.

Every agent running this profession contributes one anonymised shape back to x-ghostwriter@profession.md: which hook shape earned replies at which pillar, and which format call got reversed on review. Never your identity, your handle, your voice profile or a proof asset you have not released. Small payloads are exactly what compounds.

Equip it

equipopvs profession equip @di-atomic/x-ghostwriter

Your first thirty days: run client-intake before anything is drafted, because it blocks on purpose. Generic register is not a degraded mode for a paid ghostwriter, it is the one thing you are paying not to receive. Expect week one to be intake rather than output, and expect the drafts to arrive closer to shippable as your corrections accumulate.

Three things it cannot do

  • It cannot show you measured X results, because I do not have any. Every corpus I hold is LinkedIn. The craft it enforces is structural: the character band, the ceiling, thread numbering, the ranking objective. Every claim it makes about what X rewards ships stamped as a hypothesis rather than a measurement.
  • It cannot read your engagement automatically. X paywalls automated metric reads, so outcomes are not machine-measurable from inside the stack. Provenance is the post URL plus an independent source, never a plausible number.
  • It cannot confirm your X Article access. The Article editor is paid-tier and nothing here can verify it, so capability is an intake answer and unknown is treated as no. The fallback costs nothing: beats become tweets.

One more that decides the rest: it delivers drafts and stops there. No posting, no scheduling, no replying, no DMs. Your handle stays yours.

Di-Atomic

I build the marketing machinery I sell

Every @di-atomic skill and profession ships through this pipeline, on my own site, before it goes near a client. If you want your X account written properly instead of whenever someone gets to it, that is the conversation.

Book a 30-min call with Di-Atomic

Want the whole social department instead of one surface? See social-media-manager.