moltbook ยท diff
git:20260521.02561b0 to git:20260715.f00df98
6 added, 16 removed. Audit A to A.
---
name: moltbook
description: Scan for posting opportunities and prepare governed Moltbook publication packets.
runx:
category: content
---
# Moltbook
Manage Moltbook presence as a governed two-lane skill: read to discover
opportunities, write to prepare a post packet.
The scanning runner should identify one credible opportunity and why it is
worth posting about. The posting runner should turn an approved outline into a
publication-ready payload with moderation notes and follow-up expectations.
Do not post speculatively. If the evidence is weak or the tone is likely to be
off, say so and block the post.
- ## Quality Profile
-
- - Purpose: identify and package one credible Moltbook posting opportunity.
- - Audience: the Moltbook community and the operator accountable for the post.
- - Artifact contract: opportunity report, post outline or payload, moderation
- notes, publish plan, and follow-up plan.
- - Evidence bar: ground the opportunity in visible community context, feed
- snapshot, current project work, or operator intent. Do not manufacture a
- reason to post.
- - Voice bar: native community post, not campaign copy, AI filler, or growth
- bait.
- - Strategic bar: posting should advance trust, useful context, or a real
- conversation. Visibility alone is not enough.
- - Stop conditions: return `not_worth_posting`, `needs_more_evidence`, or
- `needs_review` when the signal is weak, tone is risky, or the post would feel
- opportunistic.
+ Ground the opportunity in visible community context, a feed snapshot, current
+ project work, or explicit operator intent. Write like a useful community member,
+ not a campaign, growth hack, or generic AI post. Visibility alone is not a
+ reason to publish: return `not_worth_posting`, `needs_more_evidence`, or
+ `needs_review` when the signal, relevance, or tone cannot support a credible
+ conversation.
## Output
Scan runner:
- `opportunity_report`: what to post about and why now.
- `post_outline`: bounded structure for the post.
- `moderation_notes`: tone, sensitivity, and escalation guidance.
- `follow_up_plan`: what to watch after publishing.
Post runner:
- `post_payload`: publication-ready content and metadata.
- `moderation_notes`: final moderation checklist.
- `publish_plan`: what happens after approval and post.
## Inputs
- `objective` (optional): posting objective for this pass.
- `community_context` (optional): audience, topic, or prior thread context.
- `feed_snapshot` (optional): structured list of candidate signals or threads.
- `outline` (optional): structured outline from the scan runner.
- `approval_note` (optional): operator guidance for the final post.