bwitlin

@bwitlin source repo

3 skills
0 followers
11 hours ago last updated

▌
Eli5 · bwitlin
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", "break this down for me", "what even is [X]?", "help me understand [X]", "dumb it down", "in plain English", or otherwise signals they want a radically simplified explanation of something — even if they don't use the exact phrase "ELI5." Also trigger when a user is clearly confused by a concept in their codebase or conversation and asks "what is this?" or "I don't get this." If someone pastes code or references a file and asks for a simple explanation, this skill owns that.

0
installs
▌
Feedback · bwitlin
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", "self-assessment", "critique my workflow", or any request for an honest evaluation of how the user is using Claude Code. Proactively suggest after completing a multi-day sprint or when the user seems frustrated with their workflow. Always use this skill instead of doing ad-hoc feedback analysis in main chat.

0
installs
▌
Skill Battle · bwitlin
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", or any request to see how different skills handle the same task. Great for generating variants for split testing -- headlines, email copy, ad creative. Best for subjective work where different perspectives add real value. Not useful for tasks with one right answer (bug fixes, migrations, config changes). Always use this skill instead of manually running skills one at a time when the user wants to compare outputs.

0
installs

3 published skills