wuisabel-gif
UserCatches writing that sounds robotic. Shows you why, then rewrites it in a voice that sounds like you.
Categories
Indexed Skills (6)
cadence
Use when the user wants to write, draft, rewrite, edit, or improve prose that sounds human instead of AI-generated — essays, posts, landing copy, emails, docs, scripts, newsletters, threads. Learns a reusable "voice" from a sample the user provides (a book, an article, their own past writing) and writes in it. Strips AI tone: hollow-confidence words, uniform sentence rhythm, triadic lists, negation-pivot clichés, throat-clearing openers. Use for "make this sound less like AI," "write this in the voice of X," "match my tone," "de-slop this draft," or building a library of tones to choose from. Not for code, data, or visual/UI design.
memorywhale
Query and write durable debugging memory recorded by MemoryWhale. Use when debugging a failure that may have happened before, when you need the exact error/flags/output from an earlier attempt, when the user asks "how did we fix this last time?", or once you've figured out why something failed / how a fix worked and it's worth remembering. Works across machines and past sessions.
the-pass
Ship-or-don't review against a fixed standard. Returns work with one line per defect: location, what is wrong, what fixes it. Ends on a verdict, never a summary. Use when the user says "the pass", "/the-pass", "is this good enough", "brutal feedback", "tear this apart", "review before I ship", or asks whether something is ready. Complements correctness review, this one only calls ship or don't. Do NOT use when the user wants help building something, only when something already exists to judge.
canon
Build a personal library of engineering practice by mining how maintainers actually run repos over time, then write from it. Use when the user wants to learn from a codebase rather than contribute to one, wants to study several projects, is deciding their own conventions, or says "canon" or "/canon". Do NOT use when matching a single maintainer to get a PR merged, that is with-the-grain.
precedent
Read a whole repo as case law: what its CI mechanically rejects, how its reviewers resolved problems when they hit, which conventions it adopted and later overruled. Then work inside those rulings instead of reopening them. Use when the user inherits an unfamiliar codebase, asks how this repo does something or why a convention exists, wants to know whether a change will survive review, or says "precedent" or "/precedent". Do NOT use to imitate one maintainer's voice for a merge, that is with-the-grain, or to build a library across many repos, that is canon.
with-the-grain
Profile how a repo's maintainer works, then contribute in their idiom. Use when the user is about to write something that goes back to a repo they don't own: opening a PR, writing a commit for an upstream project, or asking to match a maintainer's conventions so a change gets merged. Do NOT use to understand an inherited codebase or find out why a convention exists, that is precedent, and do NOT use to build practice across several repos, that is canon.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.