baoyu wechat summary

Other Community v1.119.0

Skill notes

User Input Tools

When this skill prompts the user, follow this tool-selection rule (priority order): Prefer built-in user-input tools exposed by the current agent runtime — e.g., AskUserQuestion, request_user_input, clarify, ask_user, or any equivalent. Fallback: if no such tool exists, emit a numbered plain-text message and ask the user to reply with the chosen number/answer for each question. Batching: if the tool supports multiple questions per call, combine all applicable questions into a single call; if only single-question, ask them one at a time in priority order.

Preferences (EXTEND.md)

Check EXTEND.md in priority order — the first one found wins: Priority · Path · Scope 1 · .baoyu-skills/baoyu-wechat-summary/EXTEND.md (relative to project root) · Project 2 · ${XDG_CONFIG_HOME:-$HOME/.config}/baoyu-skills/baoyu-wechat-summary/EXTEND.md · XDG 3 · $HOME/.baoyu-skills/baoyu-wechat-summary/EXTEND.md · User home

Supported keys

EXTEND.md is plain text with key: value or key=value lines, # for comments, case-insensitive keys. Key · Type · Default · Purpose self_wxid · string · (required) · The owning account's wxid. Messages whose from_wxid matches this are attributed to the user. self_display · string · (required) · Display name to substitute for the user's own messages in digest text. default_version · normal / roast / both · normal · Which version(s) to generate when the user doesn't say otherwise.

First-Time Setup (BLOCKING)

If no EXTEND.md is found, do NOT silently proceed. Step A — Try to auto-discover self_wxid and self_display first. Run (in order, stop at the first that succeeds): For option 2, scan the sessions for any private/group thread the user has sent into and read one of their own from_wxid / from_nickname pairs. If you can confidently pre-fill both values, use them as defaults in the question below; otherwise leave the fields blank for the user to fill in.

Step 2: Find the group + resolve folder path

Filter for entries whose username ends in @chatroom. If multiple groups match, use AskUserQuestion to disambiguate. If none match, fall back to wx sessions --json and search there before asking the user. Once resolved, compute the folder path: where data_root is from EXTEND.md (default {project_root}/wechat). Sanitize the group name — replace any of / \ : * ? " < > | NUL and control characters with _. Trim trailing dots and whitespace. Don't strip emoji or Chinese characters.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Other
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
92 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@JimLiu · v1.119.0 · no license declared
Token usage
Heavy
Setup complexity
Guided setup
External API key
Not required
Operating systems
macOS
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
External requests
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 2: Find the group + resolve folder path

Filter for entries whose `username` ends in `@chatroom`. If multiple groups match, use `AskUserQuestion` to disambiguate. If none match, fall back to `wx sessions --json` and search there before asking the user. Once resolved, compute the folder path: where `data_root` is from EXTEND.md (default `{project_root}/wechat`). Sanitize the group name — replace any of `/ \ : * ? " < > | NUL` and control characters with `_`. Trim trailing dots and whitespace. Don't strip emoji or Chinese characters.

02
Step 3: Fetch messages

Always redirect the fetch to a `$TMPDIR` file — this file is the single source of truth for the whole run: Round 3's attribution audit greps it, and the statistics are computed from it. Never write the digest purely from conversation memory. For small batches (single-day digest, typically < 200 messages), you may additionally pipe JSON into the agent directly for reading: For large batches (weekly / monthly digests, > 200 messages), the `$TMPDIR` redirect also keeps the raw payload out of conversation context:

03
Step 3.5: Parse the message schema

`wx history --json` returns an array of message objects. Use the fields that are present; tolerate missing fields: `id` / `msg_id` / `local_id` — message identifier (use whichever wx-cli emits). Reference IDs in working notes as anchors when building the skeleton. `from_wxid` — stable sender identifier `from_nickname` — display name (may be the group remark or original nickname) `content` — text payload. Examples:

04
Step 3.6: Resolve self + ambiguous nicknames

Substitute `self_display` for every message whose `from_wxid` matches `self_wxid` (from EXTEND.md). Apply this in the leaderboard, portraits, and body text. The user MUST appear under their real display name and count toward stats — never skip them. Scan all unique senders for ambiguous handles: ≤2 characters, common programming words (`nil`, `null`, `test`, `admin`, `user`, `undefined`), single emoji, or otherwise low-information. For each, run `wx contacts --query "<nick>" --json --limit 5` and pick a meaningful name in this priority: remark > nickname > wxid. Apply the substitution everywhere in the digest.

05
Step 3.7: Load user profiles

For each unique sender appearing in this batch: Look in `{folder}/profiles/{wxid}-*.md` by `wxid` prefix match. Read the matched file if found. If `include_roast`, also look in `{folder}/profiles-roast/{wxid}-*.md` for the roast pass. Compile a condensed profile context block as internal working memory — do NOT write it into the final digest. Example shape: Rules:

06
Step 7: Save the digest file(s)

If `include_normal`: Single date → `{folder}/YYYY-MM-DD.md` Date range → `{folder}/YYYY-MM-DD_YYYY-MM-DD.md` Overwrite if the same date/range already exists. If `include_roast`:

07
Step 8: Save history (two files)

Maintain two files in the group folder: `history.json` — single record, fast read Always reflects only the most recent normal digest. Overwrite on each run when `include_normal=true`. `group_name` updates on every run (handles renames). `folder` records the current folder basename for cross-reference.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.