[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CD4WMF6G61HQSH1NQS8FST":3,"skill-same:01M7CD4WMF6G61HQSH1NQS8FST":47},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":46},"01M7CD4WMF6G61HQSH1NQS8FST","reflect",null,"Spawn three parallel review subagents over the active transcript, surface learnings, and route each to a concrete edit on an existing skill. Use when the user says reflect.","Whamp\u002Fpi-extensions","Whamp","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1115485?v=4","01M6GV45K5PM2S7V3H0JERGBXN","Will Hampson","01M7CD24WR8BM48CT1X6HWVASD",1,"MIT","https:\u002F\u002Fgithub.com\u002FWhamp\u002Fpi-extensions\u002Fblob\u002Fmaster\u002Fpackages\u002Fpi-pstack\u002Ffixtures\u002Fcursor-pstack-df58112\u002Fskills\u002Freflect\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: reflect\ndescription: Spawn three parallel review subagents over the active transcript, surface learnings, and route each to a concrete edit on an existing skill. Use when the user says reflect.\ndisable-model-invocation: true\n---\n\n# Reflect\n\nMine the current conversation for durable learnings, then route them into skill edits.\n\n## When to invoke\n\nInvoke when the user says \"reflect\" or \"\u002Freflect\". Skip when the conversation is trivial, off-topic, or already covered by an existing skill the parent followed correctly. One-offs are not learnings.\n\n## Process\n\n### 1. Locate the active transcript\n\nThe parent finds its own transcript file before fanning out. The system prompt names the active workspace's `agent-transcripts\u002F` directory. Use that path. Do not glob across `~\u002F.cursor\u002Fprojects\u002F*\u002F`. That crosses workspace boundaries and reads private chats from unrelated projects.\n\n```bash\nls -t \u003Cagent-transcripts>\u002F*.jsonl \u003Cagent-transcripts>\u002F*\u002F*.jsonl \u003Cagent-transcripts>\u002F*\u002Fsubagents\u002F*.jsonl 2>\u002Fdev\u002Fnull | head -10\n```\n\nThree transcript layouts: legacy flat (`\u003Cid>.jsonl`), current nested (`\u003Cid>\u002F\u003Cid>.jsonl`), and subagent (`\u003Cparent>\u002Fsubagents\u002F\u003Cchild>.jsonl`).\n\nFor each candidate, read the first JSONL line and check that `message.content[0].text` contains the conversation's opening user prompt. Take the matching path. If no path resolves, write a tight digest of the session and pass that instead.\n\n### 2. Spawn three reviewers in parallel\n\nOne message, three `Task` calls, `subagent_type: generalPurpose`, with `model` set as below, agent mode (`readonly: false`). Reviewers need MCP access for context lookups (tickets, chat threads, observability traces referenced in the transcript). Readonly strips MCPs.\n\nEach reviewer and the synthesizer name a role line in the `pstack-models.mdc` rule and a default. Set `model` to that line's value, or to the default if the rule or the line is missing. Leave `model` unset when the value is `auto` or `inherit-parent`. If the Task tool rejects a slug, use the default and say so. If it rejects the default, use the closest valid slug of the same family from its error message.\n\n| Lens | Role line | Default `model` | Prompt template |\n|---|---|---|---|\n| Judgment | `reflect judgment, divergent, synthesizer` | `claude-opus-5-5-xhigh` | `references\u002Fjudgment-reviewer.md` |\n| Tooling | `reflect tooling` | `grok-4.7-xhigh-fast` | `references\u002Ftooling-reviewer.md` |\n| Divergent | `reflect judgment, divergent, synthesizer` | `claude-opus-5-5-xhigh` | `references\u002Fdivergent-reviewer.md` |\n\nPass each template verbatim, substituting the transcript path or digest where marked. Reviewers return findings in the `Task` response body.\n\n### 3. Synthesize\n\nOne `Task` call, `subagent_type: generalPurpose`, with `model` from the `reflect judgment, divergent, synthesizer` line (default `claude-opus-5-5-xhigh`), agent mode (`readonly: false`). The synthesizer's quality check includes spot-verifying citations, which can require MCP access. Readonly strips MCPs. Use `references\u002Fsynthesizer.md` verbatim, with each reviewer's full output inlined where marked. The synthesizer returns a structured Accepted \u002F Rejected \u002F Backlog list.\n\n### 4. Structural enforcement check\n\nSanity-check the synthesizer's Accepted list. For any item that would be enforced more reliably by a lint rule, script, metadata flag, or runtime check, move it from Accepted to Backlog. See the **encode-lessons-in-structure** principle skill.\n\n### 5. Apply\n\nBefore applying any Accepted edit, present the synthesizer's full Accepted\u002FRejected\u002FBacklog output to the user and wait for explicit approval. The user picks which subset to apply and may redirect routings. Skill changes affect every future agent in the org. Do not auto-apply.\n\nBacklog items file to whatever devex \u002F backlog tracker your team uses automatically. Only the Accepted list waits for approval.\n\nFor each approved Accepted item, follow the Routing field exactly:\n\n- Trivial existing-skill edit (a one-line bullet, a tightened sentence, a stale fact corrected): parent does directly.\n- Substantive existing-skill edit (a new section, a new pattern table, more than ~10 lines): hand to Cursor's built-in `create-skill` skill and run its draft \u002F test \u002F iterate loop.\n- `tune description: \u003Cskill path>` (the skill exists but didn't trigger when it should have): hand to `create-skill` and run its description-optimization loop.\n- `new skill via create-skill: \u003Ckebab-name>`: hand creation to `create-skill`. Do not invent the shape ad hoc.\n\nIf your environment ships a SKILL.md validator, run it on every touched skill before declaring done. Skip this step if it doesn't.\n\n### 6. Summarize for the user\n\nShort list, no preamble:\n\n- Edits applied: `\u003Cskill path>`. What changed, one line each.\n- New skills created: `\u003Cskill path>`. One line each (rare).\n- Backlog filed to the devex tracker: `\u003Cissue title>` (`\u003Ctags>`). One line each.\n- Dropped: one line per rejected finding + reason from the synthesizer.\n","# Reflect\n\nMine the current conversation for durable learnings, then route them into skill edits.\n\n## When to invoke\n\nInvoke when the user says \"reflect\" or \"\u002Freflect\". Skip when the conversation is trivial, off-topic, or already covered by an existing skill the parent followed correctly. One-offs are not learnings.\n\n## Process\n\n### 1. Locate the active transcript\n\nThe parent finds its own transcript file before fanning out. The system prompt names the active workspace's `agent-transcripts\u002F` directory. Use that path. Do not glob across `~\u002F.cursor\u002Fprojects\u002F*\u002F`. That crosses workspace boundaries and reads private chats from unrelated projects.\n\n```bash\nls -t \u003Cagent-transcripts>\u002F*.jsonl \u003Cagent-transcripts>\u002F*\u002F*.jsonl \u003Cagent-transcripts>\u002F*\u002Fsubagents\u002F*.jsonl 2>\u002Fdev\u002Fnull | head -10\n```\n\nThree transcript layouts: legacy flat (`\u003Cid>.jsonl`), current nested (`\u003Cid>\u002F\u003Cid>.jsonl`), and subagent (`\u003Cparent>\u002Fsubagents\u002F\u003Cchild>.jsonl`).\n\nFor each candidate, read the first JSONL line and check that `message.content[0].text` contains the conversation's opening user prompt. Take the matching path. If no path resolves, write a tight digest of the session and pass that instead.\n\n### 2. Spawn three reviewers in parallel\n\nOne message, three `Task` calls, `subagent_type: generalPurpose`, with `model` set as below, agent mode (`readonly: false`). Reviewers need MCP access for context lookups (tickets, chat threads, observability traces referenced in the transcript). Readonly strips MCPs.\n\nEach reviewer and the synthesizer name a role line in the `pstack-models.mdc` rule and a default. Set `model` to that line's value, or to the default if the rule or the line is missing. Leave `model` unset when the value is `auto` or `inherit-parent`. If the Task tool rejects a slug, use the default and say so. If it rejects the default, use the closest valid slug of the same family from its error message.\n\n| Lens | Role line | Default `model` | Prompt template |\n|---|---|---|---|\n| Judgment | `reflect judgment, divergent, synthesizer` | `claude-opus-5-5-xhigh` | `references\u002Fjudgment-reviewer.md` |\n| Tooling | `reflect tooling` | `grok-4.7-xhigh-fast` | `references\u002Ftooling-reviewer.md` |\n| Divergent | `reflect judgment, divergent, synthesizer` | `claude-opus-5-5-xhigh` | `references\u002Fdivergent-reviewer.md` |\n\nPass each template verbatim, substituting the transcript path or digest where marked. Reviewers return findings in the `Task` response body.\n\n### 3. Synthesize\n\nOne `Task` call, `subagent_type: generalPurpose`, with `model` from the `reflect judgment, divergent, synthesizer` line (default `claude-opus-5-5-xhigh`), agent mode (`readonly: false`). The synthesizer's quality check includes spot-verifying citations, which can require MCP access. Readonly strips MCPs. Use `references\u002Fsynthesizer.md` verbatim, with each reviewer's full output inlined where marked. The synthesizer returns a structured Accepted \u002F Rejected \u002F Backlog list.\n\n### 4. Structural enforcement check\n\nSanity-check the synthesizer's Accepted list. For any item that would be enforced more reliably by a lint rule, script, metadata flag, or runtime check, move it from Accepted to Backlog. See the **encode-lessons-in-structure** principle skill.\n\n### 5. Apply\n\nBefore applying any Accepted edit, present the synthesizer's full Accepted\u002FRejected\u002FBacklog output to the user and wait for explicit approval. The user picks which subset to apply and may redirect routings. Skill changes affect every future agent in the org. Do not auto-apply.\n\nBacklog items file to whatever devex \u002F backlog tracker your team uses automatically. Only the Accepted list waits for approval.\n\nFor each approved Accepted item, follow the Routing field exactly:\n\n- Trivial existing-skill edit (a one-line bullet, a tightened sentence, a stale fact corrected): parent does directly.\n- Substantive existing-skill edit (a new section, a new pattern table, more than ~10 lines): hand to Cursor's built-in `create-skill` skill and run its draft \u002F test \u002F iterate loop.\n- `tune description: \u003Cskill path>` (the skill exists but didn't trigger when it should have): hand to `create-skill` and run its description-optimization loop.\n- `new skill via create-skill: \u003Ckebab-name>`: hand creation to `create-skill`. Do not invent the shape ad hoc.\n\nIf your environment ships a SKILL.md validator, run it on every touched skill before declaring done. Skip this step if it doesn't.\n\n### 6. Summarize for the user\n\nShort list, no preamble:\n\n- Edits applied: `\u003Cskill path>`. What changed, one line each.\n- New skills created: `\u003Cskill path>`. One line each (rare).\n- Backlog filed to the devex tracker: `\u003Cissue title>` (`\u003Ctags>`). One line each.\n- Dropped: one line per rejected finding + reason from the synthesizer.\n",{"name":5,"description":7,"disable-model-invocation":24},true,"master","1d75a8ae76094c017ddb973723b6d6dfa1e0c1c3","packages\u002Fpi-pstack\u002Ffixtures\u002Fcursor-pstack-df58112\u002Fskills\u002Freflect",0,"https:\u002F\u002Fgithub.com\u002FWhamp\u002Fpi-extensions","https:\u002F\u002Fgithub.com\u002FWhamp","https:\u002F\u002Ftwitter.com\u002Fhampsonw","Motorcycles. Dogs. Bonds. Autodidact. http:\u002F\u002Fcourse.fast.ai  alum","2026-10-24 21:56:00",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":24},[36,39,42],{"tool":37,"command":38},"npx","npx skills add Whamp\u002Fpi-extensions --skill reflect",{"tool":40,"command":41},"bunx","bunx skills add Whamp\u002Fpi-extensions --skill reflect",{"tool":43,"command":44},"pnpm","pnpm dlx skills add Whamp\u002Fpi-extensions --skill reflect","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FWhamp\u002Fpi-extensions\u002Fblob\u002Fmaster\u002Fpackages\u002Fpi-pstack\u002Ffixtures\u002Fcursor-pstack-df58112\u002Fskills\u002Freflect\u002FSKILL.md",[],[48,55,62,69,76,83],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7CD9WQEV4QVY73VGX1TDQ43","sidekick-browser","Use the pinned local AXI launcher for explicit, isolated browser verification in a Sidekick child.","https:\u002F\u002Fgithub.com\u002FWhamp\u002Fpi-extensions\u002Fblob\u002Fmaster\u002Fpackages\u002Fpi-sidekick\u002Fskills\u002Fsidekick-browser\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7CD9PVK6TRMX8DZR5B9QS1W","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\u002FWhamp\u002Fpi-extensions\u002Fblob\u002Fmaster\u002Fpackages\u002Fpi-pstack\u002Fskills\u002Fwhy\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7CD9KY7SH6P8ENEZG6463DV","unslop","Cut AI tells from any writing.","https:\u002F\u002Fgithub.com\u002FWhamp\u002Fpi-extensions\u002Fblob\u002Fmaster\u002Fpackages\u002Fpi-pstack\u002Fskills\u002Funslop\u002FSKILL.md",[],[],{"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":19},"01M7CD9J8RY8ZH1XMHNC1A2423","typescript-best-practices","TypeScript best practices. Use when reading or editing any .ts or .tsx file.","https:\u002F\u002Fgithub.com\u002FWhamp\u002Fpi-extensions\u002Fblob\u002Fmaster\u002Fpackages\u002Fpi-pstack\u002Fskills\u002Ftypescript-best-practices\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":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7CD9DY3PRH9Z1X7JTZMZRBG","technical-writing","Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for \u002Fskill:technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.","https:\u002F\u002Fgithub.com\u002FWhamp\u002Fpi-extensions\u002Fblob\u002Fmaster\u002Fpackages\u002Fpi-pstack\u002Fskills\u002Ftechnical-writing\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7CD9B6C9NXWJHEKGYPCFD6M","teach","Explain a body of work plainly so a person actually understands it. Runs the `how` and `why` skills and weaves what they find into one clear explanation. Use for 'teach me this', 'help me really understand X', 'explain this change or subsystem to me'.","https:\u002F\u002Fgithub.com\u002FWhamp\u002Fpi-extensions\u002Fblob\u002Fmaster\u002Fpackages\u002Fpi-pstack\u002Fskills\u002Fteach\u002FSKILL.md",[],[]]