[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6PB7SCN3VJV5E74QZXVRP2J":3,"skill-same:01M6PB7SCN3VJV5E74QZXVRP2J":88},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":50,"commitSha":51,"skillDirectory":52,"forksCount":13,"repositoryHtmlUrl":53,"repositoryHomepageUrl":6,"ownerHtmlUrl":54,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":55,"install":56,"resources":69},"01M6PB7SCN3VJV5E74QZXVRP2J","opencode-delegate",null,"Delegate coding tasks to the OpenCode CLI only when the user explicitly requests it, while the orchestrator retains review and landing responsibility.","duc-duy-1612\u002FOnline-Delivery-Systems-Web","duc-duy-1612","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F192231384?v=4","01M6NSDKQQDKVTHZ8DZMZ1VYY6","01M6NSDKW8DDVTQHBT1HBDDJPT",0,"MIT","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fopencode-delegate\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"opencode delegate","delegate","opencode","orchestrator","agent-orchestration","critical","commands","community","files","master","only","review","read","node","Bash","git","run","tasks","orchestration","cli","2026-11-10 10:12:30",false,"---\nname: opencode-delegate\ndescription: Delegate coding tasks to the OpenCode CLI only when the user explicitly\n  requests it, while the orchestrator retains review and landing responsibility.\nrisk: critical\ncategory: agent-orchestration\nsource: https:\u002F\u002Fgithub.com\u002FamElnagdy\u002Fdelegate-skills\nsource_repo: amElnagdy\u002Fdelegate-skills\nsource_type: community\ndate_added: '2026-08-26'\nlicense: MIT\nlicense_source: https:\u002F\u002Fgithub.com\u002FamElnagdy\u002Fdelegate-skills\u002Fblob\u002Fmaster\u002FLICENSE\ncompatibility: Requires the `opencode` CLI installed and authenticated, Node 18+,\n  and git. The orchestrating agent must be able to run shell commands and read files.\n  Shell examples assume bash\u002Fzsh (macOS\u002FLinux, or Git Bash\u002FWSL on Windows).\nmetadata:\n  version: 0.5.0\n---\n# OpenCode Delegate\n\n## When to Use\n\n- You want to delegate a bounded coding task to a separate `opencode` implementer (`OpenCode`) and then review its diff yourself.\n- The user explicitly asked for delegation to this implementer.\n\nYou are the **orchestrator**. This skill lets you hand a bounded coding task to a separate\n**implementer** — the OpenCode CLI — then review what it produced and land it yourself. You write\nthe brief and own the judgment; OpenCode does the typing in its own session; you verify and commit.\n\nNothing here is specific to one orchestrating agent. The loop needs only the ability to run a shell\ncommand and read a file, so any agent with those two capabilities — Claude Code, OpenCode driving a\nsibling session, or a comparable one — can drive it. (It is designed for and run on Claude Code; treat\nother orchestrators as designed-for, not yet proven.)\n\n## When NOT to use this\n\n- The task is small enough to just do inline — delegation overhead is not worth it.\n- The `opencode` CLI is not installed or not authenticated (run `opencode auth login`).\n- You want to write the code yourself, or you only need a review (use the `plan` agent via `--read-only`).\n\n## Prerequisites (check once)\n\n1. `opencode --version` succeeds. If not, install (`npm i -g opencode-ai`, or the native installer from\n   opencode.ai) and `opencode auth login`.\n2. **Confirm which `opencode` is on PATH.** `command -v opencode` shows the active binary and\n   `opencode --version` its version. The relay records the version it ran into `result.json`, so a stale\n   binary is visible after the fact.\n3. A model provider is authenticated — `opencode auth list` shows at least one credential.\n4. You are in (or will point `--cd` at) the target git repository.\n\n## Choose the implementer model\n\nOpenCode has **no safe default** — a bare `opencode run` errors — so a fresh run needs a model via\n`--model` or a fleet `--lane` that sets one (a resumed run inherits its session's model). Naming the\nmodel is the one decision a single-model backend like codex-delegate never had, and it has two owners:\n\n- **The human owns which models are allowed.** `opencode models` lists hundreds of entries, most billed\n  per token (OpenRouter and the like); only the human knows which are their flat-rate subscriptions, and\n  the CLI can't tell them apart. So the usable set is theirs — ideally stated once in the repo's\n  `AGENTS.md` or their `CLAUDE.md` (e.g. \"delegate mechanical work to `opencode-go\u002F…`, hard logic to\n  `…`\").\n- **You, the orchestrator, pick per task — from that set.** Match the model to the brief: a cheap, fast\n  model for a mechanical sweep (rename, migration, removal); a strong one for a subtle bug or a\n  money\u002Fsecurity path.\n- **If no usable set is stated, ask — don't guess.** Guessing from the catalog risks a metered model and\n  a surprise bill. Name the constraint to the human and let them choose.\n\nMore depth: [references\u002Fwriting-the-brief.md](references\u002Fwriting-the-brief.md).\n\n## The loop\n\nRun these five steps per task. Steps 1, 4, and 5 are your judgment; 2 and 3 are mechanical.\n\n### 1. Write the brief\n\nOpenCode sees **only** the text you send plus what it can read from the working tree — no chat history,\nno shared context. Everything the task needs goes in the brief: the goal, the current state, what to\nchange, what to leave untouched, the project's **actual** gate commands (discover them from the repo's\nAGENTS.md\u002FCLAUDE.md\u002FMakefile — do not assume), and a report contract. Tell OpenCode it will **not**\ncommit (you will). Keep one task per brief. Full guidance and a template:\n[references\u002Fwriting-the-brief.md](references\u002Fwriting-the-brief.md).\n\n### 2. Dispatch\n\nSend the brief to OpenCode with the bundled helper. It wraps `opencode run`, captures the run, and\nwrites a structured `result.json` — so your only job is \"run a command, read a file.\" (`\u003Cskill-dir>`\nbelow is this skill's installed directory — the folder containing this `SKILL.md`. Claude Code prints\nit as \"Base directory for this skill\" when the skill loads; on other orchestrators use that same\ndirectory — if unsure where it landed, run `find ~ -name relay.mjs -path '*opencode-delegate*'` and\nsubstitute the directory above it.)\n\n```bash\nnode \"\u003Cskill-dir>\u002Fscripts\u002Frelay.mjs\" --brief brief.txt --model \u003Cprovider\u002Fmodel> --cd \u002Fpath\u002Fto\u002Frepo\n# --model (or a --lane that sets model) is required on a fresh run\n# fleet lane from delegate-setup:           add --lane \u003Cname>  (dials apply; flags still win)\n# read-only (review\u002Fdiagnosis, no edits):   add --read-only   (uses the plan agent)\n# continue the previous OpenCode session:   add --resume-last  (delta brief only; keeps the model)\n# hard time limit (watchdog):               add --timeout 2h  (default: off; implementation runs routinely need 1-2h)\n# see all options:                          node ...\u002Frelay.mjs --help\n```\n\nThe helper defaults to the write-capable `build` agent and writes its artifacts to a temp dir, so the\nrepo under review stays clean. It **never commits** — see step 5. Mechanics, flags, and the\n`result.json` shape: [references\u002Fdispatch-and-poll.md](references\u002Fdispatch-and-poll.md).\n\n### 3. Wait for completion\n\nThe helper blocks until OpenCode finishes, so back it with whatever your orchestrator offers and resume\nwhen it returns:\n\n- **Claude Code:** run the Bash call with `run_in_background: true`; you are notified on completion.\n- **Plain shell \u002F other agents:** run it in the foreground for short tasks, or background it and poll\n  the result file — `… &` in bash\u002Fzsh (including Git Bash\u002FWSL), or your shell's equivalent (`Start-Job`\n  in PowerShell, `start \u002Fb` in cmd). The run is done when `result.json` exists with a `status`. (A\n  pre-run usage error — bad args or an empty brief — instead exits with code 2 and writes no result\n  file, so check the exit code too. A missing `opencode` binary exits 127 but *does* write a\n  `result.json` with status `opencode_unavailable`.)\n\nDo not trust progress trackers over reality: a run is finished when `result.json` is written and the\nprocess has exited. Read the working tree, not a status line. The implementer's full report is\nthe `finalMessage` field in `result.json` (also printed in full on stdout between the report markers).\n\n### 4. Review — do not trust the self-report\n\nOpenCode's `result.json` includes its own final message and any gate claims. **Re-verify, don't accept:**\n\n- **Re-run the project's gates yourself** (the test\u002Flint\u002Fbuild commands from step 1). Never take\n  \"gates passed\" on faith.\n- **Read the diff** against the brief: did OpenCode do what was asked, nothing more (scope creep) and\n  nothing less? `touchedFiles` in the result is your starting point.\n- **Run the relevant guard skills** on the diff if you have them installed (clean-code-guard,\n  test-guard, etc. from `guard-skills`) — this skill produces the work; those skills judge it.\n- For schema\u002Fmigration changes, round-trip them; for removals, grep for dangling references.\n\nFull checklist: [references\u002Freview-and-land.md](references\u002Freview-and-land.md).\n\n### 5. Land it\n\nThe implementer edits the working tree; **the orchestrator commits.** Committing should be the act of\nthe party that verified the work. Only after the gates pass and the diff holds:\n\n- Commit the verified work yourself, with a clear message.\n- If it needs changes, send a delta brief with `--resume-last` (don't restate the whole task) and\n  review again.\n\n## Autonomy model\n\nOpenCode's autonomy is governed by the **agent**, not a sandbox enum:\n\n- **`build`** (the relay default) — write-capable; edits files in the working dir headlessly. The\n  equivalent of \"let it implement.\"\n- **`plan`** (via `--read-only`) — read-only; reviews and diagnoses without touching the tree. The\n  equivalent of \"let it look but not edit.\"\n\nPermissions **auto-approve by default**: the relay passes `--auto` so a headless run never blocks on a\nprompt no one can answer. That is the point of unattended delegation — the orchestrator's diff review\nand the implementer sweep (step 4) are the safety net, not a per-action prompt. Pass `--no-auto` to\nhonor the agent's own permission config instead (allow\u002Fask\u002Fdeny per action); pair it with an agent whose\nin-workspace permissions are set to *allow*, or a headless run can hang waiting on an `ask`.\n**Read-only (`plan`) runs never get `--auto`** — auto-approving would let the plan agent's ask-gated\nedit\u002Fbash permissions through and defeat \"read-only,\" so a review can't be tricked into touching the tree.\n\n## Authorization model\n\nDelegation is something the human opts into. Once they have (\"run this queue\", \"proceed\"), committing\nverified, gate-passing work is the agreed contract — that is the whole point. Two limits on that\nmandate: **surface, don't absorb** (report OpenCode's design decisions, defensible-but-unasked turns,\nand non-blocking nitpicks rather than silently keeping them) and **stop for scope changes** (if correct\ncompletion needs going beyond the brief, ask — don't expand the mandate yourself). The full treatment\nis in [references\u002Freview-and-land.md](references\u002Freview-and-land.md).\n\n## References\n\n- [references\u002Fwriting-the-brief.md](references\u002Fwriting-the-brief.md) — how to write a brief OpenCode can\n  execute blind: structure, XML blocks, the report contract, embedding the real gate commands.\n- [references\u002Fdispatch-and-poll.md](references\u002Fdispatch-and-poll.md) — `relay.mjs` flags, the\n  `result.json` contract, backgrounding per orchestrator, and recovery when a run misbehaves.\n- [references\u002Freview-and-land.md](references\u002Freview-and-land.md) — the review checklist, the commit\n  boundary, and the rework cycle via `--resume-last`.\n- [references\u002Fmulti-task-queues.md](references\u002Fmulti-task-queues.md) — running a sequential queue:\n  carrying constraints forward, progress tracking, and the end-of-run coherence check.\n\n\n## Limitations\n\n- Docs-only import — executable `scripts\u002Frelay.mjs` not included; see upstream for full runtime. Requires `opencode` CLI, Node 18+, git.\n- Relay never commits — it only returns structured result JSON; you review and land the commit.\n\n> Adapted from [amElnagdy\u002Fdelegate-skills](https:\u002F\u002Fgithub.com\u002FamElnagdy\u002Fdelegate-skills) (MIT) — docs-only, runtime not bundled.\n","# OpenCode Delegate\n\n## When to Use\n\n- You want to delegate a bounded coding task to a separate `opencode` implementer (`OpenCode`) and then review its diff yourself.\n- The user explicitly asked for delegation to this implementer.\n\nYou are the **orchestrator**. This skill lets you hand a bounded coding task to a separate\n**implementer** — the OpenCode CLI — then review what it produced and land it yourself. You write\nthe brief and own the judgment; OpenCode does the typing in its own session; you verify and commit.\n\nNothing here is specific to one orchestrating agent. The loop needs only the ability to run a shell\ncommand and read a file, so any agent with those two capabilities — Claude Code, OpenCode driving a\nsibling session, or a comparable one — can drive it. (It is designed for and run on Claude Code; treat\nother orchestrators as designed-for, not yet proven.)\n\n## When NOT to use this\n\n- The task is small enough to just do inline — delegation overhead is not worth it.\n- The `opencode` CLI is not installed or not authenticated (run `opencode auth login`).\n- You want to write the code yourself, or you only need a review (use the `plan` agent via `--read-only`).\n\n## Prerequisites (check once)\n\n1. `opencode --version` succeeds. If not, install (`npm i -g opencode-ai`, or the native installer from\n   opencode.ai) and `opencode auth login`.\n2. **Confirm which `opencode` is on PATH.** `command -v opencode` shows the active binary and\n   `opencode --version` its version. The relay records the version it ran into `result.json`, so a stale\n   binary is visible after the fact.\n3. A model provider is authenticated — `opencode auth list` shows at least one credential.\n4. You are in (or will point `--cd` at) the target git repository.\n\n## Choose the implementer model\n\nOpenCode has **no safe default** — a bare `opencode run` errors — so a fresh run needs a model via\n`--model` or a fleet `--lane` that sets one (a resumed run inherits its session's model). Naming the\nmodel is the one decision a single-model backend like codex-delegate never had, and it has two owners:\n\n- **The human owns which models are allowed.** `opencode models` lists hundreds of entries, most billed\n  per token (OpenRouter and the like); only the human knows which are their flat-rate subscriptions, and\n  the CLI can't tell them apart. So the usable set is theirs — ideally stated once in the repo's\n  `AGENTS.md` or their `CLAUDE.md` (e.g. \"delegate mechanical work to `opencode-go\u002F…`, hard logic to\n  `…`\").\n- **You, the orchestrator, pick per task — from that set.** Match the model to the brief: a cheap, fast\n  model for a mechanical sweep (rename, migration, removal); a strong one for a subtle bug or a\n  money\u002Fsecurity path.\n- **If no usable set is stated, ask — don't guess.** Guessing from the catalog risks a metered model and\n  a surprise bill. Name the constraint to the human and let them choose.\n\nMore depth: [references\u002Fwriting-the-brief.md](references\u002Fwriting-the-brief.md).\n\n## The loop\n\nRun these five steps per task. Steps 1, 4, and 5 are your judgment; 2 and 3 are mechanical.\n\n### 1. Write the brief\n\nOpenCode sees **only** the text you send plus what it can read from the working tree — no chat history,\nno shared context. Everything the task needs goes in the brief: the goal, the current state, what to\nchange, what to leave untouched, the project's **actual** gate commands (discover them from the repo's\nAGENTS.md\u002FCLAUDE.md\u002FMakefile — do not assume), and a report contract. Tell OpenCode it will **not**\ncommit (you will). Keep one task per brief. Full guidance and a template:\n[references\u002Fwriting-the-brief.md](references\u002Fwriting-the-brief.md).\n\n### 2. Dispatch\n\nSend the brief to OpenCode with the bundled helper. It wraps `opencode run`, captures the run, and\nwrites a structured `result.json` — so your only job is \"run a command, read a file.\" (`\u003Cskill-dir>`\nbelow is this skill's installed directory — the folder containing this `SKILL.md`. Claude Code prints\nit as \"Base directory for this skill\" when the skill loads; on other orchestrators use that same\ndirectory — if unsure where it landed, run `find ~ -name relay.mjs -path '*opencode-delegate*'` and\nsubstitute the directory above it.)\n\n```bash\nnode \"\u003Cskill-dir>\u002Fscripts\u002Frelay.mjs\" --brief brief.txt --model \u003Cprovider\u002Fmodel> --cd \u002Fpath\u002Fto\u002Frepo\n# --model (or a --lane that sets model) is required on a fresh run\n# fleet lane from delegate-setup:           add --lane \u003Cname>  (dials apply; flags still win)\n# read-only (review\u002Fdiagnosis, no edits):   add --read-only   (uses the plan agent)\n# continue the previous OpenCode session:   add --resume-last  (delta brief only; keeps the model)\n# hard time limit (watchdog):               add --timeout 2h  (default: off; implementation runs routinely need 1-2h)\n# see all options:                          node ...\u002Frelay.mjs --help\n```\n\nThe helper defaults to the write-capable `build` agent and writes its artifacts to a temp dir, so the\nrepo under review stays clean. It **never commits** — see step 5. Mechanics, flags, and the\n`result.json` shape: [references\u002Fdispatch-and-poll.md](references\u002Fdispatch-and-poll.md).\n\n### 3. Wait for completion\n\nThe helper blocks until OpenCode finishes, so back it with whatever your orchestrator offers and resume\nwhen it returns:\n\n- **Claude Code:** run the Bash call with `run_in_background: true`; you are notified on completion.\n- **Plain shell \u002F other agents:** run it in the foreground for short tasks, or background it and poll\n  the result file — `… &` in bash\u002Fzsh (including Git Bash\u002FWSL), or your shell's equivalent (`Start-Job`\n  in PowerShell, `start \u002Fb` in cmd). The run is done when `result.json` exists with a `status`. (A\n  pre-run usage error — bad args or an empty brief — instead exits with code 2 and writes no result\n  file, so check the exit code too. A missing `opencode` binary exits 127 but *does* write a\n  `result.json` with status `opencode_unavailable`.)\n\nDo not trust progress trackers over reality: a run is finished when `result.json` is written and the\nprocess has exited. Read the working tree, not a status line. The implementer's full report is\nthe `finalMessage` field in `result.json` (also printed in full on stdout between the report markers).\n\n### 4. Review — do not trust the self-report\n\nOpenCode's `result.json` includes its own final message and any gate claims. **Re-verify, don't accept:**\n\n- **Re-run the project's gates yourself** (the test\u002Flint\u002Fbuild commands from step 1). Never take\n  \"gates passed\" on faith.\n- **Read the diff** against the brief: did OpenCode do what was asked, nothing more (scope creep) and\n  nothing less? `touchedFiles` in the result is your starting point.\n- **Run the relevant guard skills** on the diff if you have them installed (clean-code-guard,\n  test-guard, etc. from `guard-skills`) — this skill produces the work; those skills judge it.\n- For schema\u002Fmigration changes, round-trip them; for removals, grep for dangling references.\n\nFull checklist: [references\u002Freview-and-land.md](references\u002Freview-and-land.md).\n\n### 5. Land it\n\nThe implementer edits the working tree; **the orchestrator commits.** Committing should be the act of\nthe party that verified the work. Only after the gates pass and the diff holds:\n\n- Commit the verified work yourself, with a clear message.\n- If it needs changes, send a delta brief with `--resume-last` (don't restate the whole task) and\n  review again.\n\n## Autonomy model\n\nOpenCode's autonomy is governed by the **agent**, not a sandbox enum:\n\n- **`build`** (the relay default) — write-capable; edits files in the working dir headlessly. The\n  equivalent of \"let it implement.\"\n- **`plan`** (via `--read-only`) — read-only; reviews and diagnoses without touching the tree. The\n  equivalent of \"let it look but not edit.\"\n\nPermissions **auto-approve by default**: the relay passes `--auto` so a headless run never blocks on a\nprompt no one can answer. That is the point of unattended delegation — the orchestrator's diff review\nand the implementer sweep (step 4) are the safety net, not a per-action prompt. Pass `--no-auto` to\nhonor the agent's own permission config instead (allow\u002Fask\u002Fdeny per action); pair it with an agent whose\nin-workspace permissions are set to *allow*, or a headless run can hang waiting on an `ask`.\n**Read-only (`plan`) runs never get `--auto`** — auto-approving would let the plan agent's ask-gated\nedit\u002Fbash permissions through and defeat \"read-only,\" so a review can't be tricked into touching the tree.\n\n## Authorization model\n\nDelegation is something the human opts into. Once they have (\"run this queue\", \"proceed\"), committing\nverified, gate-passing work is the agreed contract — that is the whole point. Two limits on that\nmandate: **surface, don't absorb** (report OpenCode's design decisions, defensible-but-unasked turns,\nand non-blocking nitpicks rather than silently keeping them) and **stop for scope changes** (if correct\ncompletion needs going beyond the brief, ask — don't expand the mandate yourself). The full treatment\nis in [references\u002Freview-and-land.md](references\u002Freview-and-land.md).\n\n## References\n\n- [references\u002Fwriting-the-brief.md](references\u002Fwriting-the-brief.md) — how to write a brief OpenCode can\n  execute blind: structure, XML blocks, the report contract, embedding the real gate commands.\n- [references\u002Fdispatch-and-poll.md](references\u002Fdispatch-and-poll.md) — `relay.mjs` flags, the\n  `result.json` contract, backgrounding per orchestrator, and recovery when a run misbehaves.\n- [references\u002Freview-and-land.md](references\u002Freview-and-land.md) — the review checklist, the commit\n  boundary, and the rework cycle via `--resume-last`.\n- [references\u002Fmulti-task-queues.md](references\u002Fmulti-task-queues.md) — running a sequential queue:\n  carrying constraints forward, progress tracking, and the end-of-run coherence check.\n\n\n## Limitations\n\n- Docs-only import — executable `scripts\u002Frelay.mjs` not included; see upstream for full runtime. Requires `opencode` CLI, Node 18+, git.\n- Relay never commits — it only returns structured result JSON; you review and land the commit.\n\n> Adapted from [amElnagdy\u002Fdelegate-skills](https:\u002F\u002Fgithub.com\u002FamElnagdy\u002Fdelegate-skills) (MIT) — docs-only, runtime not bundled.\n",{"name":5,"risk":23,"source":43,"license":14,"category":22,"metadata":44,"date_added":46,"description":7,"source_repo":47,"source_type":25,"compatibility":48,"license_source":49},"https:\u002F\u002Fgithub.com\u002FamElnagdy\u002Fdelegate-skills",{"version":45},"0.5.0","2026-08-26","amElnagdy\u002Fdelegate-skills","Requires the `opencode` CLI installed and authenticated, Node 18+, and git. The orchestrating agent must be able to run shell commands and read files. Shell examples assume bash\u002Fzsh (macOS\u002FLinux, or Git Bash\u002FWSL on Windows).","https:\u002F\u002Fgithub.com\u002FamElnagdy\u002Fdelegate-skills\u002Fblob\u002Fmaster\u002FLICENSE","main","f3312ba749561b6159f477dbfc9313c875d40a56",".agents\u002Fskills_archive\u002Fopencode-delegate","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612","2026-10-25 23:50:58",{"source":8,"skillName":5,"commands":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill opencode-delegate",{"tool":62,"command":63},"bunx","bunx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill opencode-delegate",{"tool":65,"command":66},"pnpm","pnpm dlx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill opencode-delegate","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fopencode-delegate\u002FSKILL.md",true,[70,76,80,84],{"path":71,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002Fdispatch-and-poll.md","REFERENCE","参考文档",10161,"https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fopencode-delegate\u002Freferences\u002Fdispatch-and-poll.md",{"path":77,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Fmulti-task-queues.md",3928,"https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fopencode-delegate\u002Freferences\u002Fmulti-task-queues.md",{"path":81,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Freview-and-land.md",7851,"https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fopencode-delegate\u002Freferences\u002Freview-and-land.md",{"path":85,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":86,"sourceHtmlUrl":87},"references\u002Fwriting-the-brief.md",7524,"https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fopencode-delegate\u002Freferences\u002Fwriting-the-brief.md",[89,116,128,153,181,205],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":100,"publishedAt":38},"01M6Q0FA5FZ410Z33Z3TFQ4DBA","zero-trust","Implement zero-trust network architecture. Configure identity-based access, micro-segmentation, and continuous verification. Use when implementing modern security architectures.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fzero-trust\u002FSKILL.md",[95],{"categoryNo":96,"categoryName":97,"taxonomyType":98,"taxonomyTypeDesc":99},"01JBSEEDCAT000000000000011","运维与部署","SCENARIO","使用场景",[101,102,103,104,105,106,91,107,108,109,110,28,25,50,111,23,112,113,114,115],"ZeRO","trust","zero trust","architecture","assessment","verification","segmentation","devops-security","access","configure","active","scope","scripts","relevant","implementing",{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":38},"01M6Q0F1YZJW3KX5FBKEVZ8CV4","zcode-delegate","Delegate coding tasks to the Z.AI ZCode CLI only when the user explicitly requests it, while the orchestrator retains review and landing responsibility.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fzcode-delegate\u002FSKILL.md",[],[19,123,124,29,37,36,35,34,32,125,31,30,21,28,26,25,126,127,23,22],"zcode","zcode delegate","model","desktop app","app",{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":134,"publishedAt":38},"01M6Q0ETK41VGNMYEXW0T00AJN","youtube-transcript","Fetch YouTube transcripts through DeepAPI or local fallback tooling and save clean text output.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fyoutube-transcript\u002FSKILL.md",[],[135,136,137,138,139,140,141,142,143,144,145,146,147,25,50,148,149,150,151,152],"transcript","youtube transcript","youtube","safe","github","codex","research","license","https","text","fetch","tooling","clean","local","output","deepapi","youtube transcripts","blob",{"skillNo":154,"name":155,"nameZh":6,"description":156,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":157,"categories":158,"keywords":170,"publishedAt":38},"01M6Q0EPPH2PVMDW40017F8WX0","youtube-transcript-skills","Fetch YouTube video transcripts, search videos\u002Fchannels, browse channels, and extract playlists via the getyoutubetranscript.com API - free tier, no card required.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fyoutube-transcript-skills\u002FSKILL.md",[159,162,165],{"categoryNo":160,"categoryName":161,"taxonomyType":98,"taxonomyTypeDesc":99},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":163,"categoryName":164,"taxonomyType":98,"taxonomyTypeDesc":99},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":166,"categoryName":167,"taxonomyType":168,"taxonomyTypeDesc":169},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[135,136,137,171,138,172,139,140,142,173,174,175,176,145,177,25,50,178,179,180],"youtube transcript skills","gemini","search","api","Video","browse","api-integration","free","card","channels",{"skillNo":182,"name":183,"nameZh":6,"description":184,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":185,"categories":186,"keywords":191,"publishedAt":38},"01M6Q0EAB96PX83W5PTE8A0R8D","youtube-notetaker","Turn YouTube talks into local study notes with slides, transcripts, editable annotations, and a markdown-backed viewer.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fyoutube-notetaker\u002FSKILL.md",[187,190],{"categoryNo":188,"categoryName":189,"taxonomyType":98,"taxonomyTypeDesc":99},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":163,"categoryName":164,"taxonomyType":98,"taxonomyTypeDesc":99},[137,192,193,37,138,194,195,196,197,142,175,198,199,200,201,50,202,148,203,204],"youtube notetaker","notetaker","workflow","official","notes","code","markdown","slides","annotations","README","study","dair-academy","viewer",{"skillNo":206,"name":207,"nameZh":6,"description":208,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":209,"categories":210,"keywords":212,"publishedAt":38},"01M6Q0E55F0GW5MX48V8HXS8B5","youtube-full","Fetch YouTube transcripts, search videos, browse channels, and extract playlists via TranscriptAPI — no yt-dlp, no Google API key, works from any cloud server.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fyoutube-full\u002FSKILL.md",[211],{"categoryNo":160,"categoryName":161,"taxonomyType":98,"taxonomyTypeDesc":99},[213,137,214,215,138,172,173,216,217,174,175,176,145,218,177,25,50,178,219,151],"youtube full","full","google","server","dlp","credits","automatic"]