how
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.
How do I install this agent skill?
npx skills add https://github.com/ericlitman/open-pstack --skill howIs this agent skill safe to install?
- Gen Agent Trust Hubpass
This skill provides architectural walkthroughs and codebase exploration using a multi-agent system. It is designed with security best practices, including an enforced read-only mode for all file system operations. No malicious patterns, exfiltration attempts, or unauthorized execution vectors were detected.
- Socketpass
No alerts
- Snykpass
Risk: LOW · No issues
What does this agent skill do?
How
Explore the codebase to answer "how does X work?" questions. Produce architectural explanations at the level of a senior engineer onboarding onto a subsystem, enough to build a working mental model, not so much that it reads like annotated source code.
Dispatch contract. Resolve every configured role through provider-dispatch.md. Values are provider-qualified descriptors; the parent chooses native versus external execution. Every lane runs in read-only mode. Explorers use the how explorer descriptor, and every explainer uses the how explainer descriptor. When the sheet lacks either line, use that role's role default. A native lane uses the parent subagent primitive; an external lane uses the launcher directly. On Codex, resolve remaining Claude tool names via codex-tools.md. Pick each subagent's effort for the job, per the Subagents section of the poteto-mode skill.
1. Assess complexity
If the scope is ambiguous, state your interpretation and explore. The user can redirect.
- Simple (a single module, a small utility, a narrow question such as "how does function X work"): no explorers. Dispatch one explainer that explores and explains in one pass, built from
references/explainer-prompt.mdwithout the explorer-findings section. Go to step 4. - Complex (a subsystem spanning multiple files or services, a cross-cutting feature, a full architectural overview): go to step 2.
When in doubt, take the simple path.
2. Explore (complex only)
Decompose the question into 2 to 4 angles, each a distinct slice of the subsystem. Start all explorers in one fan-out phase, each with references/explorer-prompt.md and its angle filled in.
3. Synthesize (complex only)
Once all explorers have returned, dispatch one explainer with references/explainer-prompt.md and every explorer's findings filled in.
4. Present
Present the explainer's output. Light edits for clarity or context from the conversation are fine. Do not substantially rewrite it.
Output format
The explanation uses the sections defined in references/explainer-prompt.md, dropping any that do not apply: Overview, Key Concepts, How It Works, Where Things Live, Gotchas.
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/ericlitman/open-pstack/how">View how on skillZs</a>