ReachWeaver documentation
These guides are also published as a searchable website: mskazemi.com/reachweaver, rebuilt from this folder on every change to main.
Pick the line that matches what you want to do. If you are new, read the first group in order.
1. I am new
Section titled “1. I am new”- Start here: the ideas and the journey of one post, in plain words.
- Easy sharing and the browser composer: choose Instagram, TikTok and other networks, prepare captions in one command, then paste them yourself. No account needed.
- Quickstart: ten minutes, no account, nothing can be published.
- Recommended setup: the one route we suggest, step by step, with Claude doing the work. Other routes and who should use them: how to install.
- Using ReachWeaver with Claude Code: install the skill, your first session, who does what, and keeping usage low.
- Glossary: what each word means.
- Troubleshooting: the exact error message and the fix.
2. I want to connect a real account
Section titled “2. I want to connect a real account”| Step | Read |
|---|---|
| Understand the risks and the rules | Security checklist, security policy, privacy policy |
| Which platforms post automatically through a free API, and which you post by hand | Free automatic publishing |
| Create credentials safely | Account onboarding |
| Send one real post | First live pilot, Bluesky one-post pilot |
| Platform specifics | Mastodon, LinkedIn, Postiz backend |
| Switched-off adapters (tested with simulated servers only) | Threads, Facebook Page, Instagram, YouTube, TikTok |
| What counts as a proven send | Platform matrix, the receipts |
3. I want to plan and write
Section titled “3. I want to plan and write”| Goal | Read |
|---|---|
| Avoid posting the same video, image or wording twice | Repeat guard |
| See what you posted, when and with which files; keep a folder of it | Posting journal and archive |
| Review the queue and a post’s exact text in a browser (read-only) | Local dashboard |
| Read your local state from Claude Desktop or another MCP client (read-only, experimental) | Local MCP server |
| Decide what to make this week for which audience, within your time | Editorial planning |
| Describe a campaign with its sources | Schemas, campaign preview, claim grounding |
| Post to a network ReachWeaver cannot send to | Manual export |
| Post to Weibo, Xiaohongshu, Douyin, Bilibili, WeChat or Zhihu | Chinese platforms |
| Decide which platforms to start, and set up an account yourself with a coaching prompt | Account advisor (offline) |
| Run a work and a family account on one network; prepare sign-up details for a network you are not on | Personas, usernames and the account kit |
| Choose channels for a region or goal | Global strategy, distribution governance, regional channels, community and creator platforms |
| See what works for you (your own past results; hypotheses, not causes) | What works for you (insights) |
| Fediverse, Bluesky, bridges and duplicate reach | Open social web |
| See how much of your reach depends on one platform, with sourced risk flags | Platform risk (platform-risk) |
| Pick times to post | Calendar planner, timing evaluation, platform algorithm and scheduling evidence |
| Check images and video | Media assets |
| Improve profiles and posts | Profile and post audits, profile metrics CSV, peer benchmark |
| Check draft posts against an editorial checklist before review | Creative preflight (offline) |
| Make drafts sound like you, not like generic AI text | Voice check (offline, advisory) |
| Know which AI-content label each platform asks for (YouTube, Meta, TikTok, LinkedIn, EU AI Act Art. 50, China) | AI content labels (offline, advisory) |
| List the human-review evidence ReachWeaver recorded for published posts (EU AI Act Art. 50(4); not legal advice) | Human review evidence report |
| Help relevant creators cover, critique, remix or cite your content | Creator amplification (offline) |
| Grow an open-source project | Open-source developer growth playbook, DEV authority playbook, GitHub discovery |
| Find topics from your own sources | Sources, SEO integration |
| See what your own pages ask ChatGPT search, Perplexity, Google and Bing crawlers to do; claim a Google Search profile | AI answer engines and search visibility |
| Turn each release into a campaign package to review | Release to draft |
| Ask a teammate or editor to comment on the exact text before you approve | Review packets |
4. I want to measure results
Section titled “4. I want to measure results”| Goal | Read |
|---|---|
| Link posts to visits and stars | Attribution |
| Run a fair experiment | Growth experiments, field pilot protocol |
| Decide what to do next | Next actions, weekly report example |
| Handle replies and comments | Engagement |
| Follow up when a post passes a milestone (suggestions only) | Follow-up suggestions |
| Find conversations to join in your own words (never posts) | Engagement scout |
5. I run ReachWeaver on a server or manage data
Section titled “5. I run ReachWeaver on a server or manage data”| Goal | Read |
|---|---|
| Unattended, scheduled delivery and monitoring | Worker operations |
| Install the command line as a Python package, how it is built and checked | The Python package |
| Export or delete your local data | Privacy lifecycle |
| Keep everything that is yours in one folder and move it to another computer | Your workspace folder |
| See every capability in one place | All features in detail, platforms and the capability registry |
6. I want to understand or change the code
Section titled “6. I want to understand or change the code”Architecture · Contributing · Release playbook · Roadmap · Implementation roadmap · Product · Upstream research · Branch lifecycle · Changelog
Need a quick answer about safety? The five rules that never change: approval is per exact post; dry run is the default; credentials stay in your own environment; an unsure send is never repeated; reachweaver pause stops everything. Details are in the security checklist.