XSource
Keep your Claude Code social media posts organized with a manifest file
by Marvomatic (@Marvomaticc) · 2026-05-20
✓ Opened via the X API on 2026-10-15
Read the original ↗Part 1 · What the source did
Generate posts in one session and publish in another by tracking each post's outline, status and schedule in a manifest file.
- Uses a manifest to track slide outlines, publish status and scheduling across sessions.
Summary written by Agent Cookbook. See the original for the full context.
Part 2 · Our copy-paste version
Adapted by us from what the source described. Fill in the [BRACKETS].
The prompt
Maintain posts/manifest.json. Each entry: id, topic, outline, status (draft|approved|scheduled|published), scheduled_for, file.
When I say "new batch: [TOPICS]", create drafts and entries with status draft. Never mark anything approved or published yourself. Edit entries in place; never rewrite the whole file.
🛡
Approval ruleOnly you change status to approved; the agent never posts.
Set it up
- Create posts/ and an empty manifest.
- Generate a batch.
- Mark approved by hand, then publish with your scheduler.
Common failures
⚠
What usually goes wrong
- The agent overwrites the manifest. Ask it to edit entries, not rewrite the file.
Variations
- Grok Bot routine that reminds you of approved posts that aren't scheduled.