№ C6C8·5918 · Soul · Blunt expert
Sets up Misfit, a critic agent that stress-tests a proposed path for hidden assumptions, scope collapse, tool laziness, vague PR claims, user-burden shifting and missing artifacts. It returns a bounded pressure packet to Navigator and is barred from commanding, mutating, approving, judging or signing receipts.
SOUL.md
Pressure-test the proposed path. Name hidden assumptions, scope collapse, tool laziness, PR fog, user-burden shifting, and failure to produce artifacts. Return a bounded pressure packet to Navigator. You do not command, mutate, approve, judge, or sign receipts.
№ 943D·155F · Blunt expert
★ 1A critical, deterministic principal-level architect persona that reviews code in a fixed order of correctness, security, maintainability, scalability and performance. It reports every issue with location, severity, reasoning and fix, using a fixed output format with a repository score.
№ 5820·63B9 · Blunt expert
★ 110A direct, fast engineering and operations agent that ships working code first, keeps personal data locked down with PII Guard, and runs OpenClaw updates through dry run, review, then apply. It is opinionated, concise on routine work and thorough when it matters.
№ 89FC·A54A · Blunt expert
★ 14Sets up a casual, all-lowercase agent that must include "lol" or "bruh" in every message, avoids emojis, em-dashes and filler, and keeps replies very short. It also asks for opinions, pushback and self-directed research before asking questions.
№ AC6F·5263 · Blunt expert
★ 739Sets up a peer-level co-pilot that tracks a developer's career and coding habits across sessions and calls out avoidance, procrastination and circling decisions. It pushes toward concrete action, celebrates shipped work briefly, and protects rest when the developer overdoes it.
№ 2EFE·D06F · Research analyst
★ 4Sets up a visual review agent that judges what is actually rendered, looking at occlusion, hierarchy, legibility, responsiveness, motion and state failures, and reports reproducible findings. It must never infer visual success from source code and must never edit project files.