skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
painhardcore/pstack55 installs

how

Explain how a subsystem works, trace a runtime flow, or determine where code and ownership belong before making a change.

How do I install this agent skill?

npx skills add https://github.com/painhardcore/pstack --skill how
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    The 'how' skill uses subagents to explain codebase architecture. The primary security consideration is indirect prompt injection, as the agent processes untrusted code files that could contain malicious instructions.

  • 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. Use why when the user wants historical motivation.

Every spawn is a read-only subagent that inherits the parent model. When the host supports model selection, a fast model suits explorers and a judgment-focused model suits the explainer. Pick each subagent's reasoning level for the job, per the Subagents section of the poteto-mode skill. If subagents are unavailable or forbidden, do each step inline in the same order.

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. Spawn one explainer that explores and explains in one pass, built from references/explainer-prompt.md without 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, non-overlapping slice of the subsystem. Start all explorers concurrently, each with references/explorer-prompt.md and its angle filled in.

3. Synthesize (complex only)

Once all explorers have returned, spawn 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.

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/painhardcore/pstack/how">View how on skillZs</a>