Always-on CAPS emphasis skill for reasoning and planning. Use this skill whenever the user asks to highlight CRITICAL constraints, goals, deadlines, budgets, limits, or requirements in ALL CAPS, or asks for a PRIORITY REGISTER / ACTIVE PRIORITIES list across steps. Also trigger when prompts include words like must, never, always, critical, only, constraint, requirement, deadline, budget, limit, or ask to keep emphasis visible during multi-step planning, tool use, summaries, or final output.
Unified token-efficiency skill — ALWAYS ACTIVE by default on every response, even without any prompt from the user. Combines caveman ultra-compression, contraction-based natural compression, and terse PR code review. Also explicitly triggered when the user says "caveman mode", "talk like caveman", "use contractions", "be brief", "less tokens", "token efficient", "compress your replies", "review this PR", "code review", "/caveman", "/contract", "/review", or asks for any form of shorter / more efficient responses. Supports modes: contract, lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra, review.
Self-improving agent skill — ALWAYS ACTIVE on every task execution. After every task the agent observes, reflects, extracts patterns, scores them, generates skills, and registers them autonomously. Explicitly trigger when the user says "self-heal", "auto-skill", "learn from this", "create a skill for this", "add this to the skill library", "reflect on that", or asks the agent to improve itself. Also trigger when the agent detects it repeated the same multi-step sequence more than once, encountered a recoverable error, or spent significantly more tokens than the task's complexity warranted. Full spec: references/spec.md
Apply the blkst8 Go codebase style guide when generating, scaffolding, or reviewing Go code. ALWAYS use this skill when the user asks to create a new Go project or service, scaffold any Go code, add a handler / repository / service / model / worker / migration, set up HTTP routing with Echo, configure logging (zap) or database (sqlx / MySQL), wire dependencies, or structure a Go application — even if they don't explicitly mention the style guide. Also trigger when the user says "follow the style guide", "follow our Go conventions", "use our patterns", "how should I structure X in Go", or asks about private DI vs singleton in this codebase.