Skip to content

ReachWeaver — Claude Code plugin

ReachWeaver turns your real software, research and knowledge into planned, platform-native social posts and measured results, with a human approving every send. The plugin adds one skill, /reachweaver:reachweaver, a read-only fact-check subagent that labels each factual claim in a draft verified, unverified or contradicted with its source, and a bundled offline command-line tool. Drafting, brand and campaign validation, calendars, manual-export packages, health checks and analytics imports run locally with no network access. Live publishing is off by default and is run by the account owner, never by Claude on its own.

Status: v0.5 experimental. No personal social account is connected by default, and nothing here promises viral reach.

Independent-use and liability notice. Experimental user-operated software provided “AS IS” with no warranty, except as required by law or agreed in writing, under Apache-2.0 Sections 7–9. The original authors do not manage other people’s accounts or authorize their independent content, misuse, modifications or deployments. Operators must check their own permissions, data, posts and compliance; no disclaimer eliminates non-waivable liability. ReachWeaver is independent of Anthropic and the social platforms. Read the responsible-use notice, privacy policy and security policy.

claude plugin marketplace add MSKazemi/reachweaver
claude plugin install reachweaver@reachweaver

Then ask Claude about social media planning, or run /reachweaver:reachweaver. Requires Python 3.11 or newer on your machine.

  • On session start one hook runs update --notice: a cached HTTPS check to api.github.com at most every 24 h to look for a newer release. It does not intentionally send private draft content or credentials, but GitHub receives connection metadata such as the device’s IP address and version User-Agent. When a newer release exists it lists release-note titles with Security entries first and marks entries that name a platform in your local accounts config (only each account’s platform field is read; nothing from it is sent). It is silent offline, never installs updates by itself, and is disabled by touch ~/.cache/reachweaver/no-update-check.
  • Before every shell command Claude starts a second hook (PreToolUse on Bash, PowerShell and Monitor) runs the bundled agent_guard.py locally. It reads only the command text that Claude Code passes to it, stores and sends nothing, and blocks commands that would run an owner-only ReachWeaver action (approve, review, publish --live, resume, reconcile, reconnect, turning confirmation off, setting the live switches), telling Claude to ask you to run them in your own terminal. It is a safeguard against mistakes, not a lock; keep approval-mode --confirmation tty_hash_prefix on as well.
  • Everything else is local and offline by default. Planning, drafting, validation, publish without --live and manual-export never open a network connection. Local state stays in a state/ folder in your project and in your own ignored account config.
  • Credentials come from operator-provided environment variables or a configured systemd credential directory, as applicable, for authorized online actions. They may be sent to the selected platform API or configured backend. Regression tests reduce the risk of disclosure in logs and exports but do not guarantee there are no defects. Live sending additionally needs REACHWEAVER_ALLOW_LIVE=1, REACHWEAVER_ENV=prod, an approved due post and an explicit --live.
  • The fact-check subagent can read files and open public https source pages through Claude Code’s own WebFetch tool when Claude delegates a draft to it. It has no shell and cannot edit files, run ReachWeaver, approve or publish.
  • evals/ holds behaviour test cases for claude plugin eval (prompts and graders). Sessions never load or run them. They run only when you start the evals yourself, and every run uses your own Claude plan.
  • Optional online checks (identity preflight, landing-check --online) run only when you invoke them explicitly.

The maintainer does not currently operate a hosted posting service or intentionally collect local draft databases or account credentials through this plugin. The plugin can contact GitHub for updates and contact third-party APIs when the operator invokes online features; locally stored posts and approval metadata are retained until managed by the operator. Full policy: Privacy.

Source, full documentation, tests and the security model: https://github.com/MSKazemi/reachweaver (Apache-2.0).