WeRead to flomo

Sync WeRead (微信读书) highlights and notes into flomo with incremental deduplication and configurable sync scope. Use when the user wants to export or sync WeRe...

Security Scan

The skill's code and instructions are coherent with its stated purpose (syncing local WeRead Markdown exports to a flomo webhook); it reads exported markdown, posts to the provided webhook, and tracks state locally — no unexplained network endpoints or elevated privileges are present.

Purpose & Capability

The script and SKILL.md implement WeRead -> flomo syncing as described: parsing local Markdown exports, building content, POSTing to a flomo webhook, and tracking sent entries. Minor mismatch: SKILL.md suggests setting WEREAD_COOKIE, but the included script does not use any cookie — likely the cookie is needed outside the skill when producing WeRead Markdown exports, not for this script itself.

Instruction Scope

Runtime instructions are narrowly scoped: they direct the agent/user to run the included script against a specified local directory of exported .md files and to provide a flomo webhook. The skill only reads files from the provided weread-dir and a per-directory state file; it does not instruct reading unrelated system files or secrets.

Install Mechanism

There is no install step (instruction-only with an included script). Nothing is downloaded or written outside the user's explicit weread-dir/state file. This is the lowest-risk install posture.

Credentials

The registry metadata lists no required env vars, but SKILL.md advises setting FLOMO_WEBHOOK (and mentions WEREAD_COOKIE). The script accepts the flomo webhook as an argument and will POST content to whichever URL is provided — this is expected and proportionate. The webhook is a sensitive secret (it can accept arbitrary notes), so the skill's need for that secret is reasonable but should be treated carefully. The advertised WEREAD_COOKIE is not used by the script and therefore appears unnecessary here.

Persistence & Privilege

The script writes a local state file (.weread-flomo-state.json) inside the provided weread export directory to track sent items. The skill does not request persistent platform-wide privileges, does not set always:true, and does not modify other skill configs.

Assessment

This skill appears to do what it claims: read local WeRead-exported Markdown files, POST entries to a flomo webhook you supply, and record which items were sent in a state file under the export directory. Before using it: (1) review the script yourself (it's included) to confirm expected behavior; (2) keep your FLOMO_WEBHOOK secret and supply it via an environment variable or CLI argument as suggested — the script will send content to that URL; (3) run --dry-run first to preview what would be sent; (4) be aware the script creates/updates .weread-flomo-state.json in the export directory; (5) the SKILL.md mentions WEREAD_COOKIE but the script doesn't use it — that cookie may only be relevant for producing the Markdown export outside this tool; (6) avoid putting webhook URLs or cookies into the skill directory or any public repo. If you want higher assurance, run the script in a controlled environment and confirm that the webhook endpoint belongs to flomo (or another trusted destination) before sending real data.

Use this skill to move WeRead highlights/notes into flomo safely.

Default workflow

1. Export WeRead notes into local Markdown files first.
2. Set FLOMO_WEBHOOK and WEREAD_COOKIE via environment variables or config files outside the skill package.
3. Choose one sync scope:
   • today: only today's new entries
   • date: entries from a specified day
   • all: full migration
4. Use local state tracking to avoid duplicate pushes.
5. Run --dry-run before the first real sync or before a bulk migration.
6. Prefer today or date mode when the user already has historical reading notes in flomo.

Modes

1. Sync today's new entries

python3 ./scripts/weread_to_flomo.py --weread-dir /path/to/weread --mode today --flomo-webhook "$FLOMO_WEBHOOK" --dry-run
python3 ./scripts/weread_to_flomo.py --weread-dir /path/to/weread --mode today --flomo-webhook "$FLOMO_WEBHOOK"

2. Sync a specified date

python3 ./scripts/weread_to_flomo.py --weread-dir /path/to/weread --mode date --date 2026-03-26 --flomo-webhook "$FLOMO_WEBHOOK"

3. Full migration

python3 ./scripts/weread_to_flomo.py --weread-dir /path/to/weread --mode all --flomo-webhook "$FLOMO_WEBHOOK"

Sync scopes

• today: sync only entries whose WeRead timestamp falls on the current Asia/Shanghai day.
• date: sync only entries from --date YYYY-MM-DD.
• all: migrate all exported entries.

Tag template

Default output:

内容正文

#02_读书 #02_读书/「书名」

Override with:

--tag-prefix "02_读书"

State and dedup

• State file defaults to .weread-flomo-state.json under the WeRead export directory.
• Dedup uses bookmark:<id> / review:<id>.
• Re-running the same scope only sends unsent entries.

Notes

• Keep webhook/cookie outside the skill directory.
• Dry-run on first use.
• If the user already manually copied many old notes into flomo, prefer today or date mode before all.

References

• Read references/formatting.md when adjusting output structure or tag conventions.
• Read references/publishing.md when preparing the skill for ClawHub publication.