[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6XC9QXTK2ABK1EVVPGZG0QR":3,"skill-same:01M6XC9QXTK2ABK1EVVPGZG0QR":81},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":6,"ownerHtmlUrl":49,"ownerBlogUrl":50,"ownerDescription":51,"updatedAt":52,"install":53,"resources":66},"01M6XC9QXTK2ABK1EVVPGZG0QR","setup-repo",null,"Configure a GitHub repository for workbuddy orchestration. Use when the user wants to set up repo automation, initialize workbuddy, create workbuddy labels\u002Fagents\u002Fworkflows, onboard a new repository, or says phrases like \"set up repo\", \"configure repo for workbuddy\", \"initialize workbuddy\", \"配置仓库\", or \"初始化workbuddy\".","Lincyaw\u002Fworkbuddy","Lincyaw","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F53161583?v=4","01M6XC87YTNETZ3AARKMHXJYJR","Aoyang Fang","01M6XC882ZSY5XBX2W6S88AGNH",2,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FLincyaw\u002Fworkbuddy\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fsetup-repo\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"setup","setup repo","repo","configure","when","labels","for","初始化","configure repo","up","use","initialize","github","onboard","SET","repository","create","workflows","automation","orchestration","2026-11-10 10:12:30",false,"---\nname: setup-repo\ndescription: Configure a GitHub repository for workbuddy orchestration. Use when the user wants to set up repo automation, initialize workbuddy, create workbuddy labels\u002Fagents\u002Fworkflows, onboard a new repository, or says phrases like \"set up repo\", \"configure repo for workbuddy\", \"initialize workbuddy\", \"配置仓库\", or \"初始化workbuddy\".\n---\n\n# Setup Repo\n\nBootstrap a repository so workbuddy can drive issue-based orchestration with GitHub labels, agent definitions, workflow files, and local runtime config.\n\nThis is a workflow skill. Use it when Codex should inspect a target repo, create or update `.github\u002Fworkbuddy\u002F` files, add `.workbuddy\u002F` to `.gitignore`, and optionally create missing GitHub labels via `gh`.\n\n## Quick workflow\n\n1. Resolve the target repository.\n   - Prefer an explicit `owner\u002Frepo` argument from the user.\n   - Otherwise detect it with `gh repo view --json nameWithOwner -q .nameWithOwner`.\n2. Inspect the current repo state.\n   - Detect the stack from files such as `go.mod`, `package.json`, `pyproject.toml`, or `Cargo.toml`.\n   - Check whether `.github\u002Fworkbuddy\u002F` already exists.\n   - Read `.gitignore` before editing it.\n   - Query existing labels with `gh label list --repo \u003Crepo> --json name -q '.[].name'`.\n3. Create or update the local workbuddy files.\n   - Add agent definitions under `.github\u002Fworkbuddy\u002Fagents\u002F`.\n   - Add workflow definitions under `.github\u002Fworkbuddy\u002Fworkflows\u002F`.\n   - Add `.github\u002Fworkbuddy\u002Fconfig.yaml`.\n   - Add `.workbuddy\u002F` to `.gitignore` if it is missing.\n4. Create missing labels in GitHub only when `gh` is authenticated and the user wants the remote repo configured now.\n5. Report exactly what changed locally and remotely, plus any skipped items.\n\n## Decision rules\n\n- Prefer updating existing workbuddy files over overwriting them blindly.\n- Keep stack-specific guidance minimal in `SKILL.md`; read `references\u002Ftemplates.md` for the exact label list and starter templates.\n- When the repo already contains agent definitions, preserve project-specific commands and only adjust the parts needed for workbuddy compatibility.\n- If `gh` auth or repo access is missing, still prepare the local files and clearly note the remote label step was not completed.\n- If the user asks about migrating Claude settings, explain that Codex skills cover reusable instructions, but Claude-style `hooks` from `.claude\u002Fsettings*.json` do not have a direct per-skill equivalent in the Codex skill format used here.\n\n## Claude-to-Codex migration notes\n\nMigrate the Claude skill itself into this Codex skill format:\n- keep only `name` and `description` in frontmatter\n- move the procedural guidance into the Markdown body\n- move detailed templates into `references\u002F`\n- add `agents\u002Fopenai.yaml` for Codex UI metadata\n\nDo not try to migrate `.claude\u002Fsettings.json` or `.claude\u002Fsettings.local.json` verbatim:\n- the permission allowlists are Claude-specific runtime configuration, not skill content\n- the `PostToolUse` hook for `Skill` is not part of the Codex `SKILL.md` contract\n- if that hook behavior still matters, re-express it as explicit instructions, a helper script, or a plugin outside the skill itself\n\n## Reference map\n\nRead only what you need:\n- `references\u002Ftemplates.md` -> required labels, agent templates, workflow templates, and config skeleton\n\n## Output checklist\n\nBefore finishing, make sure the response includes:\n- target repo used\n- detected stack\n- files created or updated\n- labels created or skipped\n- any manual follow-up needed, especially for remote GitHub steps\n","# Setup Repo\n\nBootstrap a repository so workbuddy can drive issue-based orchestration with GitHub labels, agent definitions, workflow files, and local runtime config.\n\nThis is a workflow skill. Use it when Codex should inspect a target repo, create or update `.github\u002Fworkbuddy\u002F` files, add `.workbuddy\u002F` to `.gitignore`, and optionally create missing GitHub labels via `gh`.\n\n## Quick workflow\n\n1. Resolve the target repository.\n   - Prefer an explicit `owner\u002Frepo` argument from the user.\n   - Otherwise detect it with `gh repo view --json nameWithOwner -q .nameWithOwner`.\n2. Inspect the current repo state.\n   - Detect the stack from files such as `go.mod`, `package.json`, `pyproject.toml`, or `Cargo.toml`.\n   - Check whether `.github\u002Fworkbuddy\u002F` already exists.\n   - Read `.gitignore` before editing it.\n   - Query existing labels with `gh label list --repo \u003Crepo> --json name -q '.[].name'`.\n3. Create or update the local workbuddy files.\n   - Add agent definitions under `.github\u002Fworkbuddy\u002Fagents\u002F`.\n   - Add workflow definitions under `.github\u002Fworkbuddy\u002Fworkflows\u002F`.\n   - Add `.github\u002Fworkbuddy\u002Fconfig.yaml`.\n   - Add `.workbuddy\u002F` to `.gitignore` if it is missing.\n4. Create missing labels in GitHub only when `gh` is authenticated and the user wants the remote repo configured now.\n5. Report exactly what changed locally and remotely, plus any skipped items.\n\n## Decision rules\n\n- Prefer updating existing workbuddy files over overwriting them blindly.\n- Keep stack-specific guidance minimal in `SKILL.md`; read `references\u002Ftemplates.md` for the exact label list and starter templates.\n- When the repo already contains agent definitions, preserve project-specific commands and only adjust the parts needed for workbuddy compatibility.\n- If `gh` auth or repo access is missing, still prepare the local files and clearly note the remote label step was not completed.\n- If the user asks about migrating Claude settings, explain that Codex skills cover reusable instructions, but Claude-style `hooks` from `.claude\u002Fsettings*.json` do not have a direct per-skill equivalent in the Codex skill format used here.\n\n## Claude-to-Codex migration notes\n\nMigrate the Claude skill itself into this Codex skill format:\n- keep only `name` and `description` in frontmatter\n- move the procedural guidance into the Markdown body\n- move detailed templates into `references\u002F`\n- add `agents\u002Fopenai.yaml` for Codex UI metadata\n\nDo not try to migrate `.claude\u002Fsettings.json` or `.claude\u002Fsettings.local.json` verbatim:\n- the permission allowlists are Claude-specific runtime configuration, not skill content\n- the `PostToolUse` hook for `Skill` is not part of the Codex `SKILL.md` contract\n- if that hook behavior still matters, re-express it as explicit instructions, a helper script, or a plugin outside the skill itself\n\n## Reference map\n\nRead only what you need:\n- `references\u002Ftemplates.md` -> required labels, agent templates, workflow templates, and config skeleton\n\n## Output checklist\n\nBefore finishing, make sure the response includes:\n- target repo used\n- detected stack\n- files created or updated\n- labels created or skipped\n- any manual follow-up needed, especially for remote GitHub steps\n",{"name":5,"description":7},"main","b9778c800f442939b879c9a556dfb8d6f4a40971",".codex\u002Fskills\u002Fsetup-repo",1,"https:\u002F\u002Fgithub.com\u002FLincyaw\u002Fworkbuddy","https:\u002F\u002Fgithub.com\u002FLincyaw","http:\u002F\u002Fprofile.aoyangfang.top\u002F","Student in The Chinese University of Hong Kong, Shenzhen","2026-06-08 13:33:51",{"source":8,"skillName":5,"commands":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add Lincyaw\u002Fworkbuddy --skill setup-repo",{"tool":59,"command":60},"bunx","bunx skills add Lincyaw\u002Fworkbuddy --skill setup-repo",{"tool":62,"command":63},"pnpm","pnpm dlx skills add Lincyaw\u002Fworkbuddy --skill setup-repo","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FLincyaw\u002Fworkbuddy\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fsetup-repo\u002FSKILL.md",true,[67,73,77],{"path":68,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":71,"sourceHtmlUrl":72},"agents\u002Fopenai.yaml","REFERENCE","参考文档",190,"https:\u002F\u002Fgithub.com\u002FLincyaw\u002Fworkbuddy\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fsetup-repo\u002Fagents\u002Fopenai.yaml",{"path":74,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":75,"sourceHtmlUrl":76},"references\u002Ftemplates.md",4450,"https:\u002F\u002Fgithub.com\u002FLincyaw\u002Fworkbuddy\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fsetup-repo\u002Freferences\u002Ftemplates.md",{"path":78,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":79,"sourceHtmlUrl":80},"WHY-TWO-COPIES.md",668,"https:\u002F\u002Fgithub.com\u002FLincyaw\u002Fworkbuddy\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fsetup-repo\u002FWHY-TWO-COPIES.md",[82,107,145,161,180,206],{"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":39},"01M6XCBSW1MMEAWEF38VX9NH3E","workbuddy-guide","Explain and operate workbuddy: what it is, which command to reach for, and where to find deeper references. **Trigger whenever the user mentions 'workbuddy' in any context** — including operational requests (register\u002Fonboard a repo, add\u002Fbind a worker, 注册仓库, 加仓库, 接入新仓库, onboard repo, set up worker), explanatory questions (how to use workbuddy, workbuddy guide, teach me workbuddy, 怎么用workbuddy, 使用指南), deployment\u002Frunning\u002Foperating\u002Fdebugging workbuddy, and questions about how issues\u002Ftasks are scheduled or how dependencies between issues work (depends_on, blocked, dependency gate, 依赖, 调度, 排队, '为什么没派发'), and questions about parallel-development workflows (rollouts:N fan-out, synthesize\u002Fsynthesis reduce step, cherry-pick, '并行开发', '多个方案', 'rollout'). Invoke this skill before running workbuddy CLI commands so the documented onboarding flow (coordinator register + worker repos add) and the dependency\u002Fscheduling model aren't re-derived from scratch.","https:\u002F\u002Fgithub.com\u002FLincyaw\u002Fworkbuddy\u002Fblob\u002Fmain\u002Fplugins\u002Fworkbuddy\u002Fskills\u002Fworkbuddy-guide\u002FSKILL.md",[],[89,90,91,92,33,93,94,28,95,96,97,98,99,100,101,102,103,104,105,106],"guide","workbuddy guide","debugging","issues","model","pick","rollouts","deeper","worker","bind","how to","operating","coordinator","re","operate","which","scheduled","invoke",{"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":126,"publishedAt":39},"01M6XCBM7B95PB3Q6PHZ3TCM7F","web-debug","Validate the workbuddy webui (SPA + auth + JSON API) end-to-end on the same machine workbuddy runs on, using browser-use's headless harness. Use when the user says 'verify the frontend', 'test the SPA', 'check dashboard loads', '前端验证', '验下 webui', or after merging changes that touch internal\u002Fwebui, web\u002F, or the auth\u002Fcookie path.","https:\u002F\u002Fgithub.com\u002FLincyaw\u002Fworkbuddy\u002Fblob\u002Fmain\u002Fplugins\u002Fworkbuddy\u002Fskills\u002Fweb-debug\u002FSKILL.md",[113,118,121],{"categoryNo":114,"categoryName":115,"taxonomyType":116,"taxonomyTypeDesc":117},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",{"categoryNo":119,"categoryName":120,"taxonomyType":116,"taxonomyTypeDesc":117},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":122,"categoryName":123,"taxonomyType":124,"taxonomyTypeDesc":125},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[127,128,129,130,131,132,133,134,135,29,136,137,138,139,140,141,142,143,144,23],"web","debug","web debug","frontend","auth","browser","harness","api","check","webui","spa","end","machine","touch","loads","headless","browser-use","using browser",{"skillNo":146,"name":5,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":153,"publishedAt":39},"01M6XCBFR925WJSWEYVHGSTT56","Configure a GitHub repository for workbuddy orchestration — creates labels, the two canonical agent configs (dev + review), workflow definitions, issue templates, and config.yaml. Use when the user says 'set up repo', 'configure repo for workbuddy', 'initialize workbuddy', '配置仓库', '初始化workbuddy', or wants to onboard a new repo.","https:\u002F\u002Fgithub.com\u002FLincyaw\u002Fworkbuddy\u002Fblob\u002Fmain\u002Fplugins\u002Fworkbuddy\u002Fskills\u002Fsetup-repo\u002FSKILL.md",[150],{"categoryNo":151,"categoryName":152,"taxonomyType":116,"taxonomyTypeDesc":117},"01JBSEEDCAT000000000000023","Skill与智能体开发",[19,20,21,154,38,155,156,157,34,33,22,30,28,158,159,26,160,25,24,23],"review","workflow","config","dev","issue","new repo","canonical",{"skillNo":162,"name":163,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":165,"categories":166,"keywords":167,"publishedAt":39},"01M6XCBAEPZQTAS5FZYCPDEGAG","pipeline-monitor","Monitor the workbuddy agent pipeline, detect stuck issues, zombie processes, and missed redispatches. Works for both the 3-unit bundle (supervisor + coordinator + worker) and single-process `serve`. Use when the user says 'monitor the pipeline', 'check workbuddy status', '监工', '看看跑完了没', or asks to watch issue progress.","https:\u002F\u002Fgithub.com\u002FLincyaw\u002Fworkbuddy\u002Fblob\u002Fmain\u002Fplugins\u002Fworkbuddy\u002Fskills\u002Fpipeline-monitor\u002FSKILL.md",[],[168,169,170,171,92,172,135,29,158,173,97,174,175,176,177,101,178,25,179,23],"monitor","pipeline","pipeline monitor","status","supervisor","missed","watch","progress","detect","unit","agent pipeline","single",{"skillNo":181,"name":182,"nameZh":6,"description":183,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":184,"categories":185,"keywords":189,"publishedAt":39},"01M6XCB5RTYNH7QK9RQ5Z4B6NK","merge-flow","Merge a batch of approved workbuddy PRs into main: order them, resolve conflicts against design intent, validate post-merge health, and report. Use when the user asks to 'merge the batch', 'merge approved PRs', 'integrate finished issues', '批量合并', '处理冲突'; or when the merge-agent is invoked.","https:\u002F\u002Fgithub.com\u002FLincyaw\u002Fworkbuddy\u002Fblob\u002Fmain\u002Fplugins\u002Fworkbuddy\u002Fskills\u002Fmerge-flow\u002FSKILL.md",[186],{"categoryNo":187,"categoryName":188,"taxonomyType":116,"taxonomyTypeDesc":117},"01JBSEEDCAT000000000000015","视觉设计",[190,191,192,193,194,195,92,196,197,198,29,199,200,201,202,44,203,204,205,23],"merge","flow","merge flow","design","validate","report","batch","health","user","integrate","resolve conflicts","conflicts","intent","post","design intent","prs",{"skillNo":207,"name":208,"nameZh":6,"description":209,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":210,"categories":211,"keywords":215,"publishedAt":39},"01M6XCB29F96RJ02Z3BXTAVYSB","deploy","Workbuddy deployment topology guide — explains the 3-unit bundle (supervisor + coordinator + worker), the rolling-restart property, and the cutover from the legacy single-process `serve` install. Use when the user says 'how should I deploy workbuddy', 'install workbuddy as a service', 'switch to bundle', 'rolling restart', '部署 workbuddy', '升级到 bundle'.","https:\u002F\u002Fgithub.com\u002FLincyaw\u002Fworkbuddy\u002Fblob\u002Fmain\u002Fplugins\u002Fworkbuddy\u002Fskills\u002Fdeploy\u002FSKILL.md",[212],{"categoryNo":213,"categoryName":214,"taxonomyType":116,"taxonomyTypeDesc":117},"01JBSEEDCAT000000000000011","运维与部署",[208,216,217,218,172,219,220,89,29,221,222,97,223,224,225,226,177,101,179,23],"deployment","topology","how","process","install","Legacy","switch","service","as","bundle","serve"]