Multi-persona deliberation framework for high-stakes decisions. Five specialized personas independently analyze a dilemma, blind-review each other's reasoning, and a Chairman synthesizes a single verdict. Use this skill whenever the user says 'council this', 'run the council on...', 'pressure-test this', 'war room this', 'stress-test this decision', 'red-team this', or asks for adversarial review of a choice. Also trigger when the user is weighing a high-cost, hard-to-reverse decision — architecture and tech selection, security tradeoffs, business pivots, pricing, hiring, major commitments — and would benefit from deliberately breaking their own assumptions before committing. When in doubt on a consequential or expensive decision, convene the council.
Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's comprehensive "Signs of AI writing" guide. Detects and fixes patterns including: inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, passive voice, negative parallelisms, and filler phrases. Scores each rewrite against a 0-100 rubric and loops until it clears threshold; matches a user-supplied voice sample via an extracted style profile when one is given.
Audits system-level prompts (system prompts, CLAUDE.md files, project instructions, custom style/preferences) against a curated directive library and surface-specific best practices, producing a scored gap report with ranked, copy-ready fixes. Use whenever the user invokes `/prompt-audit`, or asks to "audit," "review," "improve," "optimize," "critique," or "grade" a system prompt, CLAUDE.md, project instructions, custom instructions, agent instructions, or any persistent instruction set. Also trigger when a user pastes a system-level prompt and asks what's wrong with it or how to make it better, even without saying "audit." On request it also outputs a rewritten version with best practices applied — offer this when the user says "fix," "rewrite," "apply the changes," or wants the improved prompt itself. For persistent prompts, NOT one-off task prompts.
Prompt engineering skill that scores prompts against the KERNEL framework (Keep simple, Easy to verify, Reproducible, Narrow scope, Explicit constraints, Logical structure) using PASS/WEAK/FAIL ratings and rewrites them into the TICO-V output format (Task, Input, Constraints, Output, Verify). Classifies the input first (raw idea, draft prompt, system prompt, one-liner), explains every non-PASS rating, and chains complex requests into sequenced sub-prompts. Use when the user invokes `/kernel-angus`, `/ka`, or asks to improve, refine, or structure a prompt.
Structured context-gathering workflow that interviews the user before executing their prompt. Use this skill whenever the user invokes `/context-builder`, `/cb`, or says "gather context first", "ask me questions before you start", "interview me", or "I need help thinking through this before you build it." Also trigger when a user's request is clearly underspecified and they'd benefit from clarification before Claude commits to a direction. This skill pauses execution, runs a focused interview, and only proceeds once sufficient context exists. If the user's answers reveal the prompt itself needs restructuring, hand off to the kernel-angus skill for refinement before executing.