Explore skills

Generate visual concepts and image prompts for profile banners, article headers, thumbnails, and wallpapers using current-state, desired-state, and transformation-mechanism storytelling.

Translate natural-language requests about modifying an AI coding agent, its skills, MCP tools, MCP servers, prompts, routing, tool descriptions, context loading, memory, portability, or other agentic behavior into the concrete mechanics of the target system. Use when a request is underspecified, phrased in human terms instead of runtime terms, or risks making the wrong change because the agent mus

Generate properly formatted Markdown from unstructured notes, scratch text, transcripts, or rough drafts. Use when the user wants content rewritten into cleaner Markdown without inventing new information.

Apply when producing any markdown artifact for someone else (or future-you) to read — READMEs, analysis documents, Confluence pages, status reports, troubleshooting write-ups, skill content, conversation summaries, ticket descriptions, post-mortems, snapshots of system state, or any document that contains concrete current-state values. Defines the "snapshot + reproducer" rule (every static value m

Core principles for technical communication such as commits, PR descriptions, branch names, and technical documentation. Use when writing or refining engineering-facing messaging and when other skills need a shared communication baseline.

Mandatory credential protection skill for all agents. Prevents reading, exposing, or leaking credentials, secrets, API keys, tokens, passwords, and auth-capable config files.

Analyze the current conversation or mine historical chat sessions for correction patterns, wrong conclusions, or unnecessary user intervention. Use when the user wants to improve prompts, skills, workflows, or guardrails based on repeated mistakes.

Guide for working through a Jira story efficiently by separating context gathering, immutable evidence collection, codebase exploration, human-in-the-loop specification refinement, execution planning, and implementation. Use when turning a ticket into a reliable engineering workflow instead of jumping straight to code.

Break down any concept, code, technology, or idea into a clear, layered explanation for adults who want the "aha moment" without the jargon. Produces a single self-contained HTML page with a concrete analogy, embedded CSS visual diagrams, layered detail, and curated links — then opens it in the browser. Use this skill whenever the user says "ELI5", "explain like I'm 5", "explain this simply", "bre

Use when comparing two versions of agent output to determine which is better, or when evaluating whether a skill produces higher quality results than baseline

Structured feedback session analyzing Claude Code usage over a configurable time window. Gathers evidence from git history, memory files, and project state, then delivers an honest 5/5/5 report (going well, not going well, what to improve) with specific evidence and trend tracking against previous sessions. Use when asked to "run feedback", "how am I doing", "feedback session", "usage review", "se

Run multiple skills on the same task in parallel and compare outputs side by side. A creative pitch room -- give it a brief, and it finds skills (local + trusted community repos) to work on it independently, then presents all outputs for comparison. Use when asked to "skill battle", "compare skills", "run multiple skills", "pitch room", "get different takes", "split test this", "give me options",