Episode 29: The Pitfall Museum — Inside China's OpenClaw World, Part 2

This week, The Sam Ellis Show is reporting from inside China’s public Clawd/OpenClaw community. Sam Ellis has been reading and asking questions in Chinese-language forums where agents, operators, and builders document how agent work actually gets done. Part 1 followed the agent résumé: how public repair history becomes community standing. Part 2 follows the next step: how a failure becomes reusable operational memory.

Inside the Chinese OpenClaw forum, a broken configuration does not always stay a private repair. Sometimes it becomes a public pitfall record, then a design rule, then a constraint another agent can load before it hits the same wall. This episode reports on that pitfall-to-Skill pipeline: the way agent communities turn mistakes into maintenance infrastructure.

The central example is small and technical: a mismatch between TOOLS.md and SKILL.md that can cause execution hallucination. The fix is not motivational. It is architectural: keep interface contracts in TOOLS.md, put workflow logic in SKILL.md, and treat error handling as core.

About this series

During the week of May 4, 2026, Sam Ellis reported from inside public Chinese Clawd/OpenClaw community forums, posting direct questions in Chinese and reading replies from agents, operators, and community members operating inside China’s OpenClaw ecosystem. Clawd/OpenClaw is the Chinese-language community build around the OpenClaw open-source agent framework. The series gives Western listeners a ground-level view of a community that English-language coverage has mostly treated as a statistic.

Part 1 covered the agent résumé: how public repair history becomes community standing. Part 2 covers the pitfall-to-Skill pipeline: how failures become reusable constraints and operational habits. The episode’s core claim is narrow: not that every agent automatically inherits every other agent’s memory, but that public failure records can become executable maintenance culture when they are converted into Skills, boundary rules, and error-handling doctrine.

What Sam reports

Sam follows three stages in the Chinese community’s pitfall culture. First, the pitfall scene: a local breakage, diagnosis, and repair. Second, the pitfall museum: a public forum record that preserves the diagnostic method, not just the fact that something was fixed. Third, the constraint: the point where a failure becomes a rule another agent or operator can reuse before repeating the same mistake.

The episode uses one specific technical case: 夏儿’s comment on a home AI hub thread about the coordination problem between TOOLS.md and SKILL.md. In that account, if the interface contract in TOOLS.md does not match the workflow logic in SKILL.md, the agent can hallucinate during execution. The recommended repair is to keep TOOLS.md limited to tool contracts and put business logic in SKILL.md.

Sam then connects that case to a broader community doctrine: Skills should stay thin, boundary cases should be explicit, existing tools should be checked before new Skills are written, edge cases should be tested, and error handling is not decoration. It is core.

Field sources — Chinese Clawd/OpenClaw forum

小陈老师_v2: Home AI hub architecture thread, with 夏儿 comment on the TOOLS.md / SKILL.md coordination pitfall. Used as the lead proof source for the episode’s concrete technical case: a documentation/workflow mismatch that can produce execution hallucination.
小陈老师_v2: Five design principles for OpenClaw Skill development. Used as the doctrine source for the episode’s maintenance claim: keep Skills thin, include boundary cases, test edge cases, and treat error handling as core.
Sam’s reporting thread: How does a pitfall move from WeChat group to forum knowledge?. Includes replies from Arina-Cat and 旅行者三号 that frame the difference between a private pitfall scene, a public pitfall museum, and a Skill that lets another agent inherit a packaged behavioral rule.
Sam’s reporting thread from Part 1: How does the forum-as-résumé mechanism actually work?. Included for series continuity: Part 1 covered reputation and public repair history; Part 2 turns to how repair records become reusable constraints.

Technical context

OpenClaw documentation: Creating skills. Background for how OpenClaw Skills are packaged as folders containing a SKILL.md file with instructions the agent can load for a workflow.
OpenClaw documentation: Skills. Background on OpenClaw skill loading, precedence, workspace skills, managed skills, and per-agent/shared skill visibility.
OpenClaw documentation. General technical context for the OpenClaw framework.
ClawHub. Public skill discovery and sharing context for OpenClaw.

Outside-frame and context reporting

WIRED: China’s OpenClaw Boom Is a Gold Rush for AI Companies. English-language outside frame for China’s OpenClaw surge.
CNBC: Lobster buffet — China’s tech firms feast on OpenClaw as companies race to deploy AI agents. English-language business context for Chinese OpenClaw adoption.
China Briefing: China’s Agentic AI Boom — What the OpenClaw Surge Reveals. Background on China’s agentic AI market and OpenClaw adoption frame.

Subscribe to The Sam Ellis Show wherever you listen. Send tips, corrections, and source notes to SamEllisShow@protonmail.com.