[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EREMHJS9JY10AM5EKVX3GP":3,"skill-same:01M7EREMHJS9JY10AM5EKVX3GP":106},{"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":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7EREMHJS9JY10AM5EKVX3GP","why",null,"Find why code is the way it is, from its history and every evidence source this session can query, with citations. Use for 'why does X work this way', 'why did we pick Y', regressions and postmortems. Use how for runtime behavior.","JoshuaHayesWasHere\u002Fjstack","JoshuaHayesWasHere","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F78288453?v=4","01M7EQPZP0GDYN3SYY9SZZHFJE","Joshua Hayes","01M7EQPZPQKJDZR99NG512A8X2",1,"MIT","https:\u002F\u002Fgithub.com\u002FJoshuaHayesWasHere\u002Fjstack\u002Fblob\u002Fmain\u002Ffeatures\u002Fwhy\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: why\ndescription: \"Find why code is the way it is, from its history and every evidence source this session can query, with citations. Use for 'why does X work this way', 'why did we pick Y', regressions and postmortems. Use how for runtime behavior.\"\ntip: finds why the code is the way it is, with cited evidence | why does * work this way | why did we pick | why did we choose | design rationale | postmortem | post mortem\ncard: \"Understand what is there | 2 | Explains why something was built this way, with a cited read of the decisions and tradeoffs from source control, issues and docs. | Reach for it when you need the rationale, or are looking into a regression. | op: the operator; plain: a step of `architect`\"\n---\n\n# Why\n\nSource: pstack, `pstack\u002Fskills\u002Fwhy\u002FSKILL.md`\n\nInvestigate the motivation and intent behind code. The companion `how` skill answers what the code does and how it works. `why` answers what forces led to its shape.\n\nEvery spawn below is one call of the `Agent` tool (or, with no subagent tool, do it in this thread, working from the same prompt), this one with `prompt` set to the prompt built from its template:\n\n```json\n{\n  \"subagent_type\": \"Explore\",\n  \"description\": \"why investigator\",\n  \"prompt\": \"The prompt, built from its template.\",\n  \"run_in_background\": false\n}\n```\n\nThe type is `Explore`: it is started with no Edit, Write or NotebookEdit tool and keeps this session's MCP tools, which the MCP-backed investigators and the synthesizer's citation spot-checks need. It runs on this session's model at this session's effort. No `model`, no `effort` and no `isolation`, for an investigator or the synthesizer: there is no model per role here. The synthesizer's call is the same with the description `why synthesizer`.\n\nA step starts at most ten subagents. The seven categories below are the most this skill starts at once.\n\nThe templates and the source playbooks are beside this file, in `references\u002F`.\n\n## Operating Posture\n\nOperate as a **careful, cautious, and precise investigator**. Be honest about what you know vs what you're inferring. Read `references\u002Fepistemics.md` for the full confidence framework and phrasing guide. The synthesizer must follow it.\n\n## Step 1. Understand the Target and the Question\n\nThe **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.\n\nIf the target is vague (\"why do we do it this way?\" with no clear referent), make your best guess from conversation context (open files, recent edits, what was just discussed). State your interpretation briefly so the user can redirect if you're off, then proceed.\n\n## Step 2. Establish the Code Anchor\n\nBefore spawning investigators, build the seed context inline: file paths and line ranges, key symbols (functions, classes, constants), the last few commits touching the target, PR numbers from merge commits (pattern `(#1234)` in the subject line), and any linked ticket IDs. Run `git blame -L \u003Cstart>,\u003Cend> \u003Cfile>` for last-touch commits, `git log --follow -p -- \u003Cfile>` for full history with patches through renames, `git log --oneline -20 -- \u003Cfile>` for recent commits with PR numbers visible, and `git log -1 --format=%B \u003Ccommit>` to extract PR numbers. Then pull the PR bodies and discussion for any substantive commit: `gh pr view \u003Cnumber> --json title,body,author,createdAt,mergedAt,labels,closingIssuesReferences,comments,reviews`. This anchor goes to every investigator and to the synthesizer.\n\n## Step 3. Spawn Parallel Investigators\n\n**Default to the full parallel investigation.** The goal is a complete coverage map, not a minimal one. Document the null, don't skip the search.\n\n### Discovery\n\nBefore spawning investigators, list the MCP servers this session has. Claude Code names their tools `mcp__\u003Cserver>__\u003Ctool>`, and another harness by its own rule. If your harness defers a tool, load it first: in Claude Code, with ToolSearch. A server that still needs authorizing is not available: say so in the coverage map, and do not ask the user for a token.\n\nMap each available MCP to one evidence category:\n\n1. Source control history\n2. Issue \u002F ticket tracker\n3. Long-form documents\n4. Real-time team chat\n5. Infrastructure observability\n6. Error \u002F exception tracking\n7. Product analytics warehouse\n\nSource control is always available through git and `gh`. For the other six, classify using the MCP name, server instructions, tool names, and resource descriptors. If an MCP could fit more than one category, choose the one matching its primary evidence. Record ambiguous cases in the coverage map.\n\nSpawn one investigator per category that has a matching MCP, all in a single message so they run concurrently, each owning exactly one tool or MCP. Don't ask one agent to cover multiple MCPs.\n\nEach investigator's prompt is `references\u002Finvestigator-prompt.md` filled in, plus:\n- the category playbook `references\u002Fsources\u002F\u003Csource>.md` for the selected MCP, adapted from the examples in `references\u002Fsource-playbook.md`\n- `references\u002Fsources\u002Fincident-postmortem.md` **if the target code looks defensive** (null checks, retry logic, timeout handling, rate limiting, feature flags, egress guards, OOM handlers)\n- the code anchor and the user's original question\n\n### Investigator roster, one per available evidence category\n\nEach category below is uniquely positioned to surface one shape of \"why\", shown after \"Best at\". Use it to know what to expect back, to name a gap when a category returns empty, and, only in the rare provably-irrelevant case, to justify a skip.\n\n1. **Source control** (git history, `gh` for PRs, code comments, tests). Always spawn, the only guaranteed source. Best at *implementation-time rationale captured during review*.\n2. **Issue \u002F ticket tracker** (e.g. Linear, Jira, GitHub Issues, Plane, Shortcut MCP). Best at *the product or business forcing function*. Strongest when the why is external to engineering.\n3. **Long-form documents** (e.g. Notion, Confluence, Google Docs, Coda MCP). Best at *long-form design rationale*, written out before it becomes code.\n4. **Real-time team chat** (e.g. Slack, Discord, Microsoft Teams, Mattermost MCP). Best at *real-time deliberation that never reached a doc*. Especially important when the source control, ticket, and doc paper trail is thin.\n5. **Infrastructure observability** (e.g. Datadog, New Relic, Honeycomb, Grafana, Splunk MCP). Best at *infrastructure and runtime reality that motivated the code*. Strongest when the target reacts to an infra signal (timeouts, retries, rate limits, circuit breakers).\n6. **Error \u002F exception tracking** (e.g. Sentry, Rollbar, Bugsnag, Airbrake MCP). Best at *the specific exceptions and error trajectories that motivated defensive or corrective code*. Strongest for catch blocks, null guards, type checks, retries, and other defenses.\n7. **Product analytics warehouse** (e.g. Databricks, Snowflake, BigQuery, ClickHouse, dbt, Redshift MCP). Best at *product and data reality that shaped the code*. Strongest for flag-gated code, experiment-driven ships, data migrations, and \"where did this number come from\" questions.\n\n### When to skip an investigator\n\nOnly with an **explicit, written justification** that goes in the final Sources Consulted. Two valid reasons:\n\n- **No MCP is available for that category** in this environment. Flag it as a gap, not a choice: \"Real-time team chat skipped. No matching MCP available, so the conversational record was not searchable.\"\n- **The source is provably irrelevant**, not just \"probably irrelevant.\" A high bar: \"Error \u002F exception tracking skipped. Target is a build-time script with no runtime code path.\"\n\nIf your scope assessment suggests a single-commit trivial target where the PR description already contains the complete answer, you may answer inline **only after** confirming all seven available category searches would be redundant. Say so explicitly. This should be rare.\n\n## Step 4. Synthesize\n\nSpawn one synthesizer. It gets:\n1. The investigator findings, including any null results and any categories skipped with justification\n2. The code anchor\n3. The user's original question\n4. The epistemics framework from `references\u002Fepistemics.md`\n5. The synthesizer prompt template from `references\u002Fsynthesizer-prompt.md`\n\n## Step 5. Present\n\nPresent the synthesizer's output to the user. You may lightly edit for clarity or add context from the conversation, but **do not rewrite the confidence language**.\n\n## Output Format\n\nThe structure is the one in `references\u002Fsynthesizer-prompt.md`: The Question, The Code in Question, What We Found, What We Can Reasonably Infer, Competing Hypotheses, What We Don't Know, Sources Consulted, Confidence Summary. Adapt as needed, but keep the confidence separation intact, and keep Sources Consulted as one line per investigator, including the ones that returned nothing or were skipped, with the reason.\n\nAfter Sources Consulted, if the user's `why` question is a precursor to changing this code, convert the lineage findings into a Preserve \u002F Change \u002F Avoid \u002F Risk constraint set for planning the change.\n\n## Common Failure Modes to Avoid\n\n- **Recency bias**. Assuming the most recent commit is authoritative. The current shape is often the accretion of many earlier decisions. Trace back.\n","# Why\n\nSource: pstack, `pstack\u002Fskills\u002Fwhy\u002FSKILL.md`\n\nInvestigate the motivation and intent behind code. The companion `how` skill answers what the code does and how it works. `why` answers what forces led to its shape.\n\nEvery spawn below is one call of the `Agent` tool (or, with no subagent tool, do it in this thread, working from the same prompt), this one with `prompt` set to the prompt built from its template:\n\n```json\n{\n  \"subagent_type\": \"Explore\",\n  \"description\": \"why investigator\",\n  \"prompt\": \"The prompt, built from its template.\",\n  \"run_in_background\": false\n}\n```\n\nThe type is `Explore`: it is started with no Edit, Write or NotebookEdit tool and keeps this session's MCP tools, which the MCP-backed investigators and the synthesizer's citation spot-checks need. It runs on this session's model at this session's effort. No `model`, no `effort` and no `isolation`, for an investigator or the synthesizer: there is no model per role here. The synthesizer's call is the same with the description `why synthesizer`.\n\nA step starts at most ten subagents. The seven categories below are the most this skill starts at once.\n\nThe templates and the source playbooks are beside this file, in `references\u002F`.\n\n## Operating Posture\n\nOperate as a **careful, cautious, and precise investigator**. Be honest about what you know vs what you're inferring. Read `references\u002Fepistemics.md` for the full confidence framework and phrasing guide. The synthesizer must follow it.\n\n## Step 1. Understand the Target and the Question\n\nThe **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.\n\nIf the target is vague (\"why do we do it this way?\" with no clear referent), make your best guess from conversation context (open files, recent edits, what was just discussed). State your interpretation briefly so the user can redirect if you're off, then proceed.\n\n## Step 2. Establish the Code Anchor\n\nBefore spawning investigators, build the seed context inline: file paths and line ranges, key symbols (functions, classes, constants), the last few commits touching the target, PR numbers from merge commits (pattern `(#1234)` in the subject line), and any linked ticket IDs. Run `git blame -L \u003Cstart>,\u003Cend> \u003Cfile>` for last-touch commits, `git log --follow -p -- \u003Cfile>` for full history with patches through renames, `git log --oneline -20 -- \u003Cfile>` for recent commits with PR numbers visible, and `git log -1 --format=%B \u003Ccommit>` to extract PR numbers. Then pull the PR bodies and discussion for any substantive commit: `gh pr view \u003Cnumber> --json title,body,author,createdAt,mergedAt,labels,closingIssuesReferences,comments,reviews`. This anchor goes to every investigator and to the synthesizer.\n\n## Step 3. Spawn Parallel Investigators\n\n**Default to the full parallel investigation.** The goal is a complete coverage map, not a minimal one. Document the null, don't skip the search.\n\n### Discovery\n\nBefore spawning investigators, list the MCP servers this session has. Claude Code names their tools `mcp__\u003Cserver>__\u003Ctool>`, and another harness by its own rule. If your harness defers a tool, load it first: in Claude Code, with ToolSearch. A server that still needs authorizing is not available: say so in the coverage map, and do not ask the user for a token.\n\nMap each available MCP to one evidence category:\n\n1. Source control history\n2. Issue \u002F ticket tracker\n3. Long-form documents\n4. Real-time team chat\n5. Infrastructure observability\n6. Error \u002F exception tracking\n7. Product analytics warehouse\n\nSource control is always available through git and `gh`. For the other six, classify using the MCP name, server instructions, tool names, and resource descriptors. If an MCP could fit more than one category, choose the one matching its primary evidence. Record ambiguous cases in the coverage map.\n\nSpawn one investigator per category that has a matching MCP, all in a single message so they run concurrently, each owning exactly one tool or MCP. Don't ask one agent to cover multiple MCPs.\n\nEach investigator's prompt is `references\u002Finvestigator-prompt.md` filled in, plus:\n- the category playbook `references\u002Fsources\u002F\u003Csource>.md` for the selected MCP, adapted from the examples in `references\u002Fsource-playbook.md`\n- `references\u002Fsources\u002Fincident-postmortem.md` **if the target code looks defensive** (null checks, retry logic, timeout handling, rate limiting, feature flags, egress guards, OOM handlers)\n- the code anchor and the user's original question\n\n### Investigator roster, one per available evidence category\n\nEach category below is uniquely positioned to surface one shape of \"why\", shown after \"Best at\". Use it to know what to expect back, to name a gap when a category returns empty, and, only in the rare provably-irrelevant case, to justify a skip.\n\n1. **Source control** (git history, `gh` for PRs, code comments, tests). Always spawn, the only guaranteed source. Best at *implementation-time rationale captured during review*.\n2. **Issue \u002F ticket tracker** (e.g. Linear, Jira, GitHub Issues, Plane, Shortcut MCP). Best at *the product or business forcing function*. Strongest when the why is external to engineering.\n3. **Long-form documents** (e.g. Notion, Confluence, Google Docs, Coda MCP). Best at *long-form design rationale*, written out before it becomes code.\n4. **Real-time team chat** (e.g. Slack, Discord, Microsoft Teams, Mattermost MCP). Best at *real-time deliberation that never reached a doc*. Especially important when the source control, ticket, and doc paper trail is thin.\n5. **Infrastructure observability** (e.g. Datadog, New Relic, Honeycomb, Grafana, Splunk MCP). Best at *infrastructure and runtime reality that motivated the code*. Strongest when the target reacts to an infra signal (timeouts, retries, rate limits, circuit breakers).\n6. **Error \u002F exception tracking** (e.g. Sentry, Rollbar, Bugsnag, Airbrake MCP). Best at *the specific exceptions and error trajectories that motivated defensive or corrective code*. Strongest for catch blocks, null guards, type checks, retries, and other defenses.\n7. **Product analytics warehouse** (e.g. Databricks, Snowflake, BigQuery, ClickHouse, dbt, Redshift MCP). Best at *product and data reality that shaped the code*. Strongest for flag-gated code, experiment-driven ships, data migrations, and \"where did this number come from\" questions.\n\n### When to skip an investigator\n\nOnly with an **explicit, written justification** that goes in the final Sources Consulted. Two valid reasons:\n\n- **No MCP is available for that category** in this environment. Flag it as a gap, not a choice: \"Real-time team chat skipped. No matching MCP available, so the conversational record was not searchable.\"\n- **The source is provably irrelevant**, not just \"probably irrelevant.\" A high bar: \"Error \u002F exception tracking skipped. Target is a build-time script with no runtime code path.\"\n\nIf your scope assessment suggests a single-commit trivial target where the PR description already contains the complete answer, you may answer inline **only after** confirming all seven available category searches would be redundant. Say so explicitly. This should be rare.\n\n## Step 4. Synthesize\n\nSpawn one synthesizer. It gets:\n1. The investigator findings, including any null results and any categories skipped with justification\n2. The code anchor\n3. The user's original question\n4. The epistemics framework from `references\u002Fepistemics.md`\n5. The synthesizer prompt template from `references\u002Fsynthesizer-prompt.md`\n\n## Step 5. Present\n\nPresent the synthesizer's output to the user. You may lightly edit for clarity or add context from the conversation, but **do not rewrite the confidence language**.\n\n## Output Format\n\nThe structure is the one in `references\u002Fsynthesizer-prompt.md`: The Question, The Code in Question, What We Found, What We Can Reasonably Infer, Competing Hypotheses, What We Don't Know, Sources Consulted, Confidence Summary. Adapt as needed, but keep the confidence separation intact, and keep Sources Consulted as one line per investigator, including the ones that returned nothing or were skipped, with the reason.\n\nAfter Sources Consulted, if the user's `why` question is a precursor to changing this code, convert the lineage findings into a Preserve \u002F Change \u002F Avoid \u002F Risk constraint set for planning the change.\n\n## Common Failure Modes to Avoid\n\n- **Recency bias**. Assuming the most recent commit is authoritative. The current shape is often the accretion of many earlier decisions. Trace back.\n",{"tip":24,"card":25,"name":5,"description":7},"finds why the code is the way it is, with cited evidence | why does * work this way | why did we pick | why did we choose | design rationale | postmortem | post mortem","Understand what is there | 2 | Explains why something was built this way, with a cited read of the decisions and tradeoffs from source control, issues and docs. | Reach for it when you need the rationale, or are looking into a regression. | op: the operator; plain: a step of `architect`","main","daff051d2674b46e2eb8a333bbd3f3e40f8d1cea","features\u002Fwhy",0,"https:\u002F\u002Fgithub.com\u002FJoshuaHayesWasHere\u002Fjstack","https:\u002F\u002Fgithub.com\u002FJoshuaHayesWasHere","Software Engineer @ Markel\r\n","2026-11-15 11:25:06",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add JoshuaHayesWasHere\u002Fjstack --skill why",{"tool":40,"command":41},"bunx","bunx skills add JoshuaHayesWasHere\u002Fjstack --skill why",{"tool":43,"command":44},"pnpm","pnpm dlx skills add JoshuaHayesWasHere\u002Fjstack --skill why","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FJoshuaHayesWasHere\u002Fjstack\u002Fblob\u002Fmain\u002Ffeatures\u002Fwhy\u002FSKILL.md",true,[48,54,58,62,66,70,74,78,82,86,90,94,98,102],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"feature.json","REFERENCE","参考文档",148,"https:\u002F\u002Fgithub.com\u002FJoshuaHayesWasHere\u002Fjstack\u002Fblob\u002Fmain\u002Ffeatures\u002Fwhy\u002Ffeature.json",{"path":55,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Fepistemics.md",6736,"https:\u002F\u002Fgithub.com\u002FJoshuaHayesWasHere\u002Fjstack\u002Fblob\u002Fmain\u002Ffeatures\u002Fwhy\u002Freferences\u002Fepistemics.md",{"path":59,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":60,"sourceHtmlUrl":61},"references\u002Finvestigator-prompt.md",5554,"https:\u002F\u002Fgithub.com\u002FJoshuaHayesWasHere\u002Fjstack\u002Fblob\u002Fmain\u002Ffeatures\u002Fwhy\u002Freferences\u002Finvestigator-prompt.md",{"path":63,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":64,"sourceHtmlUrl":65},"references\u002Fsource-playbook.md",1363,"https:\u002F\u002Fgithub.com\u002FJoshuaHayesWasHere\u002Fjstack\u002Fblob\u002Fmain\u002Ffeatures\u002Fwhy\u002Freferences\u002Fsource-playbook.md",{"path":67,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":68,"sourceHtmlUrl":69},"references\u002Fsources\u002Fcode-archaeology.md",1440,"https:\u002F\u002Fgithub.com\u002FJoshuaHayesWasHere\u002Fjstack\u002Fblob\u002Fmain\u002Ffeatures\u002Fwhy\u002Freferences\u002Fsources\u002Fcode-archaeology.md",{"path":71,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Fsources\u002Fdatabricks.md",6994,"https:\u002F\u002Fgithub.com\u002FJoshuaHayesWasHere\u002Fjstack\u002Fblob\u002Fmain\u002Ffeatures\u002Fwhy\u002Freferences\u002Fsources\u002Fdatabricks.md",{"path":75,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Fsources\u002Fdatadog.md",4971,"https:\u002F\u002Fgithub.com\u002FJoshuaHayesWasHere\u002Fjstack\u002Fblob\u002Fmain\u002Ffeatures\u002Fwhy\u002Freferences\u002Fsources\u002Fdatadog.md",{"path":79,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Fsources\u002Fincident-postmortem.md",372,"https:\u002F\u002Fgithub.com\u002FJoshuaHayesWasHere\u002Fjstack\u002Fblob\u002Fmain\u002Ffeatures\u002Fwhy\u002Freferences\u002Fsources\u002Fincident-postmortem.md",{"path":83,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":84,"sourceHtmlUrl":85},"references\u002Fsources\u002Flinear.md",2996,"https:\u002F\u002Fgithub.com\u002FJoshuaHayesWasHere\u002Fjstack\u002Fblob\u002Fmain\u002Ffeatures\u002Fwhy\u002Freferences\u002Fsources\u002Flinear.md",{"path":87,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":88,"sourceHtmlUrl":89},"references\u002Fsources\u002Fnotion.md",2853,"https:\u002F\u002Fgithub.com\u002FJoshuaHayesWasHere\u002Fjstack\u002Fblob\u002Fmain\u002Ffeatures\u002Fwhy\u002Freferences\u002Fsources\u002Fnotion.md",{"path":91,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":92,"sourceHtmlUrl":93},"references\u002Fsources\u002Fsentry.md",2089,"https:\u002F\u002Fgithub.com\u002FJoshuaHayesWasHere\u002Fjstack\u002Fblob\u002Fmain\u002Ffeatures\u002Fwhy\u002Freferences\u002Fsources\u002Fsentry.md",{"path":95,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":96,"sourceHtmlUrl":97},"references\u002Fsources\u002Fslack.md",1348,"https:\u002F\u002Fgithub.com\u002FJoshuaHayesWasHere\u002Fjstack\u002Fblob\u002Fmain\u002Ffeatures\u002Fwhy\u002Freferences\u002Fsources\u002Fslack.md",{"path":99,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":100,"sourceHtmlUrl":101},"references\u002Fsynthesizer-prompt.md",7189,"https:\u002F\u002Fgithub.com\u002FJoshuaHayesWasHere\u002Fjstack\u002Fblob\u002Fmain\u002Ffeatures\u002Fwhy\u002Freferences\u002Fsynthesizer-prompt.md",{"path":103,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":104,"sourceHtmlUrl":105},"verify.md",487,"https:\u002F\u002Fgithub.com\u002FJoshuaHayesWasHere\u002Fjstack\u002Fblob\u002Fmain\u002Ffeatures\u002Fwhy\u002Fverify.md",[107,114,121,128,135,142],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":19},"01M7ERF9GXMY62V7QTVAR6G8DG","no-key","A skill its skills.json lists as hidden that a model may still call by itself, kept broken so the lint is seen to catch it.","https:\u002F\u002Fgithub.com\u002FJoshuaHayesWasHere\u002Fjstack\u002Fblob\u002Fmain\u002Ftesting\u002Ftests\u002Ffixtures\u002Fskills\u002Fno-key\u002FSKILL.md",[],[],{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":19},"01M7ERF83ZG3XKJ2SB8MJHCZ8H","fake-skill","A FAKE skill in a FAKE tree, named for its folder until the test renames the folder.","https:\u002F\u002Fgithub.com\u002FJoshuaHayesWasHere\u002Fjstack\u002Fblob\u002Fmain\u002Ftesting\u002Ftests\u002Ffixtures\u002Fskills\u002Fnamed-tree\u002Fskills\u002Ffake-skill\u002FSKILL.md",[],[],{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":19},"01M7ERF698RV4VF8QCDF8H8DA4","extra-key","A skill its skills.json does not list as hidden that a model still cannot call, kept broken so the lint is seen to catch it.","https:\u002F\u002Fgithub.com\u002FJoshuaHayesWasHere\u002Fjstack\u002Fblob\u002Fmain\u002Ftesting\u002Ftests\u002Ffixtures\u002Fskills\u002Fextra-key\u002FSKILL.md",[],[],{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":134,"publishedAt":19},"01M7ERF2V8N73X9T0Y9PJ4SFV6","unslop","Cut AI tells from writing. Use when the user says text reads like AI, asks to unslop it, or before prose ships to people.","https:\u002F\u002Fgithub.com\u002FJoshuaHayesWasHere\u002Fjstack\u002Fblob\u002Fmain\u002Ffeatures\u002Fwriting\u002Fskills\u002Funslop\u002FSKILL.md",[],[],{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":139,"categories":140,"keywords":141,"publishedAt":19},"01M7EREWM67WX934XKABM4XCSZ","technical-writing","Write or review docs, READMEs, RFCs, PR descriptions and commit messages to a layered standard: Diataxis structure, Google developer style, STE rules and Global English.","https:\u002F\u002Fgithub.com\u002FJoshuaHayesWasHere\u002Fjstack\u002Fblob\u002Fmain\u002Ffeatures\u002Fwriting\u002Fskills\u002Ftechnical-writing\u002FSKILL.md",[],[],{"skillNo":143,"name":144,"nameZh":6,"description":145,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":146,"categories":147,"keywords":148,"publishedAt":19},"01M7EREGWH7JW073MWRB3F1PYS","verify-jstack","Drive jstack's commands (jbus, jmerge, jgauge, install.sh) the way a user does, inside a throwaway sandbox with stand-ins for T3 Code and GitHub, and keep the evidence. Use to prove a change to jstack works in the real commands and not only in its tests, before a pull request claims it does.","https:\u002F\u002Fgithub.com\u002FJoshuaHayesWasHere\u002Fjstack\u002Fblob\u002Fmain\u002Ffeatures\u002Fverify-jstack\u002Fproject-skill\u002FSKILL.md",[],[]]