From the author
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.
Install
npx skills add backnotprop/pstack --skill how -a claude-code
Installs to .claude/skills/how/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 90
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- whybacknotprop/pstackUse 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.DevOps★ 3K
- code-explanationDevelopersGlobal/ai-agent-skillsGet layered, context-aware explanations of unfamiliar code. Understand what it does, why it was written that way, and how to work with it safely.Engineering★ 216
- explainSerhiiKorniienko/bullshit-detectorExplain content or any concept inside it at the depth the user needs — ELI5, practitioner level, or expert deep-dive — with a jargon glossary and context the original assumes. Use when the user says "explain this", "what does X mean here", "break this down", "I don't understand this part", or shares content and asks how something in it works.Productivity★ 160
- planowainlewis/youtube-tutorialsWrite a short implementation plan or a longer execution plan before coding. Use when starting new work, when a ticket needs clearer boundaries, when a change spans multiple files or interfaces, or when a multi-hour task needs a living plan.Planning★ 410
- planningserejaris/personal-corp-osUse when a completed department retro should become accepted outcomes and a full living ISO-week plan, or the user asks "планирование", "план недели", or "что делаем на следующей неделе".Planning★ 238
- repo-onboardinghoangsonww/Claude-Code-Agent-MonitorOnboard quickly to this repository. Use when asked to understand architecture, locate ownership, choose the right module, or identify the correct commands and verification strategy before coding.Planning★ 1.1K
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in