[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78D1MGNAGGBSVBGA5MJNECZ":3,"skill-same:01M78D1MGNAGGBSVBGA5MJNECZ":68},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M78D1MGNAGGBSVBGA5MJNECZ","how",null,"Use for \"how does X work\", code walkthroughs before changing something, and placement \u002F ownership \u002F layering questions (\"where should this live\", \"which package owns this\", \"is this the right layer\"). Explains subsystem architecture, runtime flow, onboarding mental models. Can critique architecture. Use why for motivation.","emo-eth\u002Fskills","emo-eth","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6371847?v=4","01M78CWE28WS3JH2WXYPRNC26K","James","01M78CWE2YS6Y5883W8J0D60XA",0,"MIT","https:\u002F\u002Fgithub.com\u002Femo-eth\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Fhow\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Femo-eth\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Fhow\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: how\ndescription: \"Use for \\\"how does X work\\\", code walkthroughs before changing something, and placement \u002F ownership \u002F layering questions (\\\"where should this live\\\", \\\"which package owns this\\\", \\\"is this the right layer\\\"). Explains subsystem architecture, runtime flow, onboarding mental models. Can critique architecture. Use why for motivation.\"\n---\n\n# How\n\nRead `pstack-runtime` before the first host-specific operation.\n\nExplore the codebase to answer \"how does X work?\" questions. Produce clear architectural explanations at the level of a senior engineer onboarding onto a subsystem. Enough to build a working mental model, not annotated source code.\n\nTwo modes:\n\n1. **Explain** (default). Explore the codebase and produce a clear explanation\n2. **Critique.** Explain first, then spawn independent reviewers through the current host.\n\n## Explain Mode\n\n### Step 1. Understand the Question and Assess Complexity\n\nParse what the user is asking about:\n\n- \"How does the rate limiter work?\", a subsystem\n- \"How do we handle billing for on-demand usage?\", a feature flow\n- \"How is the auth service structured?\", an architectural overview\n- \"Walk me through what happens when a user submits a form\", a runtime trace\n\nIdentify the scope. If ambiguous, state your best-guess interpretation before exploring. Don't ask. Let the user redirect if you're off.\n\n**Assess complexity to decide the approach:**\n\n- **Simple** (a single module, a small utility, a narrow question like \"how does function X work\"): skip explorer agents; the explainer explores and explains in a single pass. Go to Step 2b.\n- **Complex** (a subsystem spanning multiple files\u002Fservices, a cross-cutting feature, a full architectural overview): spawn parallel explorer agents first, then hand off to the explainer. Go to Step 2a.\n\nWhen in doubt, lean simple. You can always spawn explorers if the explainer hits a wall.\n\n### Step 2a. Explore (complex questions only)\n\nDecompose the question into 2-4 parallel exploration angles, each a distinct slice of the subsystem so explorers don't duplicate work. Example split for \"how does the rate limiter work?\":\n\n- Explorer 1: data model and state management\n- Explorer 2: request path and enforcement\n- Explorer 3: configuration and metrics infrastructure\n\nThe right decomposition depends on the question. Use your judgment. Narrow questions: 2 explorers is fine. Broad subsystems: up to 4.\n\nRead `~\u002F.config\u002Fpstack\u002Fomp-agents.json` when it exists. Spawn every explorer in one OMP `task` batch. Use the configured `how-explorer` type, or `scout` by default. Explorer tasks are read-only and must use the `scout` contract.\nEach explorer gets the same base prompt from `references\u002Fexplorer-prompt.md` plus a specific exploration angle naming its slice. Each explorer should:\n- Start broad with `glob` for relevant directories and `grep` for key types, interfaces, and names\n- Follow symbols with `lsp` references and definitions when a language server is available; otherwise trace callers, callees, data flow, and type definitions from source\n- Read the actual code instead of guessing from file names\n- Stop when it can describe the full path from input to output, or trigger to effect, without hand-waving a step\n- Note surprising or non-obvious behavior that a newcomer could get wrong\n\nEach explorer returns structured findings: components found, flow traced, files read, anything non-obvious. Overlap between explorers is fine; the explainer reconciles.\n\nThen proceed to Step 3.\n\n### Step 2b. Direct Explain (simple questions)\n\nSpawn one read-only `scout` task that explores and explains in one pass. Use the configured `how-explainer` type only when it is a read-only research agent available in the current OMP roster.\n\nThe agent does its own exploration with `glob`, `grep`, `read`, and `lsp`, then writes the explanation directly. Read `references\u002Fexplainer-prompt.md` for the communication style and output format. Use the same structure with no explorer findings as input.\n\nProceed to Step 4.\n\n### Step 3. Synthesize (complex questions only)\n\nAfter all explorers return, spawn one synthesis task. Use the configured `how-explainer` type, or `scout` by default. Pass the explorer results by `local:\u002F\u002F` artifact when they are large instead of inlining raw output.\n\nThe explainer writes the human-facing explanation. Read `references\u002Fexplainer-prompt.md` for the full prompt template. It reconciles overlap, resolves contradictions against cited source, and joins the slices into one model.\n\n### Step 4. Present\n\nPresent the explainer's output to the user. You may lightly edit for clarity or add context from the conversation, but don't substantially rewrite. The explainer's communication is the product.\n\n### Output Format\n\nFollow this structure, adapted to the question. Not every section is needed for every question.\n\n**Overview.** 1-2 paragraphs. What it is, what it does, why it exists. Enough to decide whether to keep reading.\n\n**Key Concepts.** The important types, services, or abstractions. Brief definition of each. Not exhaustive, just the ones needed to understand the rest.\n\n**How It Works.** The core of the explanation. Walk through the flow: what triggers it, what happens step by step, where data goes, the decision points. Prose, not pseudocode. Reference specific files and functions so the reader can go look, but don't dump code blocks unless a snippet is genuinely necessary.\n\n**Where Things Live.** A brief map of the relevant files\u002Fdirectories. Not every file, just the ones needed to start working in this area.\n\n**Gotchas.** Non-obvious or surprising things that would trip someone up. Historical context that explains why something looks weird. Known sharp edges.\n\n## Critique Mode\n\nTriggered when the user asks for architectural issues, problems, or improvements, not just understanding.\n\n### Step 1. Explain First\n\nRun the full explain flow above (Steps 1-4). You must understand the architecture before critiquing it.\n\n### Step 2. Spawn Critics\n\nAfter the explanation is complete, read the `how-critics` list from `~\u002F.config\u002Fpstack\u002Fomp-agents.json` when present. Otherwise use two `reviewer` tasks. Spawn all critics in one OMP `task` batch. Every critic is read-only.\n\nOMP agent types can use the same underlying model. Treat this as independent review, not guaranteed model-family diversity. A missing configured type falls back to `reviewer`.\n\nRead `references\u002Fcritic-prompt.md` for the prompt template. Each critic gets:\n1. The explanation from Step 1 (so they don't re-explore)\n2. The relevant file paths (so they can read the actual code)\n3. The architectural critique rubric from `references\u002Fcritique-rubric.md`\n\n### Step 3. Lead Judgment\n\nSame framework as the interrogate skill. You're a pragmatic lead, not an aggregator.\n\nCategorize findings:\n- **Act on.** Architectural problems worth fixing now\n- **Consider.** Real concerns, but the cost\u002Fbenefit is unclear\n- **Noted.** Valid observations, low priority\n- **Dismissed.** Wrong, missing context, or style preference\n\nPresent the explanation first (from Step 1), then the critique verdict below it. The explanation should stand on its own; someone who just wants to understand the system shouldn't wade through critique.\n","# How\n\nRead `pstack-runtime` before the first host-specific operation.\n\nExplore the codebase to answer \"how does X work?\" questions. Produce clear architectural explanations at the level of a senior engineer onboarding onto a subsystem. Enough to build a working mental model, not annotated source code.\n\nTwo modes:\n\n1. **Explain** (default). Explore the codebase and produce a clear explanation\n2. **Critique.** Explain first, then spawn independent reviewers through the current host.\n\n## Explain Mode\n\n### Step 1. Understand the Question and Assess Complexity\n\nParse what the user is asking about:\n\n- \"How does the rate limiter work?\", a subsystem\n- \"How do we handle billing for on-demand usage?\", a feature flow\n- \"How is the auth service structured?\", an architectural overview\n- \"Walk me through what happens when a user submits a form\", a runtime trace\n\nIdentify the scope. If ambiguous, state your best-guess interpretation before exploring. Don't ask. Let the user redirect if you're off.\n\n**Assess complexity to decide the approach:**\n\n- **Simple** (a single module, a small utility, a narrow question like \"how does function X work\"): skip explorer agents; the explainer explores and explains in a single pass. Go to Step 2b.\n- **Complex** (a subsystem spanning multiple files\u002Fservices, a cross-cutting feature, a full architectural overview): spawn parallel explorer agents first, then hand off to the explainer. Go to Step 2a.\n\nWhen in doubt, lean simple. You can always spawn explorers if the explainer hits a wall.\n\n### Step 2a. Explore (complex questions only)\n\nDecompose the question into 2-4 parallel exploration angles, each a distinct slice of the subsystem so explorers don't duplicate work. Example split for \"how does the rate limiter work?\":\n\n- Explorer 1: data model and state management\n- Explorer 2: request path and enforcement\n- Explorer 3: configuration and metrics infrastructure\n\nThe right decomposition depends on the question. Use your judgment. Narrow questions: 2 explorers is fine. Broad subsystems: up to 4.\n\nRead `~\u002F.config\u002Fpstack\u002Fomp-agents.json` when it exists. Spawn every explorer in one OMP `task` batch. Use the configured `how-explorer` type, or `scout` by default. Explorer tasks are read-only and must use the `scout` contract.\nEach explorer gets the same base prompt from `references\u002Fexplorer-prompt.md` plus a specific exploration angle naming its slice. Each explorer should:\n- Start broad with `glob` for relevant directories and `grep` for key types, interfaces, and names\n- Follow symbols with `lsp` references and definitions when a language server is available; otherwise trace callers, callees, data flow, and type definitions from source\n- Read the actual code instead of guessing from file names\n- Stop when it can describe the full path from input to output, or trigger to effect, without hand-waving a step\n- Note surprising or non-obvious behavior that a newcomer could get wrong\n\nEach explorer returns structured findings: components found, flow traced, files read, anything non-obvious. Overlap between explorers is fine; the explainer reconciles.\n\nThen proceed to Step 3.\n\n### Step 2b. Direct Explain (simple questions)\n\nSpawn one read-only `scout` task that explores and explains in one pass. Use the configured `how-explainer` type only when it is a read-only research agent available in the current OMP roster.\n\nThe agent does its own exploration with `glob`, `grep`, `read`, and `lsp`, then writes the explanation directly. Read `references\u002Fexplainer-prompt.md` for the communication style and output format. Use the same structure with no explorer findings as input.\n\nProceed to Step 4.\n\n### Step 3. Synthesize (complex questions only)\n\nAfter all explorers return, spawn one synthesis task. Use the configured `how-explainer` type, or `scout` by default. Pass the explorer results by `local:\u002F\u002F` artifact when they are large instead of inlining raw output.\n\nThe explainer writes the human-facing explanation. Read `references\u002Fexplainer-prompt.md` for the full prompt template. It reconciles overlap, resolves contradictions against cited source, and joins the slices into one model.\n\n### Step 4. Present\n\nPresent the explainer's output to the user. You may lightly edit for clarity or add context from the conversation, but don't substantially rewrite. The explainer's communication is the product.\n\n### Output Format\n\nFollow this structure, adapted to the question. Not every section is needed for every question.\n\n**Overview.** 1-2 paragraphs. What it is, what it does, why it exists. Enough to decide whether to keep reading.\n\n**Key Concepts.** The important types, services, or abstractions. Brief definition of each. Not exhaustive, just the ones needed to understand the rest.\n\n**How It Works.** The core of the explanation. Walk through the flow: what triggers it, what happens step by step, where data goes, the decision points. Prose, not pseudocode. Reference specific files and functions so the reader can go look, but don't dump code blocks unless a snippet is genuinely necessary.\n\n**Where Things Live.** A brief map of the relevant files\u002Fdirectories. Not every file, just the ones needed to start working in this area.\n\n**Gotchas.** Non-obvious or surprising things that would trip someone up. Historical context that explains why something looks weird. Known sharp edges.\n\n## Critique Mode\n\nTriggered when the user asks for architectural issues, problems, or improvements, not just understanding.\n\n### Step 1. Explain First\n\nRun the full explain flow above (Steps 1-4). You must understand the architecture before critiquing it.\n\n### Step 2. Spawn Critics\n\nAfter the explanation is complete, read the `how-critics` list from `~\u002F.config\u002Fpstack\u002Fomp-agents.json` when present. Otherwise use two `reviewer` tasks. Spawn all critics in one OMP `task` batch. Every critic is read-only.\n\nOMP agent types can use the same underlying model. Treat this as independent review, not guaranteed model-family diversity. A missing configured type falls back to `reviewer`.\n\nRead `references\u002Fcritic-prompt.md` for the prompt template. Each critic gets:\n1. The explanation from Step 1 (so they don't re-explore)\n2. The relevant file paths (so they can read the actual code)\n3. The architectural critique rubric from `references\u002Fcritique-rubric.md`\n\n### Step 3. Lead Judgment\n\nSame framework as the interrogate skill. You're a pragmatic lead, not an aggregator.\n\nCategorize findings:\n- **Act on.** Architectural problems worth fixing now\n- **Consider.** Real concerns, but the cost\u002Fbenefit is unclear\n- **Noted.** Valid observations, low priority\n- **Dismissed.** Wrong, missing context, or style preference\n\nPresent the explanation first (from Step 1), then the critique verdict below it. The explanation should stand on its own; someone who just wants to understand the system shouldn't wade through critique.\n",{"name":5,"description":7},"main","556c6b2a01f1f75137a940333ffc8bd95cf0756e","skills\u002Fpstack\u002Fhow","https:\u002F\u002Fgithub.com\u002Femo-eth\u002Fskills","https:\u002F\u002Fgithub.com\u002Femo-eth","I make music and write code","2026-11-13 05:13:04",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add emo-eth\u002Fskills --skill how",{"tool":38,"command":39},"bunx","bunx skills add emo-eth\u002Fskills --skill how",{"tool":41,"command":42},"pnpm","pnpm dlx skills add emo-eth\u002Fskills --skill how","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Femo-eth\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Fhow\u002FSKILL.md",true,[46,50,56,60,64],{"path":47,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":16},"LICENSE","许可证",1067,{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Fcritic-prompt.md","REFERENCE","参考文档",2286,"https:\u002F\u002Fgithub.com\u002Femo-eth\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Fhow\u002Freferences\u002Fcritic-prompt.md",{"path":57,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":58,"sourceHtmlUrl":59},"references\u002Fcritique-rubric.md",2877,"https:\u002F\u002Fgithub.com\u002Femo-eth\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Fhow\u002Freferences\u002Fcritique-rubric.md",{"path":61,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":62,"sourceHtmlUrl":63},"references\u002Fexplainer-prompt.md",3063,"https:\u002F\u002Fgithub.com\u002Femo-eth\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Fhow\u002Freferences\u002Fexplainer-prompt.md",{"path":65,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":66,"sourceHtmlUrl":67},"references\u002Fexplorer-prompt.md",2670,"https:\u002F\u002Fgithub.com\u002Femo-eth\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Fhow\u002Freferences\u002Fexplorer-prompt.md",[69,76,84,92,100,108],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":20},"01M78D75SMNM5JJXJGN9W6Z304","system-vibe","Personal operating-system contract for the home fleet, sync, SSH, skills, Herdr, and local inference. Use when diagnosing or changing machines, chezmoi, SSH, skill distribution, Windows sleep\u002Fwake, or the local model router. This is the qualitative list of what must stay true; agents invent enforcement from the clauses, not from tribal setup lore.","https:\u002F\u002Fgithub.com\u002Femo-eth\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fsystem-vibe\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":80,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":20},"01M78D65Z8HK3VTSAWKC59TR94","rubber-stamp-travel-field-note","Use for rubber-stamp travel field-note photo posters.","CC-BY-4.0","https:\u002F\u002Fgithub.com\u002Femo-eth\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Frubber-stamp-travel-field-note\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":88,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":20},"01M78D5VXYSJZVTGETSYGZWQPQ","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.","https:\u002F\u002Fgithub.com\u002Femo-eth\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Fwhy\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Femo-eth\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Fwhy\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":96,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":20},"01M78D5SMN2NTGT19B2T5WY83T","unslop","Cut AI tells from any writing. Must always apply.","https:\u002F\u002Fgithub.com\u002Femo-eth\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Funslop\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Femo-eth\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Funslop\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":104,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":20},"01M78D5PN73KA6B88JVHABNTKY","typescript-best-practices","TypeScript best practices. Use when reading or editing any .ts or .tsx file.","https:\u002F\u002Fgithub.com\u002Femo-eth\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Ftypescript-best-practices\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Femo-eth\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Ftypescript-best-practices\u002FSKILL.md",[],[],{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":112,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":20},"01M78D5JHTG4B6YPZ8TNN18Y6D","technical-writing","Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for \u002Ftechnical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.","https:\u002F\u002Fgithub.com\u002Femo-eth\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Ftechnical-writing\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Femo-eth\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fpstack\u002Ftechnical-writing\u002FSKILL.md",[],[]]