[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EVAG5FCYYZWS57K2TA3RF3":3,"skill-same:01M7EVAG5FCYYZWS57K2TA3RF3":46},{"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},"01M7EVAG5FCYYZWS57K2TA3RF3","setup-pstack",null,"Configure which models pstack uses per role and at what reasoning budget. Detects your available models and writes the shared model registry that overrides the skill defaults. Use for \u002Fsetup-pstack, \"configure pstack models\", \"pstack budget\", or changing pstack's model choices.","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\u002Fsetup-pstack\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: setup-pstack\ndescription: Configure which models pstack uses per role and at what reasoning budget. Detects your available models and writes the shared model registry that overrides the skill defaults. Use for \u002Fsetup-pstack, \"configure pstack models\", \"pstack budget\", or changing pstack's model choices.\ndisable-model-invocation: true\n---\n\n# Setup pstack\n\nWrite `~\u002F.config\u002Fagent-workflows\u002Fmodels.toml`, the model registry that sets pstack's model per role. Claude Code, Codex, and Grok all read it, through `aw-run`.\n\n## Steps\n\n### 1. Detect available models\n\nDetect only for the CLIs on `PATH`. Codex: run `codex debug models` and take the `slug` of each entry with `\"visibility\": \"list\"`, with its `supported_reasoning_levels`. Claude Code: the CLI accepts the aliases `opus`, `sonnet`, `haiku`, and `fable`, or a full model name. It has no listing command, so treat those aliases as detected and ask the user to paste any full name they want. Grok: run `grok models` and take each model id it lists. Never write a model you have not confirmed is available. The value `inherit` is always valid even though it is not a detected model.\n\n### 2. Load current state\n\nThe default role-to-model mapping is the registry shape shown in step 5 below. If `~\u002F.config\u002Fagent-workflows\u002Fmodels.toml` already exists, read it and treat its `budget` and its roles as the current choices. Otherwise start from those defaults. A role not in step 5, such as `how_critics`, is from a retired role. Drop it.\n\n### 3. Budget, map, and confirm\n\n**(a) Ask for a budget.** Ask with the CLI's structured question tool when it has one, otherwise in plain text. Offer these four options with these exact labels, and name the current budget when the registry records one. With no registry, say that `large` matches the skill defaults.\n\n- `unlimited — max reasoning`\n- `large — xhigh reasoning`\n- `medium — high reasoning`\n- `small — medium reasoning`\n\n**(b) Apply it.** The registry's `budget` sets the starting effort of every role, panel entries included, to `max`, `xhigh`, `high`, or `medium`, on the ladder `max` > `xhigh` > `high` > `medium` > `low`. All three CLIs accept every level on that ladder. An entry may set its own effort and speed as `model:effort` or `model:effort:fast`, which overrides the budget. Only Codex models have a fast tier. `aw-run` applies both. `inherit` does not change.\n\n**(c) Show the roles and confirm.** Show every role with its model, provider, and effort at the chosen budget, marking any model not in the detected set as needing a choice. Also list each role step 2 dropped. Ask whether to accept as-is or change specific roles, offering the detected models plus `inherit` (the role runs on the parent session's model) as the options. For panel roles (`arena_runners`, `architect_runners`, `interrogate_reviewers`) the value is a list, and one subagent runs per entry, `inherit` entries included, so the list length sets the count. `arena_cross_judge_pool` is also a list, but Arena selects one value from it whose provider differs from the parent's when possible. `swarm_workers` is the default model for every worker unless a race or comparison assigns another model per arm.\n\nEach model entry names its `provider`, `claude`, `codex`, or `grok`, and that CLI's subscription pays for every call on it. Show how many roles each provider carries so the user can balance the subscriptions. Each model also names a `fallback` list of models on other providers. `aw-run` resolves a model whose CLI is not installed to the first installed model in that list, and retries down the list when a provider reports a usage limit.\n\n### 4. Validate\n\nEvery model written must be in the detected set. `inherit` always passes. Each `fallback` must name another model in the registry. If a chosen model is not available, stop and ask again. Then run `aw-run --resolve \u003Crole>` for every role and fix any error it prints.\n\n### 5. Write the registry\n\nWrite `~\u002F.config\u002Fagent-workflows\u002Fmodels.toml` with a `budget` line, one `[models.\u003Cname>]` table per model, and one line per role, using the role names the workflow skill uses. Overwrite the whole file so re-runs stay idempotent. Shape:\n\n```toml\n# pstack model configuration. One line per role. Delete a role to fall back to the skill default.\n# \"inherit\" as a value: the role runs on the parent session's model. Inherit entries in a panel list still count toward its fan-out.\nbudget = \"large\"\n\n[models.opus]\nprovider = \"claude\"\nmodel = \"opus\"\nfallback = [\"sol\", \"grok\"]\n\n[models.sol]\nprovider = \"codex\"\nmodel = \"gpt-6.1-sol\"\nfallback = [\"grok\", \"opus\"]\n\n[models.grok]\nprovider = \"grok\"\nmodel = \"grok-4.7\"\nfallback = [\"sol\", \"opus\"]\n\n[roles]\nfeature_refactoring = \"sol\"\nbug_fix = \"sol\"\nperf_issue = \"sol\"\nhillclimb = \"sol\"\njudgment_prose = \"opus\"\nhardest_tasks = \"opus\"\nhow_explorer = \"sol\"\nhow_explainer = \"opus\"\nwhy_investigators = \"sol\"\nwhy_synthesizer = \"opus\"\nreflect_tooling = \"sol\"\nreflect_judgment = \"opus\"\narena_runners = [\"opus\", \"sol\"]\narena_cross_judge_pool = [\"opus\", \"sol\"]\nswarm_workers = \"sol\"\narchitect_runners = [\"opus\", \"sol\"]\ninterrogate_reviewers = [\"opus\", \"sol\"]\n```\n\n### 6. Confirm\n\nTell the user the registry was written and that it applies to the next spawn in every CLI. Re-running this skill updates it.\n\n### 7. Offer a verification skill (optional)\n\nCheck whether the project has a way to drive the real app for proof (a `verify-*` skill, or an existing harness). If not, offer once: \"want a project-local verification skill, so agents can drive the app the way a user does and prove changes work? I can generate one with \u002Fcreate-verification-skill.\" On yes, invoke `\u002Fcreate-verification-skill` (resolves wherever pstack is installed: project or user skills). On no, move on without pushing.\n","# Setup pstack\n\nWrite `~\u002F.config\u002Fagent-workflows\u002Fmodels.toml`, the model registry that sets pstack's model per role. Claude Code, Codex, and Grok all read it, through `aw-run`.\n\n## Steps\n\n### 1. Detect available models\n\nDetect only for the CLIs on `PATH`. Codex: run `codex debug models` and take the `slug` of each entry with `\"visibility\": \"list\"`, with its `supported_reasoning_levels`. Claude Code: the CLI accepts the aliases `opus`, `sonnet`, `haiku`, and `fable`, or a full model name. It has no listing command, so treat those aliases as detected and ask the user to paste any full name they want. Grok: run `grok models` and take each model id it lists. Never write a model you have not confirmed is available. The value `inherit` is always valid even though it is not a detected model.\n\n### 2. Load current state\n\nThe default role-to-model mapping is the registry shape shown in step 5 below. If `~\u002F.config\u002Fagent-workflows\u002Fmodels.toml` already exists, read it and treat its `budget` and its roles as the current choices. Otherwise start from those defaults. A role not in step 5, such as `how_critics`, is from a retired role. Drop it.\n\n### 3. Budget, map, and confirm\n\n**(a) Ask for a budget.** Ask with the CLI's structured question tool when it has one, otherwise in plain text. Offer these four options with these exact labels, and name the current budget when the registry records one. With no registry, say that `large` matches the skill defaults.\n\n- `unlimited — max reasoning`\n- `large — xhigh reasoning`\n- `medium — high reasoning`\n- `small — medium reasoning`\n\n**(b) Apply it.** The registry's `budget` sets the starting effort of every role, panel entries included, to `max`, `xhigh`, `high`, or `medium`, on the ladder `max` > `xhigh` > `high` > `medium` > `low`. All three CLIs accept every level on that ladder. An entry may set its own effort and speed as `model:effort` or `model:effort:fast`, which overrides the budget. Only Codex models have a fast tier. `aw-run` applies both. `inherit` does not change.\n\n**(c) Show the roles and confirm.** Show every role with its model, provider, and effort at the chosen budget, marking any model not in the detected set as needing a choice. Also list each role step 2 dropped. Ask whether to accept as-is or change specific roles, offering the detected models plus `inherit` (the role runs on the parent session's model) as the options. For panel roles (`arena_runners`, `architect_runners`, `interrogate_reviewers`) the value is a list, and one subagent runs per entry, `inherit` entries included, so the list length sets the count. `arena_cross_judge_pool` is also a list, but Arena selects one value from it whose provider differs from the parent's when possible. `swarm_workers` is the default model for every worker unless a race or comparison assigns another model per arm.\n\nEach model entry names its `provider`, `claude`, `codex`, or `grok`, and that CLI's subscription pays for every call on it. Show how many roles each provider carries so the user can balance the subscriptions. Each model also names a `fallback` list of models on other providers. `aw-run` resolves a model whose CLI is not installed to the first installed model in that list, and retries down the list when a provider reports a usage limit.\n\n### 4. Validate\n\nEvery model written must be in the detected set. `inherit` always passes. Each `fallback` must name another model in the registry. If a chosen model is not available, stop and ask again. Then run `aw-run --resolve \u003Crole>` for every role and fix any error it prints.\n\n### 5. Write the registry\n\nWrite `~\u002F.config\u002Fagent-workflows\u002Fmodels.toml` with a `budget` line, one `[models.\u003Cname>]` table per model, and one line per role, using the role names the workflow skill uses. Overwrite the whole file so re-runs stay idempotent. Shape:\n\n```toml\n# pstack model configuration. One line per role. Delete a role to fall back to the skill default.\n# \"inherit\" as a value: the role runs on the parent session's model. Inherit entries in a panel list still count toward its fan-out.\nbudget = \"large\"\n\n[models.opus]\nprovider = \"claude\"\nmodel = \"opus\"\nfallback = [\"sol\", \"grok\"]\n\n[models.sol]\nprovider = \"codex\"\nmodel = \"gpt-6.1-sol\"\nfallback = [\"grok\", \"opus\"]\n\n[models.grok]\nprovider = \"grok\"\nmodel = \"grok-4.7\"\nfallback = [\"sol\", \"opus\"]\n\n[roles]\nfeature_refactoring = \"sol\"\nbug_fix = \"sol\"\nperf_issue = \"sol\"\nhillclimb = \"sol\"\njudgment_prose = \"opus\"\nhardest_tasks = \"opus\"\nhow_explorer = \"sol\"\nhow_explainer = \"opus\"\nwhy_investigators = \"sol\"\nwhy_synthesizer = \"opus\"\nreflect_tooling = \"sol\"\nreflect_judgment = \"opus\"\narena_runners = [\"opus\", \"sol\"]\narena_cross_judge_pool = [\"opus\", \"sol\"]\nswarm_workers = \"sol\"\narchitect_runners = [\"opus\", \"sol\"]\ninterrogate_reviewers = [\"opus\", \"sol\"]\n```\n\n### 6. Confirm\n\nTell the user the registry was written and that it applies to the next spawn in every CLI. Re-running this skill updates it.\n\n### 7. Offer a verification skill (optional)\n\nCheck whether the project has a way to drive the real app for proof (a `verify-*` skill, or an existing harness). If not, offer once: \"want a project-local verification skill, so agents can drive the app the way a user does and prove changes work? I can generate one with \u002Fcreate-verification-skill.\" On yes, invoke `\u002Fcreate-verification-skill` (resolves wherever pstack is installed: project or user skills). On no, move on without pushing.\n",{"name":5,"description":7,"disable-model-invocation":24},true,"main","cafd398384400c1a0ce1da059a134394f28a690e","skills\u002Fsetup-pstack","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 setup-pstack",{"tool":39,"command":40},"bunx","bunx skills add shreshthkapai\u002Fagent-workflows --skill setup-pstack",{"tool":42,"command":43},"pnpm","pnpm dlx skills add shreshthkapai\u002Fagent-workflows --skill setup-pstack","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshreshthkapai\u002Fagent-workflows\u002Fblob\u002Fmain\u002Fskills\u002Fsetup-pstack\u002FSKILL.md",[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"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":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"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":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7EVBBK5G5QKHXWVYHTRKJ0B","unslop","Cut AI tells from any writing.","https:\u002F\u002Fgithub.com\u002Fshreshthkapai\u002Fagent-workflows\u002Fblob\u002Fmain\u002Fskills\u002Funslop\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"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":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"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":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"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",[],[]]