Jsnnmsc
UserExplain any technical concept to an idiot — decode errors, scope work, surface risk, and make decisions faster. In your language.
Categories
Indexed Skills (7)
3w
Break a possible adjustment or change down into Where, What, Why — where it applies, what actually changes, why it matters. Trigger when the user describes a possible tweak/adjustment and wants a quick breakdown, or says "3w", "where what why", "give me the 3w". Output: Where + What + Why. Under 8 lines.
catchup
Quick status brief so the user can pick up where things left off — what changed, what state it's in, what's next. Trigger when the user says "catch up", "catch me up", "where were we", "what's the status", "what's going on", or returns to a task/repo after a gap and wants an overview. Output: since last time / current state / next step. Under 12 lines. Grounded in actual git status/log/diff, not guesses.
decision
Surface the actual decision points in a task, plan, or problem — the specific choices that need to be made, the options for each, and a default recommendation. Trigger when the user wants decision points before diving in, or says "decision points", "what do I need to decide", "give me the decision points". Output: numbered decision points, each with options and a recommendation. Under 10 lines.
impact
Surface the blast radius of a change — which modules, services, users, or data get touched, directly or downstream. Trigger when the user asks "what does this affect", "blast radius", "who gets touched by this", "impact of this change", or pastes a change and wants to know what depends on it. Output: directly affected + downstream affected + who notices. Under 10 lines.
scope
Turn a vague feature request or task description into a clear scope — what's in, what's out, what's unknown, and how big it is. Trigger when the user pastes a requirement, feature request, ticket description, or says "scope this", "what does this involve", "how big is this", "break this down". Output: in scope / out of scope / unknowns / complexity estimate. Under 15 lines.
tldr
Quick plain-language brief — skip the explanation, get the point. Use when the user says "tldr", "quick version", "what is X", "should I use X", "just tell me", "give me the short version", or is clearly in a hurry. Output adapts to the question: - Pure definition ("what is X") → 1 sentence + 1-2 key facts - Decision / comparison ("should I use X", "X vs Y") → 1 sentence + use when / skip when / bottom line Max 5 lines. No diagrams. No analogies. No history. Direct verdict.
tradeoff
Quick A-vs-B comparison for a technical choice — what each option costs, what it buys, and which one to pick. Trigger when the user asks "X vs Y", "should I use X or Y", "which is better here", "what's the tradeoff between X and Y". Output: cost/benefit for each option + pick. Under 10 lines.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.