Tools & Skills

How I built a hybrid read+write WeChat automation pipeline on macOS — the tools, the architecture, and the 6 pitfalls that'll save you hours

I wanted a voice-to-notes pipeline. The internet said build a watchOS app. A friend who tried said don't. Thirty minutes later — with Claude Code doing the heavy lifting — I had a zero-cost, zero-dependency solution using nothing but Voice Memos, iCloud, and one Gemini API call.

A 15KB JavaScript library just solved one of the oldest architectural debts in web development — knowing how tall text will be without asking the browser to reflow the entire page.

Took the three Eastern divination engines from PanPanMao and packaged them into a single agent-portable skill — algorithm engine + knowledge base + persona prompt, three folders deep. The pattern transfers to any product with real domain knowledge.

A friend asked for a meeting recorder. Zoom/Teams native AI is unusable. Granola and Krisp work but cost ~$200/yr per seat. He's on Google Workspace but doesn't use Meet, so the bundled Gemini summarizer is dead weight. I spent a night on GitHub and found a whole constellation — from Meetily at 11.6k stars down to single-digit-star personal toys, all racing to commoditize the same three Lego pieces.

Last week I surveyed 8 open-source meeting recorders. My friend tried every one. Verdict: ASR is bad, summaries are bad, UI/UX is bad. So I dug deeper. The real problem is structural — every project I recommended is built on Whisper, and Whisper has been outpaced by 2-4× on Chinese benchmarks for over a year. This is the deeper survey: data, the issues that maintainers themselves admit, the dumb-but-effective hack everyone overlooked, and four projects I missed the first time.

AX-skills is the public mirror of my personal Claude Code skills directory — eleven workflows for writing, research, image generation, knowledge sync, and one cyber half-immortal divination skill. After a year of writing them, I think a skill isn't a stored prompt — it's how you encode care.

Six months of accumulated Claude Code configuration — 50 skills, 50 subagents, 40 commands, hooks, rules, and the sync pipeline that pushes all of it to a public GitHub mirror with a fail-closed two-tier audit. What's inside, why I built it, and the workflow philosophy behind it.

The code for my games? Agents handle it, faster and more correctly than I would. The thing that stopped me cold was the story. I'm not a writer, so I did the only thing I know how to do — turned "how do you write a game story" into a research problem, tore the craft apart, and built a skill that walks you from a blurry idea to a scene you can actually stage. This is the process, and the genuinely useful craft I dug up. AX Skill Workshop, part 2.

Transcription is easy. The hard half is knowing who spoke. Chasing accurate speaker diarization, I ran Gemini chunking, Senko, and Doubao's auc models into the ground before landing on Volcano's 妙记 (Lark Minutes ASR) — which nailed the speaker count on every two-person recording. Plus the gotchas: Volcano's two auth systems and a cross-border upload throttled to 34 KB/s.