[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EVADAM8PZCFNDKM8T3NYAX":3,"skill-same:01M7EVADAM8PZCFNDKM8T3NYAX":64},{"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":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":45},"01M7EVADAM8PZCFNDKM8T3NYAX","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.","shreshthkapai\u002Fagent-workflows","shreshthkapai","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F73650860?v=4","01M7EV5VN4GMWQ8R39WQ7KYFZQ","Shreshth","01M7EV5VNTDGPW78K42W4TYBAJ",0,"MIT","https:\u002F\u002Fgithub.com\u002Fshreshthkapai\u002Fagent-workflows\u002Fblob\u002Fmain\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\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## 1. Locate the active transcript\n\nBefore fanning out, find this conversation's transcript. In Claude Code it lives in `~\u002F.claude\u002Fprojects\u002F\u003Cslug>\u002F`, where `\u003Cslug>` is the working directory with every `\u002F` replaced by `-`. Do not glob across `~\u002F.claude\u002Fprojects\u002F*\u002F`. That crosses workspace boundaries and reads private chats from unrelated projects. Codex keeps every project's sessions under `~\u002F.codex\u002Fsessions\u002FYYYY\u002FMM\u002FDD\u002F`, so check that the first line's `payload.cwd` is the working directory before reading further. Grok keeps `~\u002F.grok\u002Fsessions\u002F\u003Cencoded-cwd>\u002F\u003Csession-id>\u002Fchat_history.jsonl`, one directory per workspace, and `grok sessions list` names this workspace's sessions.\n\n```bash\nls -t ~\u002F.claude\u002Fprojects\u002F\u003Cslug>\u002F*.jsonl ~\u002F.claude\u002Fprojects\u002F\u003Cslug>\u002F*\u002Fsubagents\u002F*.jsonl 2>\u002Fdev\u002Fnull | head -10  # Claude Code\nls -t ~\u002F.codex\u002Fsessions\u002F*\u002F*\u002F*\u002F*.jsonl 2>\u002Fdev\u002Fnull | head -10  # Codex\ngrok sessions list  # Grok\n```\n\nThat covers the Claude Code session (`\u003Cid>.jsonl`) and subagent (`\u003Cid>\u002Fsubagents\u002F\u003Cchild>.jsonl`) layouts, and Codex's dated rollout files. For each candidate, `grep -l` a distinctive phrase from the conversation's opening user prompt. Take the file that contains it. If none matches, pass a tight digest of the session instead.\n\n## 2. Spawn three reviewers in parallel\n\nSpawn three general-purpose subagents at once, not read-only. Reviewers need MCP access to look up the tickets, chat threads, and observability traces the transcript references, and read-only modes can block MCP tools.\n\nEach reviewer and the synthesizer name a role in `~\u002F.config\u002Fagent-workflows\u002Fmodels.toml`. Resolve its model with `aw-run --resolve \u003Crole>` and spawn per the Subagents section of the **workflow** skill. A role of `inherit` runs on the parent model. If the spawn or `aw-run` rejects the model, use the model's `fallback` and say so. Pick each subagent's reasoning level and fast or standard speed for the job, per the Subagents section of the **workflow** skill.\n\n| Lens | Role | Prompt template |\n|---|---|---|\n| Judgment | `reflect_judgment` | `references\u002Fjudgment-reviewer.md` |\n| Tooling | `reflect_tooling` | `references\u002Ftooling-reviewer.md` |\n| Divergent | `reflect_judgment` | `references\u002Fdivergent-reviewer.md` |\n\nPass each template verbatim, substituting the transcript path or digest where marked. Reviewers return findings in their final message.\n\n## 3. Synthesize\n\nOne general-purpose subagent on the `reflect_judgment` role, not read-only. It spot-verifies citations through MCP, and read-only modes can block MCP tools. Pass `references\u002Fsynthesizer.md` verbatim, with each reviewer's full output inlined where marked. It returns an Accepted \u002F Rejected \u002F Backlog list.\n\n## 4. Structural enforcement check\n\nMove any Accepted item that a lint rule, script, metadata flag, or runtime check would enforce more reliably to Backlog. See the **encode-lessons-in-structure** principle skill.\n\n## 5. Apply\n\nPresent the synthesizer's full Accepted \u002F Rejected \u002F Backlog output and wait for explicit approval before applying any Accepted edit. The user picks the subset and may redirect routings. Skill changes affect every future agent in the org. Do not auto-apply.\n\nFile each Backlog item to your team's devex or backlog tracker without waiting. Only the Accepted list waits for approval.\n\nFollow each approved row's Routing exactly:\n\n- Trivial existing-skill edit (a one-line bullet, a tightened sentence, a stale fact corrected): the parent does it directly.\n- Substantive existing-skill edit (a new section, a new pattern table, more than ~10 lines): hand to the CLI's `skill-creator` 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 `skill-creator` and run its description-optimization loop.\n- `new skill via skill-creator: \u003Ckebab-name>`: hand creation to `skill-creator`. 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.\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\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## 1. Locate the active transcript\n\nBefore fanning out, find this conversation's transcript. In Claude Code it lives in `~\u002F.claude\u002Fprojects\u002F\u003Cslug>\u002F`, where `\u003Cslug>` is the working directory with every `\u002F` replaced by `-`. Do not glob across `~\u002F.claude\u002Fprojects\u002F*\u002F`. That crosses workspace boundaries and reads private chats from unrelated projects. Codex keeps every project's sessions under `~\u002F.codex\u002Fsessions\u002FYYYY\u002FMM\u002FDD\u002F`, so check that the first line's `payload.cwd` is the working directory before reading further. Grok keeps `~\u002F.grok\u002Fsessions\u002F\u003Cencoded-cwd>\u002F\u003Csession-id>\u002Fchat_history.jsonl`, one directory per workspace, and `grok sessions list` names this workspace's sessions.\n\n```bash\nls -t ~\u002F.claude\u002Fprojects\u002F\u003Cslug>\u002F*.jsonl ~\u002F.claude\u002Fprojects\u002F\u003Cslug>\u002F*\u002Fsubagents\u002F*.jsonl 2>\u002Fdev\u002Fnull | head -10  # Claude Code\nls -t ~\u002F.codex\u002Fsessions\u002F*\u002F*\u002F*\u002F*.jsonl 2>\u002Fdev\u002Fnull | head -10  # Codex\ngrok sessions list  # Grok\n```\n\nThat covers the Claude Code session (`\u003Cid>.jsonl`) and subagent (`\u003Cid>\u002Fsubagents\u002F\u003Cchild>.jsonl`) layouts, and Codex's dated rollout files. For each candidate, `grep -l` a distinctive phrase from the conversation's opening user prompt. Take the file that contains it. If none matches, pass a tight digest of the session instead.\n\n## 2. Spawn three reviewers in parallel\n\nSpawn three general-purpose subagents at once, not read-only. Reviewers need MCP access to look up the tickets, chat threads, and observability traces the transcript references, and read-only modes can block MCP tools.\n\nEach reviewer and the synthesizer name a role in `~\u002F.config\u002Fagent-workflows\u002Fmodels.toml`. Resolve its model with `aw-run --resolve \u003Crole>` and spawn per the Subagents section of the **workflow** skill. A role of `inherit` runs on the parent model. If the spawn or `aw-run` rejects the model, use the model's `fallback` and say so. Pick each subagent's reasoning level and fast or standard speed for the job, per the Subagents section of the **workflow** skill.\n\n| Lens | Role | Prompt template |\n|---|---|---|\n| Judgment | `reflect_judgment` | `references\u002Fjudgment-reviewer.md` |\n| Tooling | `reflect_tooling` | `references\u002Ftooling-reviewer.md` |\n| Divergent | `reflect_judgment` | `references\u002Fdivergent-reviewer.md` |\n\nPass each template verbatim, substituting the transcript path or digest where marked. Reviewers return findings in their final message.\n\n## 3. Synthesize\n\nOne general-purpose subagent on the `reflect_judgment` role, not read-only. It spot-verifies citations through MCP, and read-only modes can block MCP tools. Pass `references\u002Fsynthesizer.md` verbatim, with each reviewer's full output inlined where marked. It returns an Accepted \u002F Rejected \u002F Backlog list.\n\n## 4. Structural enforcement check\n\nMove any Accepted item that a lint rule, script, metadata flag, or runtime check would enforce more reliably to Backlog. See the **encode-lessons-in-structure** principle skill.\n\n## 5. Apply\n\nPresent the synthesizer's full Accepted \u002F Rejected \u002F Backlog output and wait for explicit approval before applying any Accepted edit. The user picks the subset and may redirect routings. Skill changes affect every future agent in the org. Do not auto-apply.\n\nFile each Backlog item to your team's devex or backlog tracker without waiting. Only the Accepted list waits for approval.\n\nFollow each approved row's Routing exactly:\n\n- Trivial existing-skill edit (a one-line bullet, a tightened sentence, a stale fact corrected): the parent does it directly.\n- Substantive existing-skill edit (a new section, a new pattern table, more than ~10 lines): hand to the CLI's `skill-creator` 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 `skill-creator` and run its description-optimization loop.\n- `new skill via skill-creator: \u003Ckebab-name>`: hand creation to `skill-creator`. 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.\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,"main","cafd398384400c1a0ce1da059a134394f28a690e","skills\u002Freflect","https:\u002F\u002Fgithub.com\u002Fshreshthkapai\u002Fagent-workflows","https:\u002F\u002Fgithub.com\u002Fshreshthkapai","https:\u002F\u002Fshreshth-personal-website.vercel.app\u002F","Lost....in neural networks","2026-10-30 08:24:11",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":24},[35,38,41],{"tool":36,"command":37},"npx","npx skills add shreshthkapai\u002Fagent-workflows --skill reflect",{"tool":39,"command":40},"bunx","bunx skills add shreshthkapai\u002Fagent-workflows --skill reflect",{"tool":42,"command":43},"pnpm","pnpm dlx skills add shreshthkapai\u002Fagent-workflows --skill reflect","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshreshthkapai\u002Fagent-workflows\u002Fblob\u002Fmain\u002Fskills\u002Freflect\u002FSKILL.md",[46,52,56,60],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"references\u002Fdivergent-reviewer.md","REFERENCE","参考文档",3733,"https:\u002F\u002Fgithub.com\u002Fshreshthkapai\u002Fagent-workflows\u002Fblob\u002Fmain\u002Fskills\u002Freflect\u002Freferences\u002Fdivergent-reviewer.md",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Fjudgment-reviewer.md",3172,"https:\u002F\u002Fgithub.com\u002Fshreshthkapai\u002Fagent-workflows\u002Fblob\u002Fmain\u002Fskills\u002Freflect\u002Freferences\u002Fjudgment-reviewer.md",{"path":57,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":58,"sourceHtmlUrl":59},"references\u002Fsynthesizer.md",4144,"https:\u002F\u002Fgithub.com\u002Fshreshthkapai\u002Fagent-workflows\u002Fblob\u002Fmain\u002Fskills\u002Freflect\u002Freferences\u002Fsynthesizer.md",{"path":61,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":62,"sourceHtmlUrl":63},"references\u002Ftooling-reviewer.md",4513,"https:\u002F\u002Fgithub.com\u002Fshreshthkapai\u002Fagent-workflows\u002Fblob\u002Fmain\u002Fskills\u002Freflect\u002Freferences\u002Ftooling-reviewer.md",[65,72,79,86,93,100],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7EVBMVS4ZXTSPK19XNMYNT5","workflow","Concise, detailed responses, deliberate subagents, unslopped prose, simple code, and verified work, with each task routed to a playbook. Use for \u002Fworkflow, or for requests to work in this style. `aw skills always workflow` loads it into every session.","https:\u002F\u002Fgithub.com\u002Fshreshthkapai\u002Fagent-workflows\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7EVBEEEVNYKRCGBH6V5SSFA","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\u002Fshreshthkapai\u002Fagent-workflows\u002Fblob\u002Fmain\u002Fskills\u002Fwhy\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7EVBBK5G5QKHXWVYHTRKJ0B","unslop","Cut AI tells from any writing.","https:\u002F\u002Fgithub.com\u002Fshreshthkapai\u002Fagent-workflows\u002Fblob\u002Fmain\u002Fskills\u002Funslop\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7EVB9ED5F0RVKN70D2ZKV9W","typescript-best-practices","TypeScript best practices. Use when reading or editing any .ts or .tsx file.","https:\u002F\u002Fgithub.com\u002Fshreshthkapai\u002Fagent-workflows\u002Fblob\u002Fmain\u002Fskills\u002Ftypescript-best-practices\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M7EVB568STK9X05C00C83KBD","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\u002Fshreshthkapai\u002Fagent-workflows\u002Fblob\u002Fmain\u002Fskills\u002Ftechnical-writing\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":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":19},"01M7EVB0H4V10C6GQHXX4599Y2","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\u002Fshreshthkapai\u002Fagent-workflows\u002Fblob\u002Fmain\u002Fskills\u002Fteach\u002FSKILL.md",[],[]]