[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F2N48TD0D17CFDD6VCBC5Q":3,"skill-same:01M7F2N48TD0D17CFDD6VCBC5Q":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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7F2N48TD0D17CFDD6VCBC5Q","orchestration",null,"Use Orca orchestration for structured multi-agent coordination: threaded messages, blocking ask\u002Freply flows, task dispatch, worker_done\u002Fescalation waits, task DAGs, decision gates, coordinator loops, or decomposing work across agents. Use `orca-cli` instead for full ownership handoffs, including requests phrased as \"hand off\", \"handoff\", \"handover\", \"give this to another agent\", or \"another worktree\" when the user did not explicitly ask to supervise, monitor, wait for results, or coordinate a DAG. Use `orca-cli` for terminal control, lightweight terminal prompts, shell commands, Orca worktree management, reading or waiting on terminals, and automation of the browser embedded inside Orca. Use Computer Use for external browser windows, webviews, Orca app UI, or desktop UI outside Orca's embedded browser only when the task requires OS\u002Fwindow-level control such as focus, menus, dialogs, coordinates, or screenshots. Use `orca-cli` for Orca's embedded pages and a page-automation tool such as Playwright or CDP for external pages.","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Forchestration\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: orchestration\ndescription: >-\n  Use Orca orchestration for structured multi-agent coordination: threaded\n  messages, blocking ask\u002Freply flows, task dispatch, worker_done\u002Fescalation\n  waits, task DAGs, decision gates, coordinator loops, or decomposing work\n  across agents. Use `orca-cli` instead for full ownership handoffs, including\n  requests phrased as \"hand off\", \"handoff\", \"handover\", \"give this to another\n  agent\", or \"another worktree\" when the user did not explicitly ask to\n  supervise, monitor, wait for results, or coordinate a DAG. Use `orca-cli` for\n  terminal control, lightweight terminal prompts, shell commands, Orca\n  worktree management, reading or waiting on terminals, and automation of the\n  browser embedded inside Orca. Use Computer Use for external browser windows,\n  webviews, Orca app UI, or desktop UI outside Orca's embedded browser only when\n  the task requires OS\u002Fwindow-level control such as focus, menus, dialogs,\n  coordinates, or screenshots. Use `orca-cli` for Orca's embedded pages and a\n  page-automation tool such as Playwright or CDP for external pages.\n---\n\n# Orca Orchestration\n\nThis file is a discovery stub, not the usage guide. The full, version-matched Orca\norchestration reference is served by the `orca` binary itself — kept out of this file on\npurpose so it can never drift from the binary that will actually run your commands.\n\nEngage Orca orchestration whenever you need structured multi-agent coordination: threaded\nmessages, blocking ask\u002Freply flows, task dispatch, worker_done\u002Fescalation waits, task DAGs,\ndecision gates, coordinator loops, or decomposing work across agents. Use the orca-cli skill\ninstead for full ownership handoffs (\"hand off\", \"handoff\", \"handover\", \"give this to\nanother agent\", \"another worktree\") when the user did not ask to supervise, monitor, wait\nfor results, or coordinate a DAG — and for ordinary terminal control, shell commands,\nworktree management, and the built-in browser. Coordination requires real Orca runtime\nstate; never substitute a non-Orca subagent tool.\n\n## Resolve the CLI for this session\n\nChoose the executable once and reuse it for every later command:\n\n- If the `ORCA_CLI_COMMAND` environment variable is set, use its value. Orca exports this\n  for managed WSL sessions.\n- Otherwise, in a dev checkout whose session exposes `ORCA_DEV_REPO_ROOT`, use `orca-dev`.\n- Otherwise, on Linux outside an Orca-managed terminal, use `orca-ide`. Never run bare\n  `orca` there — outside Orca's terminals it normally resolves to the\n  GNOME Orca screen reader (`\u002Fusr\u002Fbin\u002Forca`) and starts speech on the user's machine.\n- Otherwise, use `orca`.\n\nBelow, `ORCA` is a placeholder for the executable you resolved. Substitute it before\nrunning anything; do not create a shell variable or run `ORCA` literally. This works the\nsame way in POSIX shells, PowerShell, and cmd.exe.\n\nIf the selected executable cannot run, report its exact error and stop. Do not fall through\nto another executable, which could silently target a different Orca build.\n\n## Load the full guide before running Orca commands\n\n```text\nORCA skills get orchestration\n```\n\nThat prints the complete, version-matched guide for the exact binary that will handle your\nnext commands — task creation and dispatch, injected lifecycle preambles, worker_done\nauthority, decision gates, and coordinator loops. Read it first, then run the specific\ncommand you need.\n\nDon't guess subcommands or flags from memory or from a cached copy of this stub. They\nchange between Orca releases, and this file deliberately no longer lists them. Confirm the\napp is up with `ORCA status --json` (start it with `ORCA open --json` if needed), and\nprefer `--json` for agent-driven calls.\n\n## If an older Orca does not recognize `skills get`\n\nUse this fallback only when the selected binary explicitly reports that `skills get` is an\nunknown command. Another failure is not proof of an older binary; report it rather than\nguessing or changing executables. For a confirmed pre-guide binary, use only this bounded,\nread-only bootstrap to orient. Do not dead-end and do not invent commands:\n\n```text\nORCA status --json\nORCA orchestration task-list --json\nORCA terminal list --json\n```\n\nThen tell the user that updating Orca restores the full, version-matched guide via\n`ORCA skills get orchestration`. Beyond these commands, ask the user rather than guessing a\ncommand surface this older binary may not support.\n","# Orca Orchestration\n\nThis file is a discovery stub, not the usage guide. The full, version-matched Orca\norchestration reference is served by the `orca` binary itself — kept out of this file on\npurpose so it can never drift from the binary that will actually run your commands.\n\nEngage Orca orchestration whenever you need structured multi-agent coordination: threaded\nmessages, blocking ask\u002Freply flows, task dispatch, worker_done\u002Fescalation waits, task DAGs,\ndecision gates, coordinator loops, or decomposing work across agents. Use the orca-cli skill\ninstead for full ownership handoffs (\"hand off\", \"handoff\", \"handover\", \"give this to\nanother agent\", \"another worktree\") when the user did not ask to supervise, monitor, wait\nfor results, or coordinate a DAG — and for ordinary terminal control, shell commands,\nworktree management, and the built-in browser. Coordination requires real Orca runtime\nstate; never substitute a non-Orca subagent tool.\n\n## Resolve the CLI for this session\n\nChoose the executable once and reuse it for every later command:\n\n- If the `ORCA_CLI_COMMAND` environment variable is set, use its value. Orca exports this\n  for managed WSL sessions.\n- Otherwise, in a dev checkout whose session exposes `ORCA_DEV_REPO_ROOT`, use `orca-dev`.\n- Otherwise, on Linux outside an Orca-managed terminal, use `orca-ide`. Never run bare\n  `orca` there — outside Orca's terminals it normally resolves to the\n  GNOME Orca screen reader (`\u002Fusr\u002Fbin\u002Forca`) and starts speech on the user's machine.\n- Otherwise, use `orca`.\n\nBelow, `ORCA` is a placeholder for the executable you resolved. Substitute it before\nrunning anything; do not create a shell variable or run `ORCA` literally. This works the\nsame way in POSIX shells, PowerShell, and cmd.exe.\n\nIf the selected executable cannot run, report its exact error and stop. Do not fall through\nto another executable, which could silently target a different Orca build.\n\n## Load the full guide before running Orca commands\n\n```text\nORCA skills get orchestration\n```\n\nThat prints the complete, version-matched guide for the exact binary that will handle your\nnext commands — task creation and dispatch, injected lifecycle preambles, worker_done\nauthority, decision gates, and coordinator loops. Read it first, then run the specific\ncommand you need.\n\nDon't guess subcommands or flags from memory or from a cached copy of this stub. They\nchange between Orca releases, and this file deliberately no longer lists them. Confirm the\napp is up with `ORCA status --json` (start it with `ORCA open --json` if needed), and\nprefer `--json` for agent-driven calls.\n\n## If an older Orca does not recognize `skills get`\n\nUse this fallback only when the selected binary explicitly reports that `skills get` is an\nunknown command. Another failure is not proof of an older binary; report it rather than\nguessing or changing executables. For a confirmed pre-guide binary, use only this bounded,\nread-only bootstrap to orient. Do not dead-end and do not invent commands:\n\n```text\nORCA status --json\nORCA orchestration task-list --json\nORCA terminal list --json\n```\n\nThen tell the user that updating Orca restores the full, version-matched guide via\n`ORCA skills get orchestration`. Beyond these commands, ask the user rather than guessing a\ncommand surface this older binary may not support.\n",{"name":5,"description":7},"main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","05-技能与代理开发\u002Forchestration",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill orchestration",{"tool":38,"command":39},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill orchestration",{"tool":41,"command":42},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill orchestration","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Forchestration\u002FSKILL.md",true,[],[47,54,59,66,73,80],{"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},"01M7FFG485KY83TD6HSC4YPCMC","obsidian-clipper-template-creator","Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator\u002FSKILL.md",[],[],{"skillNo":55,"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":56,"categories":57,"keywords":58,"publishedAt":19},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M7FFFY0QEM14SKWPDYGMXM2P","python-api","Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP\u002FmAP semantics, and source-style import diagnostics.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Fpython-api\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M7FFFVZQZ2GJ0C0TGP7JHD20","file-evaluation","Folder-based PASCAL VOC AP\u002FmAP evaluation from ground-truth and detection text files.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Ffile-evaluation\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7FFFSFNYSE77SJ6PE1CK2DA","object-detection-metrics","Guides legacy Object-Detection-Metrics PASCAL VOC AP\u002FmAP evaluation from detection text folders and direct Python API classes.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7FFFP0GCK1RVXBCPQ8APBMT","nx-workspace-patterns","Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fnx-workspace-patterns\u002FSKILL.md",[],[]]