https://github.com/nowhitestar/meti
One manifest, every Chinese-platform you publish to. Drafts on WeChat OA · Xiaohongshu · X Articles · Substack · WeChat 贴图 from a single YAML.
https://github.com/nowhitestar/meti
automation claude-code content-publishing draft-first manifest-driven openclaw publishing python substack wechat x-articles xiaohongshu
Last synced: 1 day ago
JSON representation
One manifest, every Chinese-platform you publish to. Drafts on WeChat OA · Xiaohongshu · X Articles · Substack · WeChat 贴图 from a single YAML.
- Host: GitHub
- URL: https://github.com/nowhitestar/meti
- Owner: Nowhitestar
- License: mit
- Created: 2026-05-05T06:29:25.000Z (29 days ago)
- Default Branch: main
- Last Pushed: 2026-05-26T03:58:26.000Z (8 days ago)
- Last Synced: 2026-05-26T05:27:10.255Z (8 days ago)
- Topics: automation, claude-code, content-publishing, draft-first, manifest-driven, openclaw, publishing, python, substack, wechat, x-articles, xiaohongshu
- Language: Python
- Homepage: https://liao.uno/meti/
- Size: 590 KB
- Stars: 0
- Watchers: 0
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- Contributing: CONTRIBUTING.md
- License: LICENSE
- Code of conduct: CODE_OF_CONDUCT.md
Awesome Lists containing this project
README
Meti
One manifest, every Chinese-platform you publish to.
## Why
Meti (μῆτις, *mētis* — Greek for "wise counsel"; *meticulous* in English; 媒体 *méi-tǐ* — "media" in Mandarin). Three readings, one idea: **publishing should be careful, deliberate, and reproducible — not a tab-juggling marathon.**
Writers who care about more than one Chinese-platform audience face the same chore: open WeChat OA, paste, save draft. Open Xiaohongshu, paste, save draft. Open X, paste, save. Open Substack, paste, save. Each platform forgets what the other knows. Each tab is a place a typo can hide. Each retry costs the same five minutes.
Meti collapses that into **one YAML manifest → drafts on every platform**, with an explicit safety model:
- **Draft-first by default.** Public publishing requires explicit opt-in *plus* an in-conversation confirmation. Mistakes stop at the draft folder.
- **Cookies stay in your real Chrome.** No CDP debug-port dance, no fresh-Chromium login dance. Browser-flow providers reuse your existing logged-in session via the [OpenCLI Bridge](https://github.com/jackwener/opencli) extension.
- **Credentials are encrypted at rest.** `age`-encrypted vault at `~/.config/meti/credentials.json.age`. Secrets never appear in run artifacts.
- **Every run is reproducible.** A self-contained run dir captures the locked manifest, payloads, checkpoints, log, and result. Resume from any failure point with `meti resume `.
Works as a [Claude Code](https://claude.com/claude-code) plugin **and** as an [OpenClaw](https://openclaw.com) skill from the same source — say what you want in natural language, and the wizard walks you through source extraction → target selection → manifest assembly → draft.
## See it
| Provider | Drafts to | How it gets there |
|---|---|---|
| `wechat-article` | 公众号 图文 (article) | WeChat Open Platform API — `material/add_material` + `draft/add` |
| `wechat-image` | 公众号 贴图 (image post) | OpenCLI Bridge → real Chrome → `DataTransfer` injection |
| `xiaohongshu` | 小红书 草稿 (note) | OpenCLI Bridge → real Chrome → Creator Studio |
| `x-article` | X Articles (Premium) | OpenCLI Bridge → real Chrome |
| `x-thread` | X thread composer | OpenCLI Bridge → real Chrome, stops before `Post all` |
| `substack` | Substack post draft | OpenCLI Bridge → real Chrome |
All browser-flow providers reuse your logged-in Chrome session; Meti does not ask you to capture raw cookies for them. See [docs/browser-connectors.md](docs/browser-connectors.md).
## Install
**As a Claude Code local plugin** (current recommended path)
```bash
git clone https://github.com/Nowhitestar/meti.git
# Claude Code: settings → plugins → load from directory
```
**As a Claude Code marketplace plugin** (future path)
The Claude Code marketplace submission is pending. Once Meti is listed, the install becomes:
```
/plugin install meti
```
**As an OpenClaw skill**
```bash
git clone https://github.com/Nowhitestar/meti.git ~/.openclaw/skills/meti
```
**Versioned release install / update**
```bash
# latest stable from GitHub Releases
scripts/install.sh --latest --target ~/.openclaw/skills/meti
# pinned install or rollback
scripts/install.sh --version vX.Y.Z --target ~/.openclaw/skills/meti --yes
# from an existing checkout/install
meti update --latest
meti update --version vX.Y.Z
```
Normal reinstall/update preserves `~/.config/meti`,
`~/.config/meti/credentials.json.age`, and `~/.config/meti/age-key.txt`.
**Direct CLI** (Python ≥ 3.10)
```bash
python3 -m venv .venv
.venv/bin/python -m pip install -e ".[dev]"
.venv/bin/meti --help
```
The editable dev install includes runtime dependencies such as `pyrage` and
`tomli_w`. Using a venv avoids Homebrew Python's PEP 668
externally-managed-environment failure; use global pip only in environments
where global installs are explicitly allowed.
**Optional: OpenCLI Bridge** for `wechat-image`, `xiaohongshu`, `x-article`, `x-thread`, and `substack`. One-time setup:
```bash
brew install node # or apt install nodejs npm — needs Node ≥ 21
# Install Chrome extension: https://chromewebstore.google.com/detail/opencli/ildkmabpimmkaediidaifkhjpohdnifk
meti browser status # → OK Browser Bridge connected
```
Full setup: [docs/browser-connectors.md](docs/browser-connectors.md).
Distribution, clean install, upgrade, and pre-release checks are documented in
[docs/distribution.md](docs/distribution.md). The automated release gate is
draft-safe and account-free by default:
```bash
python scripts/check_release.py
```
## Quickstart
**The conversational wizard** (in Claude Code or OpenClaw):
> 帮我把这篇文章发到公众号、X 长文、Substack 草稿。
The wizard reads `core/wizard/*.md` and walks you through extraction, target selection, manifest assembly, and draft execution — no manifest YAML to hand-write.
**The CLI** (when you already have a manifest):
```bash
# Validate without executing
meti validate examples/longform.yaml
# Configure credentials for a provider
meti setup wechat-article
# Publish (defaults to draft mode in the manifest)
meti publish examples/longform.yaml
# Resume from where the last run failed
meti resume runs/20260507-001255-mmp
# Inspect state
meti list providers
meti providers list
meti list accounts
meti list runs
meti doctor
```
After `publish` or `resume`, inspect `runs//result.json` for the
schema-v2 run contract: top-level `status`, `next_action`, `resume_targets`,
`review_targets`, and per-target `next_action`. See
[docs/run-results.md](docs/run-results.md).
A minimal manifest:
```yaml
schema_version: "0.2"
type: longform
title: "AI for the rest of us"
body: ./article.md
mode: draft
language: zh-CN
targets:
- wechat-article
- x-article
- substack
assets:
cover: ./cover.png
tags: [ai, essay]
```
## Design
**One language, every constraint encoded.** Meti's manifest is a YAML version of "what should land on every platform" — title length caps, tag count limits, image-format constraints all live in `providers/*/rules.py` and run before any network call. A 64-character WeChat title and a 280-character XHS title are both rejected at validate-time, not at the platform.
**Provider abstraction is small on purpose.** Five methods (`validate`, `prepare`, `execute`, `health_check`, plus a registration block). New bundled platforms drop into `providers//`; user providers live under `~/.config/meti/providers//` and require explicit `meti providers trust ` before their Python is imported. See [docs/provider-contract.md](docs/provider-contract.md), [docs/provider-api-template.md](docs/provider-api-template.md), and [docs/provider-browser-template.md](docs/provider-browser-template.md).
**Two execute paths per platform:**
| Path | When | Trade-off |
|---|---|---|
| **API** (`wechat-article`) | Platform exposes a draft API + you have AppID/Secret | Fast, scriptable, no Chrome dependency |
| **Browser-flow** (`wechat-image`, `xiaohongshu`, `x-article`, `x-thread`, `substack`) | No API exists, OR API can't create the post type | Reuses real Chrome session, works inside the browser the platform expects, breaks when platform UI drifts (selectors are constants at the top of each `internal/browser_flow.py`) |
**Safety is a property of the design, not a runtime check.** `mode: draft` is the default for every provider. Bundled providers currently advertise `publish: false`; reopening public publish support would require explicit future provider work plus an active confirmation gate. Vault writes are atomic (tmp + fsync + os.replace) under flock — no concurrent-write data loss. Run dirs are append-only — `result.json` is written once, at the end.
Full architecture: [docs/architecture.md](docs/architecture.md). Safety policy: [docs/safety-policy.md](docs/safety-policy.md). Browser connector internals: [docs/browser-connectors.md](docs/browser-connectors.md).
## Project layout
```
core/ # host-agnostic Python (manifest, providers, vault, runs)
providers/ # bundled first-party providers
wechat_article/ # API
wechat_image/ # OpenCLI Bridge (贴图)
xiaohongshu/ # OpenCLI Bridge
x_article/ # OpenCLI Bridge
x_thread/ # OpenCLI Bridge
substack/ # OpenCLI Bridge
scripts/meti.py # CLI entry
.claude-plugin/ # Claude Code plugin manifest
SKILL.md # OpenClaw + Claude Code skill manifest
docs/ # user-facing docs
tests/ # 142 unit + integration tests
```
## Roadmap
- ✅ **v0.2** — Provider abstraction + dual-host distribution + wizard + age-encrypted vault
- ✅ **v0.3** — WeChat API proxy (split-routing IP whitelist) + vault hardening + `meti resume`
- ✅ **v0.3.1** — `x-article` + `substack` connectors via OpenCLI Bridge
- ✅ **v0.3.2** — `wechat-image` (贴图) connector — solves the local-file-upload + request-signing field problem
- ✅ **v0.4** — Rebrand to Meti
- ✅ **v0.4.x** — `xiaohongshu` and `x-thread` browser-flow draft paths
- 🔒 **v0.4.x** — Marketplace and distribution readiness: version sync, release gate, clean install docs, submission packet
- 💤 **Deferred** — `wechat-channel` (视频号) connector
- 💤 **Deferred** — Multi-account routing (`target.account: `) + per-provider session-expiry detection
## Contributing
Bug reports, feature requests, and provider PRs are welcome. See [CONTRIBUTING.md](CONTRIBUTING.md) for the dev environment, test conventions, and provider authoring guide.
The fastest way to add a new platform: copy [`providers/substack/`](providers/substack/) (smallest browser-flow provider), update the URL pattern + selectors, register in the manifest schema. Real-account verification is mandatory before merge — see [docs/manual-verification.md](docs/manual-verification.md).
## License
[MIT](LICENSE) © 2026 Lewis Liao