Why
Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.
Install
npx skills add Dimon94/skills --skill whygit clone --depth 1 https://github.com/Dimon94/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/skills/why ~/.claude/skills/whyPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Why Investigate the motivation and intent behind code. Companion to the `how` skill. `how` answers what the code does and how it works. `why` answers what forces led to its shape. Spawn subagents in the current runtime's native way. When the runtime accepts an explicit model per spawn, set it by role tier; a model the user explicitly chose always wins over this table. If the runtime cannot resolve a tier to a concrete model, leave model unset and continue — never block on it. - investigators: fast tier. The cheapest adequate general model in the current runtime. - synthesizer: strong tier. The strongest reasoning model available. ## Operating Posture Operate as a **careful, cautious, and precise investigator**. Be honest about what you know vs what you're inferring. Read `references/epistemics.md` for the full confidence framework and phrasing guide. The synthesizer must follow it. ## Step 1. Understand the Target and the Question Parse what the user is asking. The **target** is usually a chunk of code, a pattern, a feature, or a named design decision. The **question** is usually a design rationale, a tradeoff, a motivating edge case, an external constraint, dead code, or a broad history sweep.
Details
- Skill name
why- Repository
- Dimon94/skills
- Path
skills/why/SKILL.md- Repo updated
- 18 November 2026
- Copies
- Found in 3 GitHub repos
FAQ
What does the Why skill do?
Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.
How do I install the Why skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add Dimon94/skills --skill why. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Why popular?
It lives in Dimon94/skills, which has 107 GitHub stars and 21 forks, and is included in 2 curated skill lists.
Related skills
Maintain Verification Skill
107Dimon94/skills
Periodic pass that keeps a project's verification skill and feature map honest: parallel source readers per feature, one live session driving every feature, at most one PR of proven corrections. Use for /maintain-verification-skill or "audit the verify skill".
Create Verification Skill
107Dimon94/skills
Generate a project-local verification skill that drives your app the way a user does — any language, framework, or platform. Use for /create-verification-skill, "make a control skill for this repo", or when a project has no scripted way to prove UI/CLI/service behavior.
How
107Dimon94/skills
Use for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions ("where should this live", "which package owns this", "is this the right layer"). Explains subsystem architecture, runtime flow, onboarding mental models. Use why for motivation.
Oneshot Website
260cafe3310/public-agent-skills
Generate immersive, one-shot single-file HTML websites with embedded CSS and JS. No external images. Hostable on CodePen or Vercel. Use for writeup showcases, AI capability demos, and portfolio pieces.
Linux Perf
293mohitmishra786/low-level-dev-skills
Linux perf profiler skill for CPU performance analysis. Use when collecting sampling profiles with perf record, generating perf report, measuring hardware counters (cache misses, branch mispredicts, IPC), identifying hot functions, or feeding perf data into flamegraph tools. Activates on queries about perf, Linux performance counters, PMU events, off-CPU profiling, perf stat, perf annotate, or sampling-based profiling on Linux.
S4h Cognition Metacognition
242human-avatar/skills-for-humanity
Applies thinking-about-thinking as a practical tool — monitoring comprehension, calibrating confidence, and knowing what you do not know. Use when asked 'how confident should I be about this', 'am I actually understanding this or just recognising it', 'what do I not know that I should know', 'I think I understand this but I keep getting it wrong', 'calibrate my confidence', or when the quality of reasoning on a complex problem needs to be assessed from the outside.
Browse the most popular Claude skills, all devops & cloud skills, or write your own with the skills generator.