[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6BVQ3EZQCC7V0ND6BYBY6CS":3,"skill-same:01M6BVQ3EZQCC7V0ND6BYBY6CS":106},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":33,"linkOnly":34,"markdownContent":35,"markdownBody":36,"frontMatter":37,"refName":38,"commitSha":39,"skillDirectory":40,"forksCount":13,"repositoryHtmlUrl":41,"repositoryHomepageUrl":6,"ownerHtmlUrl":42,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":43,"install":44,"resources":57},"01M6BVQ3EZQCC7V0ND6BYBY6CS","orca-team",null,"Show supervised Orca workers in colored panes, close ended worker panes and terminals, and detect stalled workers with worker-watch. Complements Orca's orchestration skill for projects using the agent team.","mingster\u002Fdotfiles","mingster","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F528506?v=4","01M6BVP9E23T80TBZM7S0F94RG","01M6BVP9JK6JMSX0SZ2G1VMEDW",1,"MIT","https:\u002F\u002Fgithub.com\u002Fmingster\u002Fdotfiles\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Forca-team\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32],"team","orca team","orchestration","projects","panes","workers","show","agent team","worker","watch","close","detect","with","for","supervised","2026-11-10 10:12:30",false,"---\nname: orca-team\ndescription: >-\n  Show supervised Orca workers in colored panes, close ended worker panes and\n  terminals, and detect stalled workers with worker-watch. Complements Orca's\n  orchestration skill for projects using the agent team.\n---\n\n# Orca team tooling\n\nThis skill complements Orca's `orchestration` skill. Load its version-matched guide\nwith `orca skills get orchestration` before coordinating workers; Orca owns that\nskill and its lifecycle commands. Dotfiles owns the pane and watch helpers here.\n\nIn a project with the agent team (it has `.claude\u002Fagents\u002Felon.md`), the default Orca coordinator\nis the `elon` role. Elon owns the cross-project objective, cross-role DAG, dispatch and completion\nreview. `tech-lead` is a teammate that coordinates engineering integration and reports to Elon. Keep\nthis split explicit in task messages and completion reports; CEO recommendations never replace\nhuman-owner approval or required independent review.\n\n`worker-watch.sh \u003Crun_id>` next to this file flags STOPPED (provider limit or network error),\nIDLE (empty input prompt without busy markers), BLOCKED_DIALOG (trust dialog), BLOCKED_APPROVAL (pending tool approval prompt) and LOW_CONTEXT;\neach exits 4, while OK exits 0. Run it as `~\u002F.claude\u002Fskills\u002Forca-team\u002Fworker-watch.sh`.\nOn IDLE or network STOPPED, send the worker a resume message with\n`orca terminal send --terminal \u003Chandle> --text \"Resume the assigned task and report its outcome.\" --enter`\nat once; never leave it waiting.\n`worker-watch.test.sh` is its test.\n\n`worker-panes.sh \u003Crun_id> \u003Ccoordinator_terminal> [dispatch_id ...]` shows workers as colored split panes in the\ncoordinator's tab (coordinator left; the first pane splits it to the right, later panes stack in that right column, and the coordinator is split again only when no worker pane is left) (Orca cannot start a worker as a split pane). Each pane runs `worker-pane.sh \u003Cdispatch_id> [color]`,\na read-only live mirror of that worker's screen; it shows the final status line when the dispatch ends, waits about 10 seconds (`ORCA_PANE_CLOSE_DELAY`) and closes its own terminal through `ORCA_TERMINAL_HANDLE` (skipped when unset), verifying that the handle disappears from `orca terminal list` and retrying failed or lingering closes after 5, 15, 30, then 60 seconds for up to 30 minutes in a plain shell loop (CLI calls are bounded too), so a pane whose split timed out and was never recorded does not linger. A failing `worker-show` keeps it running. Each pane's handle is recorded in `~\u002F.cache\u002Forca-worker-panes\u002F\u003Cdispatch_id>`. Run it as\n`~\u002F.claude\u002Fskills\u002Forca-team\u002Fworker-panes.sh`; `worker-panes.test.sh` and `worker-pane.test.sh` are its tests.\nThe moment the coordinator validates a worker's report (or the worker fails), it runs `~\u002F.claude\u002Fskills\u002Forca-team\u002Fworker-pane-close.sh --release \u003Cdispatch_id>`. That runs `worker-release`, records a released marker (Orca keeps external terminals on release, so the marker lets a later sweep, wrap-up's included, close them while the worktree still exists) and closes the recorded pane and every terminal of the dispatch still in `orca terminal list`: the handles `worker-show` reports (agent and setup terminals) and any terminal whose `worktreePath` matches the linked git worktree the worker created or reused (its `.git` must be a file, so main checkouts are matched by worker handle only), so a pane whose split timed out is covered too (`worker-panes.sh` records the one new pane that appears in the tab after a timed out split). A dispatch still running keeps its terminals, and so does a terminal that any dispatch not in a final state also uses (a retry started with `--retry-of --terminal` reuses the failed dispatch's terminal; the script reads every page of `worker-list` and keeps such a handle with its record), and the owner's own sessions and other projects' terminals are never matched. Records are removed only after verified disappearance; unfinished closes remain recorded for a later sweep. Only positively ended dispatches authorize closure, including recorded panes: state `succeeded`, `completed`, `failed`, `cancelled` or `released`, stage `released`, or liveness `exited`. `worker_state.py` reads the flat Orca JSON first and the older nested shape as a fallback. Release closes at most the agent terminal, so after a confirmed release the script closes the remaining exact handles itself (never the agent terminal, never the caller's own `ORCA_TERMINAL_HANDLE`). Run with no arguments on every wake to close recorded panes of ended dispatches whose linked worktree no longer exists (a settled dispatch whose worktree is still there may be on a correction pass, so the sweep keeps it; explicit ids skip this check) and discover leftover terminals via every page of `worker-list`, restricting newly discovered dispatches to the current project's identity from live terminal metadata (discovery is skipped if that identity is unknown), using the same worker-handle and exact linked worktree matching rules; `worker-pane-close.test.sh` is its test.\nPane color comes from the role in the task title (`\u003Crole> - \u003Cjob>`), looked up in `role-colors.tsv` next to the scripts (unknown role: grey), so always start the title with the role name. Add a line there for a new role.\n","# Orca team tooling\n\nThis skill complements Orca's `orchestration` skill. Load its version-matched guide\nwith `orca skills get orchestration` before coordinating workers; Orca owns that\nskill and its lifecycle commands. Dotfiles owns the pane and watch helpers here.\n\nIn a project with the agent team (it has `.claude\u002Fagents\u002Felon.md`), the default Orca coordinator\nis the `elon` role. Elon owns the cross-project objective, cross-role DAG, dispatch and completion\nreview. `tech-lead` is a teammate that coordinates engineering integration and reports to Elon. Keep\nthis split explicit in task messages and completion reports; CEO recommendations never replace\nhuman-owner approval or required independent review.\n\n`worker-watch.sh \u003Crun_id>` next to this file flags STOPPED (provider limit or network error),\nIDLE (empty input prompt without busy markers), BLOCKED_DIALOG (trust dialog), BLOCKED_APPROVAL (pending tool approval prompt) and LOW_CONTEXT;\neach exits 4, while OK exits 0. Run it as `~\u002F.claude\u002Fskills\u002Forca-team\u002Fworker-watch.sh`.\nOn IDLE or network STOPPED, send the worker a resume message with\n`orca terminal send --terminal \u003Chandle> --text \"Resume the assigned task and report its outcome.\" --enter`\nat once; never leave it waiting.\n`worker-watch.test.sh` is its test.\n\n`worker-panes.sh \u003Crun_id> \u003Ccoordinator_terminal> [dispatch_id ...]` shows workers as colored split panes in the\ncoordinator's tab (coordinator left; the first pane splits it to the right, later panes stack in that right column, and the coordinator is split again only when no worker pane is left) (Orca cannot start a worker as a split pane). Each pane runs `worker-pane.sh \u003Cdispatch_id> [color]`,\na read-only live mirror of that worker's screen; it shows the final status line when the dispatch ends, waits about 10 seconds (`ORCA_PANE_CLOSE_DELAY`) and closes its own terminal through `ORCA_TERMINAL_HANDLE` (skipped when unset), verifying that the handle disappears from `orca terminal list` and retrying failed or lingering closes after 5, 15, 30, then 60 seconds for up to 30 minutes in a plain shell loop (CLI calls are bounded too), so a pane whose split timed out and was never recorded does not linger. A failing `worker-show` keeps it running. Each pane's handle is recorded in `~\u002F.cache\u002Forca-worker-panes\u002F\u003Cdispatch_id>`. Run it as\n`~\u002F.claude\u002Fskills\u002Forca-team\u002Fworker-panes.sh`; `worker-panes.test.sh` and `worker-pane.test.sh` are its tests.\nThe moment the coordinator validates a worker's report (or the worker fails), it runs `~\u002F.claude\u002Fskills\u002Forca-team\u002Fworker-pane-close.sh --release \u003Cdispatch_id>`. That runs `worker-release`, records a released marker (Orca keeps external terminals on release, so the marker lets a later sweep, wrap-up's included, close them while the worktree still exists) and closes the recorded pane and every terminal of the dispatch still in `orca terminal list`: the handles `worker-show` reports (agent and setup terminals) and any terminal whose `worktreePath` matches the linked git worktree the worker created or reused (its `.git` must be a file, so main checkouts are matched by worker handle only), so a pane whose split timed out is covered too (`worker-panes.sh` records the one new pane that appears in the tab after a timed out split). A dispatch still running keeps its terminals, and so does a terminal that any dispatch not in a final state also uses (a retry started with `--retry-of --terminal` reuses the failed dispatch's terminal; the script reads every page of `worker-list` and keeps such a handle with its record), and the owner's own sessions and other projects' terminals are never matched. Records are removed only after verified disappearance; unfinished closes remain recorded for a later sweep. Only positively ended dispatches authorize closure, including recorded panes: state `succeeded`, `completed`, `failed`, `cancelled` or `released`, stage `released`, or liveness `exited`. `worker_state.py` reads the flat Orca JSON first and the older nested shape as a fallback. Release closes at most the agent terminal, so after a confirmed release the script closes the remaining exact handles itself (never the agent terminal, never the caller's own `ORCA_TERMINAL_HANDLE`). Run with no arguments on every wake to close recorded panes of ended dispatches whose linked worktree no longer exists (a settled dispatch whose worktree is still there may be on a correction pass, so the sweep keeps it; explicit ids skip this check) and discover leftover terminals via every page of `worker-list`, restricting newly discovered dispatches to the current project's identity from live terminal metadata (discovery is skipped if that identity is unknown), using the same worker-handle and exact linked worktree matching rules; `worker-pane-close.test.sh` is its test.\nPane color comes from the role in the task title (`\u003Crole> - \u003Cjob>`), looked up in `role-colors.tsv` next to the scripts (unknown role: grey), so always start the title with the role name. Add a line there for a new role.\n",{"name":5,"description":7},"main","be82170d16c77d2edb352ca2dc16e5dbc36d3e56",".agents\u002Fskills\u002Forca-team","https:\u002F\u002Fgithub.com\u002Fmingster\u002Fdotfiles","https:\u002F\u002Fgithub.com\u002Fmingster","2026-11-15 03:23:26",{"source":8,"skillName":5,"commands":45,"prompt":55,"zipAvailable":56},[46,49,52],{"tool":47,"command":48},"npx","npx skills add mingster\u002Fdotfiles --skill orca-team",{"tool":50,"command":51},"bunx","bunx skills add mingster\u002Fdotfiles --skill orca-team",{"tool":53,"command":54},"pnpm","pnpm dlx skills add mingster\u002Fdotfiles --skill orca-team","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmingster\u002Fdotfiles\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Forca-team\u002FSKILL.md",true,[58,64,70,74,78,82,86,90,94,98,102],{"path":59,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":62,"sourceHtmlUrl":63},"role-colors.tsv","OTHER","其他",170,"https:\u002F\u002Fgithub.com\u002Fmingster\u002Fdotfiles\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Forca-team\u002Frole-colors.tsv",{"path":65,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":68,"sourceHtmlUrl":69},"worker_state.py","SCRIPT","脚本",2183,"https:\u002F\u002Fgithub.com\u002Fmingster\u002Fdotfiles\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Forca-team\u002Fworker_state.py",{"path":71,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":72,"sourceHtmlUrl":73},"worker-pane-close.sh",15050,"https:\u002F\u002Fgithub.com\u002Fmingster\u002Fdotfiles\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Forca-team\u002Fworker-pane-close.sh",{"path":75,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":76,"sourceHtmlUrl":77},"worker-pane-close.test.sh",41409,"https:\u002F\u002Fgithub.com\u002Fmingster\u002Fdotfiles\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Forca-team\u002Fworker-pane-close.test.sh",{"path":79,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":80,"sourceHtmlUrl":81},"worker-pane-retry.sh",1649,"https:\u002F\u002Fgithub.com\u002Fmingster\u002Fdotfiles\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Forca-team\u002Fworker-pane-retry.sh",{"path":83,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":84,"sourceHtmlUrl":85},"worker-pane.sh",3471,"https:\u002F\u002Fgithub.com\u002Fmingster\u002Fdotfiles\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Forca-team\u002Fworker-pane.sh",{"path":87,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":88,"sourceHtmlUrl":89},"worker-pane.test.sh",5717,"https:\u002F\u002Fgithub.com\u002Fmingster\u002Fdotfiles\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Forca-team\u002Fworker-pane.test.sh",{"path":91,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":92,"sourceHtmlUrl":93},"worker-panes.sh",4470,"https:\u002F\u002Fgithub.com\u002Fmingster\u002Fdotfiles\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Forca-team\u002Fworker-panes.sh",{"path":95,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":96,"sourceHtmlUrl":97},"worker-panes.test.sh",7224,"https:\u002F\u002Fgithub.com\u002Fmingster\u002Fdotfiles\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Forca-team\u002Fworker-panes.test.sh",{"path":99,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":100,"sourceHtmlUrl":101},"worker-watch.sh",6348,"https:\u002F\u002Fgithub.com\u002Fmingster\u002Fdotfiles\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Forca-team\u002Fworker-watch.sh",{"path":103,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":104,"sourceHtmlUrl":105},"worker-watch.test.sh",10350,"https:\u002F\u002Fgithub.com\u002Fmingster\u002Fdotfiles\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Forca-team\u002Fworker-watch.test.sh",[107,136,167,182,200,220],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":118,"publishedAt":33},"01M70M8J3PA9F7TJA4DK95GE8N","workflow-from-chats","Extract durable working preferences from recent Cursor chats and convert them into skills, rules, or workflow docs. Use when asked to learn preferences, mine feedback, personalize workflows, or generate team\u002Fperson-specific agent guidance.","https:\u002F\u002Fgithub.com\u002Fmingster\u002Fdotfiles\u002Fblob\u002Fmain\u002Ftemplates\u002Fagent-team\u002F.agents\u002Fskills\u002Fworkflow-from-chats\u002FSKILL.md",[113],{"categoryNo":114,"categoryName":115,"taxonomyType":116,"taxonomyTypeDesc":117},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[119,120,18,121,122,123,124,125,126,127,128,129,130,131,132,133,134,135],"workflow from chats","workflow","feedback","workflows","Rules","use","preferences","guidance","person","cursor","generate","mine","docs","when","extract","learn","convert",{"skillNo":137,"name":138,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":140,"categories":141,"keywords":147,"publishedAt":33},"01M70M8DK87GX45FFZCC840SW2","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\u002Fmingster\u002Fdotfiles\u002Fblob\u002Fmain\u002Ftemplates\u002Fagent-team\u002F.agents\u002Fskills\u002Fwhy\u002FSKILL.md",[142],{"categoryNo":143,"categoryName":144,"taxonomyType":145,"taxonomyTypeDesc":146},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[138,148,149,150,151,152,153,154,155,156,157,158,159,160,161,162,163,164,165,166],"product analytics","design","work","product","time","error tracking","how","tracker","read","issue","data","analytics","source","infrastructure","returns","warehouse","parallel","observability","error",{"skillNo":168,"name":169,"nameZh":6,"description":170,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":171,"categories":172,"keywords":173,"publishedAt":33},"01M70M89EYB7RB4WT9EBQ19VEW","what-did-i-get-done","Summarize authored commits over a user-specified time period into a concise update","https:\u002F\u002Fgithub.com\u002Fmingster\u002Fdotfiles\u002Fblob\u002Fmain\u002Ftemplates\u002Fagent-team\u002F.agents\u002Fskills\u002Fwhat-did-i-get-done\u002FSKILL.md",[],[174,175,176,177,178,179,152,180,181],"done","what did i get done","get","summarize","user","update","commits","concise",{"skillNo":183,"name":184,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":186,"categories":187,"keywords":188,"publishedAt":33},"01M70M887Z6CVVHAM294BC9SG3","weekly-review","Produce a weekly synthesis of authored commits with highlights by bugfix, tech debt, and net-new work","https:\u002F\u002Fgithub.com\u002Fmingster\u002Fdotfiles\u002Fblob\u002Fmain\u002Ftemplates\u002Fagent-team\u002F.agents\u002Fskills\u002Fweekly-review\u002FSKILL.md",[],[189,190,191,192,193,194,195,196,197,198,180,199,150,30],"weekly","review","weekly review","produce","Synthesis","weekly synthesis","debt","new","tech debt","bugfix","tech",{"skillNo":201,"name":202,"nameZh":6,"description":203,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":204,"categories":205,"keywords":206,"publishedAt":33},"01M70M86M3WNW7S7TZ1NVKSGT7","verify-this","Verify a claim with fresh local evidence: restate it falsifiably, capture baseline and treatment, compare artifacts, and return VERIFIED, NOT VERIFIED, or INCONCLUSIVE.","https:\u002F\u002Fgithub.com\u002Fmingster\u002Fdotfiles\u002Fblob\u002Fmain\u002Ftemplates\u002Fagent-team\u002F.agents\u002Fskills\u002Fverify-this\u002FSKILL.md",[],[207,208,209,210,211,212,213,214,215,216,217,218,219,30],"verify","verify this","fresh","it","artifacts","capture","restate","verified","claim","local","baseline","evidence","compare",{"skillNo":221,"name":222,"nameZh":6,"description":223,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":224,"categories":225,"keywords":226,"publishedAt":33},"01M70M84C3MN7ASJ0HBFAKT5Z6","typescript-best-practices","TypeScript best practices. Use when reading or editing any .ts or .tsx file.","https:\u002F\u002Fgithub.com\u002Fmingster\u002Fdotfiles\u002Fblob\u002Fmain\u002Ftemplates\u002Fagent-team\u002F.agents\u002Fskills\u002Ftypescript-best-practices\u002FSKILL.md",[],[227,228,229,230,231,132,124,232,233,234],"best practices","typescript best practices","typescript","file","editing","tsx","true","reading"]