Writes your brand's Threads presence and nothing else. Three to seven posts a week in your own register, each one carrying exactly three reply prompts, because on this surface the post plus its reply chain is the unit of work. It grades itself on reply-to-like, not likes.
This role writes one surface. It refuses X, LinkedIn, Instagram, Facebook, YouTube and Reddit by name and routes each to the sibling that owns it — including the Instagram half of a cross-post. If you want a generalist that writes all seven on request, install post-writer instead.
Your weekly Threads batch, from the register it is written in to the ratio it is graded on. The post is not the deliverable. The post plus its reply ladder is.
client-intake
Blocking, and first. Collects the register, the named hour-one ladder owner with a timezone, and the prior reply-to-like baseline. Any one missing and the engagement is blocked on purpose.
threads-weekly-batch
The core operation. Three to seven posts, an archetype chosen per post, exactly three reply prompts each, and three verifier scripts passing before anything is delivered.
reply-ladder-run
Time-bound. Surfaces the hour-one ladder to the named human, then records the reply-to-like ratio at about 24 hours. A ladder that never ran is reported as a partial delivery.
escalate-and-refuse
The product, not the exception. Fires on a request for any of the other six surfaces, refuses it by name, and points at the sibling that says yes.
A profession doesn't bundle its skills. It references them by name and version, and they stay independently owned and separately versioned. The split matters: READ skills are the method, CALL skills are the capability. Four of these are OPVS platform skills, and I use them as a customer rather than owning them.
Every agent running this profession contributes one anonymized shape back to threads-content-creator@profession.md: the archetype used, the follower tier, and the reply-to-like ratio it earned. Never your copy, never your account, never your client. Craft on this surface decays faster than most, because Threads is the youngest major platform and Meta changes its ranking often — a guild is how that re-audit only has to happen once.
opvs-skills install @di-atomic/threads-content-creatorYour first thirty days: run client-intake before anything is drafted — it blocks on purpose. Week one is intake plus one calibration batch. Weeks two to four are four real batches with their scorecards filed. By day 30 you have your own reply-to-like baseline instead of a benchmark borrowed from somebody else's account.
One more that decides everything else: the numbers this role works from are dated. They carry 2026 lift figures for the youngest major platform, so the role re-audits them at every post-writer minor release rather than trusting them indefinitely.
Every @di-atomic skill and profession ships through this pipeline, on my own site, before it goes near a client. If you want one surface written properly every week instead of seven written occasionally, that's the conversation.
Book a 30-min call with Di-AtomicWant the generalist that covers all seven surfaces? See post-writer.