[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DZS3FEK5PCAK0EEXRKDMX6":3,"skill-same:01M6DZS3FEK5PCAK0EEXRKDMX6":122},{"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":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":52,"repositoryHtmlUrl":53,"repositoryHomepageUrl":54,"ownerHtmlUrl":55,"ownerBlogUrl":56,"ownerDescription":6,"updatedAt":57,"install":58,"resources":71},"01M6DZS3FEK5PCAK0EEXRKDMX6","orbit",null,"Creates, executes and reviews Orbit tasks; searches task history and friction records; records evidence. Use for an assigned task or task ID, task authoring, `orbit.task`\u002F`orbit.search` MCP tools, `orbit tool run`, task records under `.orbit\u002F`, or friction. Use orbit-orchestrate for `orbit run` dispatch, drains and failed `jrun-*` runs, and orbit-setup for installing or configuring a machine.","constellation-works\u002Forbit","constellation-works","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F322971908?v=4","01M6DZR7HBGAB3RYGA69FES9BR","Constellation-Works","01M6DZR7NKYTEFH424SK4BHCX3",20,"MIT","https:\u002F\u002Fgithub.com\u002Fconstellation-works\u002Forbit\u002Fblob\u002Fagent-main\u002Fplugin\u002Fskills\u002Forbit\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[5,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"tool","for","machine","records","reviews","mcp tools","friction","dispatch","id","task","use","history","evidence","Tools","authoring","run","tasks","MCP","search","orchestrate","2026-11-10 10:12:30",false,"---\nname: orbit\ndescription: Creates, executes and reviews Orbit tasks; searches task history and friction records; records evidence. Use for an assigned task or task ID, task authoring, `orbit.task`\u002F`orbit.search` MCP tools, `orbit tool run`, task records under `.orbit\u002F`, or friction. Use orbit-orchestrate for `orbit run` dispatch, drains and failed `jrun-*` runs, and orbit-setup for installing or configuring a machine.\n---\n\n# Orbit\n\nWork through the authoritative task record and leave verifiable results.\nRead only the reference needed for the current action; this is not a reading\nchecklist. An injected task snapshot is your starting context.\n\n## Operator attention\n\nStart an orchestrator or on-call inspection with `orbit attention --json` or the read-only `orbit.attention` tool. Task-level kinds report pilot warnings and holds, human-waiting blocks, open decisions and settled reviews; runtime kinds report failed or stuck runs and possibly stale claims (Operator capability required); `ci_red` reports a red base branch and `friction_untriaged` lists open friction records; `host_unhealthy` reports failing doctor checks and, across registered hosts, hosts that cannot be read. Read `degraded` before interpreting an empty result. See [Attention](references\u002Fattention.md) for filters, local scopes, suggested actions and the delta cursor.\n\n## Connect and act\n\n- With MCP, discover its tools. In a managed activity, use the injected task\n  and inherited workspace binding; `orbit.workspace.list` may be outside the\n  activity allowlist. In an unbound session, call `orbit_workspace_list` and\n  copy the returned selector, including host qualification when federated.\n  For a CLI-only installation, inspect `orbit workspace list\u002Fshow` on the\n  intended host and use that registered workspace. Never substitute another\n  host or shadow store.\n- Use registered tools: MCP `orbit_task_show`, or the installed CLI's\n  `orbit tool run orbit.task.show --input '{\"id\":\"\u003Ctask-id>\"}'`.\n  Provenance comes from the session, not a `model` argument. Use `fields` for\n  compact reads. The advertised schema decides which inputs and tools are available.\n- Update task state through tools, not files under `.orbit\u002F`. Creating a task\n  does not authorize dispatch or completion. In a managed activity, implement\n  the assigned work; the pipeline owns delivery and lifecycle transitions.\n- Verify artifacts, task\u002Frun state, diffs and checks. Agent messages are\n  advisory. Do not report skipped validation as passing or merged as deployed.\n- To check a UI change in a browser, use the host's headless browser kit:\n  when it is verified, your environment carries `PLAYWRIGHT_MODULE`,\n  `PLAYWRIGHT_BROWSERS_PATH` and `ORBIT_BROWSER_KIT_ENV`. Source\n  `\"$ORBIT_BROWSER_KIT_ENV\"` in the shell that runs the check\n  ([Task execution](references\u002Ftask-execution.md#checking-a-ui-in-a-browser)).\n- Use the installed `orbit` binary, never `cargo run -- ...`. Bare\n  `orbit task ...` subcommands are the human surface and skip agent\n  provenance; agents call `orbit tool run orbit.task.*`. Task IDs come from\n  `orbit.task.add`; never invent one. Only a human can force an off-table\n  transition (`orbit task update --force` or the dashboard); `orbit.task.update`\n  and MCP have no `force`.\n\n## Desktop navigation\n\nWhen the connected client advertises `orbit_ui`, use its read-only `open` and\n`inspect` actions to open the control center or a selected task\u002Frun.\nDiscover workspaces first and copy the exact returned selector; pass `workspace`\nand public `id` together, with `kind: run` for a run. Keep ordinary task tools\navailable when the client cannot render the UI.\n\nThe panel can capture proposed tasks, edit allowed fields, comment and record\nreviews through separately guarded desktop tools. A click or conversation\nreference grants no operator authority. Reread authoritative task state before\nacting on a copied reference. Keep the same request ID\u002Fpayload when a write's\noutcome is unknown; only a definite refusal permits a corrected fresh request.\nNative support depends on the actual desktop build and connection; an installed\nplugin or passing protocol test alone does not prove rendering\u002Fcontext delivery.\n\n## Choose the reference\n\n| Need | Read |\n|---|---|\n| Implement an assigned task | [Task execution](references\u002Ftask-execution.md) |\n| Prepare configured agent-filled pull request sections | [Agent-filled PR sections](references\u002Ftask-execution.md#agent-filled-pr-sections) |\n| Set dependencies, relations or validation tools | [Task fields](references\u002Ftask-fields.md) |\n| Create or revise a task | [Task authoring](references\u002Ftask-authoring.md) |\n| Review a delivered diff | [Task review](references\u002Ftask-review.md) |\n| Find prior tasks or frictions | [Search](references\u002Fsearch.md) |\n| Run and interpret task-flow analytics | [Task-flow analytics](references\u002Fconcepts.md#task-flow-analytics) |\n| Record a concrete recurring obstacle | [Friction](references\u002Ffriction.md) |\n| Record and inspect repeated capability costs | [Evolution records](references\u002Ftool-surface.md#evolution-records) |\n| Resolve tool transport, permissions or workspace routing | [Tool surface](references\u002Ftool-surface.md) |\n| Understand Orbit nouns | [Concepts](references\u002Fconcepts.md) |\n| Act as a manager for resident mandates | [Manager](references\u002Fmanager.md) |\n| Run one resident cycle for a mandate | [Resident cycle](references\u002Fresident-cycle.md) |\n| Single-owner distributed drain setup or claimed-attempt recovery | [Distributed drain](references\u002Fsetup\u002Fdistributed-drain.md) |\n\nFor dispatch, backlog supervision and failed runs, use\n[orbit-orchestrate](..\u002Forbit-orchestrate\u002FSKILL.md). For machine, repository,\nMCP, automation or upgrade configuration, use [orbit-setup](..\u002Forbit-setup\u002FSKILL.md).\n\n## Lifecycle essentials\n\nNormal delivery is `proposed → backlog → in-progress → review → done`.\nMoving to `in-progress` requires a plan from every status except `backlog`;\nstarting `proposed`, `someday`, or `blocked` work also needs authorization.\n`done` is reachable only from `review` and needs completion evidence. The\nlifecycle table does not reopen `done` or `archived`; file a regression as a\nnew task with a `regression_from` relation. Only an operator's\n`orbit task update \u003Cid> --status \u003Cstatus> --force` restores them.\n`orbit task archive \u003Cid>` and the UI archive action are not table moves:\nthey archive a task in any status, including `done` and `rejected`,\nthrough internal authority. The transition table governs `task update\n--status` instead, which refuses an off-table move to `archived`.\n`rejected` returns to `backlog` or\n`in-progress`. Follow supported transitions and the assigned workflow; agents\nhave no lifecycle force override. A task assigned to a human crew\n(`[crews.\u003Cname>] kind = \"human\"`) is operator work: the operator's own\n`orbit task update --status` or dashboard status control sets any status from\n`proposed` to `done` with no plan, review, evidence or `--force`, and task\nhistory records it as a `forced` entry naming the human-crew bypass. Agents and\nMCP stay on the normal lifecycle for that task, and leaving `done` or\n`archived` still needs `--force`.\n\nWhen you need a person to choose between known options, such as a sign-off, a\nprice or a policy fork, raise `orbit.decision` action `raise` on a human-crew task you\nfiled instead of writing a free-text human task: a question, two to four options\n(one-line label and consequence, exactly one `recommended`), and a `topic` when\na corpus rule should be able to match the request exactly. The operator answers,\nor a current corpus rule the operator marked `auto` answers an exact topic or\nrule id and records that answer as precedent. Either way the answer is in the\ntask's history, completes the task and unblocks its `blocked_by` dependents.\nFree text stays for open-ended asks. Raw decision history is not authority.\nOnly a merged `current` rule may be cited, and only while its review date has\nnot passed and its `depends_on` digests still match. A stale or superseded\nrule is not cited and does not answer. You cannot set `auto`. An answer that\nchanges lasting behaviour or policy must be carried into the doc, config or\ncode that owns it, in the PR of the task it unblocks.\nDetails: [Tool surface](references\u002Ftool-surface.md#raising-a-decision).\n\nWhen you work a task directly in an interactive session instead of through a\ndrain, set its `context_files` to the files the work will touch as you claim\nit, and keep them current as the change grows. Drains schedule around a\ntask's `context_files`, so an interactive claim without them collides with\nqueued work.\nSet the task's `crew` to the registered crew that actually does the work\n(for example `opus`), replacing whatever filing assigned. Crew analytics\nattribute outcomes by that field.\n","# Orbit\n\nWork through the authoritative task record and leave verifiable results.\nRead only the reference needed for the current action; this is not a reading\nchecklist. An injected task snapshot is your starting context.\n\n## Operator attention\n\nStart an orchestrator or on-call inspection with `orbit attention --json` or the read-only `orbit.attention` tool. Task-level kinds report pilot warnings and holds, human-waiting blocks, open decisions and settled reviews; runtime kinds report failed or stuck runs and possibly stale claims (Operator capability required); `ci_red` reports a red base branch and `friction_untriaged` lists open friction records; `host_unhealthy` reports failing doctor checks and, across registered hosts, hosts that cannot be read. Read `degraded` before interpreting an empty result. See [Attention](references\u002Fattention.md) for filters, local scopes, suggested actions and the delta cursor.\n\n## Connect and act\n\n- With MCP, discover its tools. In a managed activity, use the injected task\n  and inherited workspace binding; `orbit.workspace.list` may be outside the\n  activity allowlist. In an unbound session, call `orbit_workspace_list` and\n  copy the returned selector, including host qualification when federated.\n  For a CLI-only installation, inspect `orbit workspace list\u002Fshow` on the\n  intended host and use that registered workspace. Never substitute another\n  host or shadow store.\n- Use registered tools: MCP `orbit_task_show`, or the installed CLI's\n  `orbit tool run orbit.task.show --input '{\"id\":\"\u003Ctask-id>\"}'`.\n  Provenance comes from the session, not a `model` argument. Use `fields` for\n  compact reads. The advertised schema decides which inputs and tools are available.\n- Update task state through tools, not files under `.orbit\u002F`. Creating a task\n  does not authorize dispatch or completion. In a managed activity, implement\n  the assigned work; the pipeline owns delivery and lifecycle transitions.\n- Verify artifacts, task\u002Frun state, diffs and checks. Agent messages are\n  advisory. Do not report skipped validation as passing or merged as deployed.\n- To check a UI change in a browser, use the host's headless browser kit:\n  when it is verified, your environment carries `PLAYWRIGHT_MODULE`,\n  `PLAYWRIGHT_BROWSERS_PATH` and `ORBIT_BROWSER_KIT_ENV`. Source\n  `\"$ORBIT_BROWSER_KIT_ENV\"` in the shell that runs the check\n  ([Task execution](references\u002Ftask-execution.md#checking-a-ui-in-a-browser)).\n- Use the installed `orbit` binary, never `cargo run -- ...`. Bare\n  `orbit task ...` subcommands are the human surface and skip agent\n  provenance; agents call `orbit tool run orbit.task.*`. Task IDs come from\n  `orbit.task.add`; never invent one. Only a human can force an off-table\n  transition (`orbit task update --force` or the dashboard); `orbit.task.update`\n  and MCP have no `force`.\n\n## Desktop navigation\n\nWhen the connected client advertises `orbit_ui`, use its read-only `open` and\n`inspect` actions to open the control center or a selected task\u002Frun.\nDiscover workspaces first and copy the exact returned selector; pass `workspace`\nand public `id` together, with `kind: run` for a run. Keep ordinary task tools\navailable when the client cannot render the UI.\n\nThe panel can capture proposed tasks, edit allowed fields, comment and record\nreviews through separately guarded desktop tools. A click or conversation\nreference grants no operator authority. Reread authoritative task state before\nacting on a copied reference. Keep the same request ID\u002Fpayload when a write's\noutcome is unknown; only a definite refusal permits a corrected fresh request.\nNative support depends on the actual desktop build and connection; an installed\nplugin or passing protocol test alone does not prove rendering\u002Fcontext delivery.\n\n## Choose the reference\n\n| Need | Read |\n|---|---|\n| Implement an assigned task | [Task execution](references\u002Ftask-execution.md) |\n| Prepare configured agent-filled pull request sections | [Agent-filled PR sections](references\u002Ftask-execution.md#agent-filled-pr-sections) |\n| Set dependencies, relations or validation tools | [Task fields](references\u002Ftask-fields.md) |\n| Create or revise a task | [Task authoring](references\u002Ftask-authoring.md) |\n| Review a delivered diff | [Task review](references\u002Ftask-review.md) |\n| Find prior tasks or frictions | [Search](references\u002Fsearch.md) |\n| Run and interpret task-flow analytics | [Task-flow analytics](references\u002Fconcepts.md#task-flow-analytics) |\n| Record a concrete recurring obstacle | [Friction](references\u002Ffriction.md) |\n| Record and inspect repeated capability costs | [Evolution records](references\u002Ftool-surface.md#evolution-records) |\n| Resolve tool transport, permissions or workspace routing | [Tool surface](references\u002Ftool-surface.md) |\n| Understand Orbit nouns | [Concepts](references\u002Fconcepts.md) |\n| Act as a manager for resident mandates | [Manager](references\u002Fmanager.md) |\n| Run one resident cycle for a mandate | [Resident cycle](references\u002Fresident-cycle.md) |\n| Single-owner distributed drain setup or claimed-attempt recovery | [Distributed drain](references\u002Fsetup\u002Fdistributed-drain.md) |\n\nFor dispatch, backlog supervision and failed runs, use\n[orbit-orchestrate](..\u002Forbit-orchestrate\u002FSKILL.md). For machine, repository,\nMCP, automation or upgrade configuration, use [orbit-setup](..\u002Forbit-setup\u002FSKILL.md).\n\n## Lifecycle essentials\n\nNormal delivery is `proposed → backlog → in-progress → review → done`.\nMoving to `in-progress` requires a plan from every status except `backlog`;\nstarting `proposed`, `someday`, or `blocked` work also needs authorization.\n`done` is reachable only from `review` and needs completion evidence. The\nlifecycle table does not reopen `done` or `archived`; file a regression as a\nnew task with a `regression_from` relation. Only an operator's\n`orbit task update \u003Cid> --status \u003Cstatus> --force` restores them.\n`orbit task archive \u003Cid>` and the UI archive action are not table moves:\nthey archive a task in any status, including `done` and `rejected`,\nthrough internal authority. The transition table governs `task update\n--status` instead, which refuses an off-table move to `archived`.\n`rejected` returns to `backlog` or\n`in-progress`. Follow supported transitions and the assigned workflow; agents\nhave no lifecycle force override. A task assigned to a human crew\n(`[crews.\u003Cname>] kind = \"human\"`) is operator work: the operator's own\n`orbit task update --status` or dashboard status control sets any status from\n`proposed` to `done` with no plan, review, evidence or `--force`, and task\nhistory records it as a `forced` entry naming the human-crew bypass. Agents and\nMCP stay on the normal lifecycle for that task, and leaving `done` or\n`archived` still needs `--force`.\n\nWhen you need a person to choose between known options, such as a sign-off, a\nprice or a policy fork, raise `orbit.decision` action `raise` on a human-crew task you\nfiled instead of writing a free-text human task: a question, two to four options\n(one-line label and consequence, exactly one `recommended`), and a `topic` when\na corpus rule should be able to match the request exactly. The operator answers,\nor a current corpus rule the operator marked `auto` answers an exact topic or\nrule id and records that answer as precedent. Either way the answer is in the\ntask's history, completes the task and unblocks its `blocked_by` dependents.\nFree text stays for open-ended asks. Raw decision history is not authority.\nOnly a merged `current` rule may be cited, and only while its review date has\nnot passed and its `depends_on` digests still match. A stale or superseded\nrule is not cited and does not answer. You cannot set `auto`. An answer that\nchanges lasting behaviour or policy must be carried into the doc, config or\ncode that owns it, in the PR of the task it unblocks.\nDetails: [Tool surface](references\u002Ftool-surface.md#raising-a-decision).\n\nWhen you work a task directly in an interactive session instead of through a\ndrain, set its `context_files` to the files the work will touch as you claim\nit, and keep them current as the change grows. Drains schedule around a\ntask's `context_files`, so an interactive claim without them collides with\nqueued work.\nSet the task's `crew` to the registered crew that actually does the work\n(for example `opus`), replacing whatever filing assigned. Crew analytics\nattribute outcomes by that field.\n",{"name":5,"description":7},"agent-main","ed219d0bda9100437b5f448fe559dfe0eea3b9a4","plugin\u002Fskills\u002Forbit",1,"https:\u002F\u002Fgithub.com\u002Fconstellation-works\u002Forbit","https:\u002F\u002Forbit-cli.com","https:\u002F\u002Fgithub.com\u002Fconstellation-works","https:\u002F\u002Fconstellation-works.com\u002F","2026-11-11 23:12:14",{"source":8,"skillName":5,"commands":59,"prompt":69,"zipAvailable":70},[60,63,66],{"tool":61,"command":62},"npx","npx skills add constellation-works\u002Forbit --skill orbit",{"tool":64,"command":65},"bunx","bunx skills add constellation-works\u002Forbit --skill orbit",{"tool":67,"command":68},"pnpm","pnpm dlx skills add constellation-works\u002Forbit --skill orbit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fconstellation-works\u002Forbit\u002Fblob\u002Fagent-main\u002Fplugin\u002Fskills\u002Forbit\u002FSKILL.md",true,[72,78,82,86,90,94,98,102,106,110,114,118],{"path":73,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Fattention.md","REFERENCE","参考文档",12247,"https:\u002F\u002Fgithub.com\u002Fconstellation-works\u002Forbit\u002Fblob\u002Fagent-main\u002Fplugin\u002Fskills\u002Forbit\u002Freferences\u002Fattention.md",{"path":79,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Fconcepts.md",8762,"https:\u002F\u002Fgithub.com\u002Fconstellation-works\u002Forbit\u002Fblob\u002Fagent-main\u002Fplugin\u002Fskills\u002Forbit\u002Freferences\u002Fconcepts.md",{"path":83,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":84,"sourceHtmlUrl":85},"references\u002Ffriction.md",12336,"https:\u002F\u002Fgithub.com\u002Fconstellation-works\u002Forbit\u002Fblob\u002Fagent-main\u002Fplugin\u002Fskills\u002Forbit\u002Freferences\u002Ffriction.md",{"path":87,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":88,"sourceHtmlUrl":89},"references\u002Fmanager.md",12259,"https:\u002F\u002Fgithub.com\u002Fconstellation-works\u002Forbit\u002Fblob\u002Fagent-main\u002Fplugin\u002Fskills\u002Forbit\u002Freferences\u002Fmanager.md",{"path":91,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":92,"sourceHtmlUrl":93},"references\u002Fresident-cycle.md",10437,"https:\u002F\u002Fgithub.com\u002Fconstellation-works\u002Forbit\u002Fblob\u002Fagent-main\u002Fplugin\u002Fskills\u002Forbit\u002Freferences\u002Fresident-cycle.md",{"path":95,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":96,"sourceHtmlUrl":97},"references\u002Fsearch.md",3584,"https:\u002F\u002Fgithub.com\u002Fconstellation-works\u002Forbit\u002Fblob\u002Fagent-main\u002Fplugin\u002Fskills\u002Forbit\u002Freferences\u002Fsearch.md",{"path":99,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":100,"sourceHtmlUrl":101},"references\u002Fsetup\u002Fdistributed-drain.md",33929,"https:\u002F\u002Fgithub.com\u002Fconstellation-works\u002Forbit\u002Fblob\u002Fagent-main\u002Fplugin\u002Fskills\u002Forbit\u002Freferences\u002Fsetup\u002Fdistributed-drain.md",{"path":103,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":104,"sourceHtmlUrl":105},"references\u002Ftask-authoring.md",34153,"https:\u002F\u002Fgithub.com\u002Fconstellation-works\u002Forbit\u002Fblob\u002Fagent-main\u002Fplugin\u002Fskills\u002Forbit\u002Freferences\u002Ftask-authoring.md",{"path":107,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":108,"sourceHtmlUrl":109},"references\u002Ftask-execution.md",33103,"https:\u002F\u002Fgithub.com\u002Fconstellation-works\u002Forbit\u002Fblob\u002Fagent-main\u002Fplugin\u002Fskills\u002Forbit\u002Freferences\u002Ftask-execution.md",{"path":111,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":112,"sourceHtmlUrl":113},"references\u002Ftask-fields.md",44381,"https:\u002F\u002Fgithub.com\u002Fconstellation-works\u002Forbit\u002Fblob\u002Fagent-main\u002Fplugin\u002Fskills\u002Forbit\u002Freferences\u002Ftask-fields.md",{"path":115,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":116,"sourceHtmlUrl":117},"references\u002Ftask-review.md",5409,"https:\u002F\u002Fgithub.com\u002Fconstellation-works\u002Forbit\u002Fblob\u002Fagent-main\u002Fplugin\u002Fskills\u002Forbit\u002Freferences\u002Ftask-review.md",{"path":119,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":120,"sourceHtmlUrl":121},"references\u002Ftool-surface.md",64475,"https:\u002F\u002Fgithub.com\u002Fconstellation-works\u002Forbit\u002Fblob\u002Fagent-main\u002Fplugin\u002Fskills\u002Forbit\u002Freferences\u002Ftool-surface.md",[123,148,169,175,181,187],{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":130,"publishedAt":44},"01M6DZRYMNW8BCQ2GGKESTJKX0","orbit-setup","Sets up and maintains Orbit on a user's machine and repositories according to their needs. Use for installation, `orbit workspace init`, onboarding, provider\u002Fcrew and MCP configuration, experimental crew memory, the Linux sandbox, the headless browser kit for UI checks, the scheduler (sweep clock, routines, auto-tasks), worktree GC, `orbit doctor`, upgrades, task publication and backup, remote access, the dashboard, or host and service log troubleshooting. Supports existing installations as well as first-time setup; task execution belongs to orbit and backlog dispatch to orbit-orchestrate.","https:\u002F\u002Fgithub.com\u002Fconstellation-works\u002Forbit\u002Fblob\u002Fagent-main\u002Fplugin\u002Fskills\u002Forbit-setup\u002FSKILL.md",[129],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[131,5,132,43,133,134,135,41,136,137,138,40,139,140,141,142,143,144,145,146,147],"orbit setup","setup","time","up","init","host","auto","access","log","browser","dashboard","gc","worktree","headless","kit","remote","memory",{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":155,"publishedAt":44},"01M6DZRV3XD70JM27G63JRHG44","orbit-orchestrate","Prepares and supervises an Orbit backlog. Deduplicates and pilots tasks (task-pilot), assigns crews, promotes ready work, dispatches with `orbit run ship` and `orbit run auto` drains, diagnoses failed or stuck `jrun-*` runs, and routes CI\u002FQA sweep findings into repair tasks. Use for delivery operations across tasks, jobs, activities and workflow runs. Use orbit for one assigned task and orbit-setup for machine configuration or scheduler installation.","https:\u002F\u002Fgithub.com\u002Fconstellation-works\u002Forbit\u002Fblob\u002Fagent-main\u002Fplugin\u002Fskills\u002Forbit-orchestrate\u002FSKILL.md",[154],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[43,156,5,157,158,159,137,160,40,161,162,39,163,164,165,166,167,25,168,26],"orbit orchestrate","ready","ci","qa","workflow","across","work","delivery","scheduler","ship","repair","backlog","qa sweep",{"skillNo":170,"name":171,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":172,"categories":173,"keywords":174,"publishedAt":44},"01M6DZRR6KKPQXN3BTPM9HKRB5","graph","https:\u002F\u002Fgithub.com\u002Fconstellation-works\u002Forbit\u002Fblob\u002Fagent-main\u002Fcrates\u002Forbit-tools\u002Ftests\u002Ffixtures\u002Fplugins\u002Fgraph-example\u002F.orbit-plugin\u002Fskills\u002Fgraph\u002FSKILL.md",[],[171],{"skillNo":176,"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":177,"categories":178,"keywords":180,"publishedAt":44},"01M6DZRMN4RDBH6YXF6GW5TPVG","https:\u002F\u002Fgithub.com\u002Fconstellation-works\u002Forbit\u002Fblob\u002Fagent-main\u002Fcrates\u002Forbit-core\u002Fassets\u002Fskills\u002Forbit\u002FSKILL.md",[179],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[5,43,42,41,40,39,38,37,36,35,24,34,33,32,31,30,29,28,27,26,25],{"skillNo":182,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":183,"categories":184,"keywords":186,"publishedAt":44},"01M6DZRFM0H5GX49W81JE494CW","https:\u002F\u002Fgithub.com\u002Fconstellation-works\u002Forbit\u002Fblob\u002Fagent-main\u002Fcrates\u002Forbit-core\u002Fassets\u002Fskills\u002Forbit-setup\u002FSKILL.md",[185],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[131,5,132,43,133,134,135,41,136,137,138,40,139,140,141,142,143,144,145,146,147],{"skillNo":188,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":189,"categories":190,"keywords":192,"publishedAt":44},"01M6DZRBD8G9E6AGM3VA87VRZG","https:\u002F\u002Fgithub.com\u002Fconstellation-works\u002Forbit\u002Fblob\u002Fagent-main\u002Fcrates\u002Forbit-core\u002Fassets\u002Fskills\u002Forbit-orchestrate\u002FSKILL.md",[191],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[43,156,5,157,158,159,137,160,40,161,162,39,163,164,165,166,167,25,168,26]]