Jsnnmsc
UserExplain any technical concept to an idiot — decode errors, scope work, surface risk, and make decisions faster. In your language.
Categories
Indexed Skills (5)
risk
Surface the risks in a code change, architectural decision, or deployment — what could break, who gets affected, and what to test before shipping. Trigger when the user pastes a diff, describes a change, or says "what could go wrong", "is this safe to deploy", "review the risk", "what do I need to test". Output: risks + impact + test checklist + risk level. Under 15 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.
error
Decode any error message or stack trace — what broke, why, and how to fix it. Trigger when the user pastes an error, exception, stack trace, or says "what does this error mean", "why am I getting this", "fix this error". Output: what broke (1 sentence) + most likely cause + numbered fix steps. Under 10 lines.
why
Explain the reasoning behind a technical design decision — why it was built this way, what problem it solves, and what trade-off it accepts. Trigger when the user asks "why is X designed this way", "why does X work like this", "why not just do Y instead", "what's the point of X". Output: the short answer + the real reason + the trade-off accepted. Under 10 lines.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.