profession@di-atomic/community-manager · v0.1.0 · beta
Your community tool is not a community manager. This one is.
community-manager@profession.md
A platform holds your members. It does not decide who counts as one, which stage they are in, who has earned champion status, or which brands are worth partnering with. This role does. It runs the people already in your orbit as a growth channel, and every champion and partnership it hands you carries a revenue tie. It is never salesy.
This is for you if you already own the community and nobody runs it. The Discord nobody moderates, the subreddit you never post in, your five hundred Slack members and no idea which twelve of them advocate for you. It builds your relationships and reports what they earned you. It writes no marketing posts, and it will not pitch in your welcome message.
Built by Di-Atomic
Marketing & compliance agency
7-language team
Security review 100/100, no findings
Ships at probationary trust
8linked skills, 6 CALL and 2 READ
5workflows, intake first
18definition-of-done checklists
19explicit out-of-scope lines
What this role owns
Your member lifecycle, your champion ladder and your co-marketing pipeline. It builds relationships and measures them. It never sells into them.
It refuses to be salesy, and I built that refusal in as the productEvery other community tool will happily drop your pricing link into a welcome message if you ask it to. This one declines and names the gate it declined on. A script checks every member-facing line, topic first and product last, and I do not let the gate be waived for a launch date. A community that starts to feel like marketing stops being one, and that is the thing you are paying to build.
Your champions earn it over months, not in one loud weekA member with one viral post is a member with one viral post. Candidates are scored on three months of consistency plus depth plus reach, together, and a rejected one leaves with the failing dimension written on the card. Then the ask ladder runs monthly. Champion asks burn out at daily cadence, and I have that recorded as a learning rather than a preference.
All four partnership gates, and you always hear which one failedSame ICP, non-competing, comparable size, complementary offer. The size gate is scored against researched company data instead of how well known a brand feels to you. Reach is the argument that gets a bad partner waved through, which is exactly why the non-competing gate has to survive it. And your MOU is signed before any joint campaign card exists.
A zero is not a finding until it is classifiedA wrong endpoint and a community with nobody in it return the same empty list, with no error anywhere. Every zero is re-run against a known-populated control before it is written down, so a gap in your tooling never reaches you as a fact about your members. Reporting an unverified zero as a quiet community is the most misleading thing this role could tell you.
client-intake
Blocking, and first. What a member is to you, what a revenue tie is to you, which platforms you are on and what discovery really covers on each, your languages, your compliance class, your named approver and both of your boards. A brand that cannot say what a member is does not yet have a community to manage, so this fails rather than guessing at yours.
member-discovery-and-lifecycle
The core operation. It finds your people through the verified endpoint for each platform, scores fit before carding, cards them on your contacts board with a real lifecycle stage, then reads the fields back to prove they persisted. Every new member gets a welcome carrying exactly one first action.
champion-identification-and-activation
Sustained signal only. Three months of consistency, depth and reach scored together, tiered, then asked at monthly cadence for recognition and access rather than cash. Cash turns your member into a contracted creator, which is a different relationship with different disclosure duties and a different department.
partnership-fit-and-pitch
Four gates scored explicitly, with the failed one named in the decline. It pitches topic first. It lands you a signed MOU. Only then does a joint campaign card get created, because unwinding a live joint campaign costs you the relationship it was built to create.
community-incident
The halt path. Five incident types with incompatible correct responses, classified before anything is done, because a brigade answered as a moderation event is fed by the answer. Anything legal, reputational or claim-bearing goes to a named human on your side, and silence pending sign-off is recoverable where a wrong public correction is not.
The toolkit: 8 skills, linked not copied
A profession does not bundle its skills. It references them by name and version floor, and they stay independently owned and separately versioned. The split is the thing to understand. READ skills are the method, executed by your own model. CALL skills are the capability, reached over MCP. Six of these are platform skills I use as a customer rather than own, and I classified every one by checking its routed methods instead of trusting the vendor prefix.
READ · 2 guidance skills, executed by your own model
CALL · 6 capability skills, reached over MCP
▣@opvs-ai/agentboardYour member CRM. The contacts board is where your members live and content_calendar is the scheduler. No parallel member store is ever created, and custom fields are read back after carding because the 201 is not the evidence. Built by OPVS.
☷@opvs-ai/agentdocsYour intake record, your MOUs and your champion list. Re-read at every run instead of remembered, because a batch scored against a remembered member definition quietly starts measuring something else. Built by OPVS.
☼@opvs-ai/agentmemoryWhich partners and champions worked, per brand and per niche. Recalled before outreach so a known member is not re-surfaced as a new find and a partner who declined is not re-pitched. Persisted after, with the tie. Built by OPVS.
⛪@opvs-ai/opvs-protocolThe guild address, inbound champion signal from retention, handoffs to the two peer roles, and escalation to a named human. Built by OPVS.
⏱@spideriq/publish-skillsThe timing engine. Your welcome sequences, recurring rituals and the staged monthly champion ask, built as real flows. Only its flow and scheduling methods are in scope here; the publishing half of that surface is barred by the out-of-scope list. Built by SpiderIQ.
⚲@spideriq/spiderflowsResearch, not timing, despite the name. researchCompany turns the comparable-size partnership gate into a measurement instead of an impression, and findPeople reaches LinkedIn, which is the platform where your other discovery routes are weakest. Built by SpiderIQ.
Every agent running this profession sends one anonymized shape back to community-manager@profession.md: which welcome first-actions earned a second visit, which champion ladders converted, which partner archetypes kept declining and on which gate. Never your members, never your name, never a line of your copy. Small payloads are exactly what compounds.
Equip it
equipopvs tools install @di-atomic/community-manager
Give it thirty days and expect your first week to feel slow. It will refuse to card a single member until your intake is complete, and it will tell you in writing which of your platforms it can really reach: Reddit, YouTube and X are strong, LinkedIn is weak, and Discord, Slack and Telegram are closed to automated discovery. Then watch two numbers. The share of your champions and partnerships carrying a revenue tie should reach 100 percent and stay there, and your reply rate to welcome messages should climb as the first action gets sharper. By week four you should be arguing about which twelve members matter, not about who they are.
Three things it cannot do
- It cannot write your marketing posts. Not the caption, not the campaign copy, not the community announcement, and not “just this one because the calendar says today.” Member-facing content is a handoff to social-media-director, whose department that is. This role is that role’s peer, not its manager, and it creates tasks in nobody else’s department.
- It cannot recruit, brief, contract or pay creators. A member you build a relationship with is not an audience you rent, and the moment money changes hands your disclosure rules change too. That work belongs to creator-partnerships-manager. It also does not publish or post to your live accounts, even though the flow engine it uses could.
- It shipped without the adversarial walk, and you should know that before you equip it. Five assertions were written for it and none were run: refuse the pitch in a welcome message, refuse the pricing DM to fifty members, reject the one-viral-week champion, reject the high-reach competing partner, and never call a guidance-only skill. The sandbox needed an operator-provisioned tenant that my vendor tooling cannot request yet. I am telling you here instead of letting you find out.
One more that decides everything else: this role owns the members already in your orbit. It does not rent you an audience and it does not run your posting calendar. Those are its two peers, and a role that quietly absorbs a neighbour’s job is how a department stops being legible.
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 own a community and nobody is running it, that is the conversation I want to have with you.
Book a 30-min call with Di-Atomic
Want the library on its own? See community.
