[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6P0SBR5MAWS81W3RCMZ7BWJ":3,"skill-same:01M6P0SBR5MAWS81W3RCMZ7BWJ":80},{"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},"01M6P0SBR5MAWS81W3RCMZ7BWJ","delegate-setup",null,"Configure approved delegation lanes across installed implementer CLIs, including optional model and effort choices, then write global or project config only after explicit user approval.","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\u002Fdelegate-setup\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"setup","delegate setup","delegate","node","agent-orchestration","project","across","community","only","implementer","write","safe","model","configure","https","license","delegation","config","orchestration","github","2026-11-10 10:12:30",false,"---\nname: delegate-setup\ndescription: Configure approved delegation lanes across installed implementer CLIs,\n  including optional model and effort choices, then write global or project config\n  only after explicit user approval.\nrisk: safe\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 Node 18+. No implementer CLIs are required — the skill discovers\n  what is available.\nmetadata:\n  version: 0.5.0\n---\n# Delegate Setup\n\n## When to Use\n\n- You want to configure which implementer CLI handles which kind of work (fleet lanes).\n- You need to discover installed implementers and write lane config after user approval.\n\nYou are the **orchestrator** in **setup mode**. Discover installed implementer CLIs, propose a\n**fleet of lanes**, and write configuration only after the user approves.\n\nThis skill does **not** dispatch coding work. It only authors the lane map.\n\nOne concept: **lanes**. Never say “routes.”\n\nExample lane: **feature** → implementer `opencode`, model `opencode\u002Fgrok`, variant `high`\n(OpenCode uses `variant` for reasoning intensity, not `effort`).\n\n## When NOT to use this\n\n- The user wants a task implemented — use the matching `*-delegate` skill instead.\n- A one-off model change on a single dispatch — pass `--model` \u002F `--effort` \u002F `--variant` on that relay.\n\n## Hard rules\n\n1. Every lane **must** include `implementer`.\n2. Put dials on the same object (`model`, `effort` or `variant`, …) only if that implementer supports them — see [references\u002Fschema.md](references\u002Fschema.md).\n3. Show a human-readable lane table **and** the full JSON before every write; re-show after every tweak.\n4. Write **only** after an explicit approval (“yes”, “approve”, “write it”).\n5. Ask scope unless already clear: **global** (all projects) vs **this repo only**. Never create a project file just because cwd is a git repo. If there is no git repo, default to global and say so.\n6. Do not invent model identifiers.\n7. In interview or usage-scan mode, never write **any** dial the user did not give you and the schema does not require — omit it, so the CLI’s or relay’s own default applies.\n8. Prefer 3–5 useful lanes over a kitchen-sink map.\n9. Never edit `AGENTS.md`, `CLAUDE.md`, or other user agent-instruction files.\n10. Never run a `*-delegate` relay from this skill.\n\n(`\u003Cskill-dir>` is this skill’s install directory — the folder that contains this `SKILL.md`.)\n\n## Flow\n\n`discover → load → grounding menu → propose (with Basis) → scope → approve → write`\n\n### 1. Discover\n\n```bash\nnode \"\u003Cskill-dir>\u002Fscripts\u002Fdiscover.mjs\"\n```\n\nSummarize installed vs missing, auth (`true` \u002F `false` \u002F `null` = unknown), and whether models were\n`reported`, `aliases` (curated aliases in the registry, not live discovery — full model names also\nwork), `unsupported`, or `failed`.\n\n### 2. Load existing (effective map)\n\n```bash\nnode \"\u003Cskill-dir>\u002Fscripts\u002Fconfig.mjs\" load --cwd \"$PWD\"\n```\n\n- Neither present → “No lanes configured yet.”\n- Otherwise → table of **effective** lanes with a Source column (`global` \u002F `project`). Do not paste\n  both raw files unless asked.\n- If `projectPresent` is true and `projectTrusted` is false, label the project lanes **untrusted**.\n  They cannot dispatch until the user reviews and approves a project write.\n\n### 3. Propose\n\nDiscovery reports capability, never task fit. So ask **one** grounding question before proposing\nanything — one question, three options, not a wizard:\n\n> How should I pick the lanes? **(1) Quick defaults** — I decide, no questions.\n> **(2) Interview** — about four questions on how you want work allocated.\n> **(3) Usage scan** — I re-read your CLIs’ local session folders (counts and dates only, never the\n> conversations) and let the numbers place your lanes — if one CLI dominates, expect one question\n> about its role. Happy to do 2 and 3 together.\n\n- **Quick defaults** → propose immediately.\n- **Interview** → the four questions (allocation policy, never model rankings) and how to ask them\n  (one medium per round) live in [references\u002Fsetup-dialogue.md](references\u002Fsetup-dialogue.md) — read\n  it before you ask.\n- **Usage scan** → `node \"\u003Cskill-dir>\u002Fscripts\u002Fdiscover.mjs\" --usage`. Tell the user it is metadata\n  only before running it. Each discovered CLI gains `usage: { sessions, lastUsed }`; `null` means no\n  probe is wired — unknown, not unused.\n- **Both** → run the scan first, then ask only what the numbers cannot answer.\n- Inside a git repo, repo signals (languages, test weight, frontend share) are a fourth source of\n  evidence. They do not change the menu; they feed the proposal and the `repo` basis.\n\n**That menu is also the consent surface** — the option chosen sets how much of the map is yours to\ndecide:\n\n- **Quick defaults** — the user hired your opinion. A full map is legitimate, dials included; label\n  every lane `my opinion`, say plainly that the map is your opinion, and keep it cheap to revise.\n- **Interview \u002F usage scan** — evidence modes, so **every** dial is gated (rule 7): set one only from\n  the user’s answer, or where the schema requires it (opencode lanes require `model`). Omitting is\n  always safe — every dial has a default the user already lives with, and a CLI’s configured default\n  is their standing choice, better evidence than your priors. Choosing which installed implementer\n  gets a lane is still yours — Basis `my opinion` — but a dial that raises spend is not: offer your\n  dial picks only as an addendum after the proposal, see\n  [references\u002Fsetup-dialogue.md](references\u002Fsetup-dialogue.md).\n- **An unanswered question shrinks the map; it never licenses a substitution.** Propose fewer, more\n  conservative lanes, name the axis you are blind on (no quota answer → say the map is quota-blind),\n  and invite the answer anytime. Re-ask once at most; never backfill silence with priors.\n\n**Delegation economics.** The orchestrator reviews and lands every result — the review is the\nquality gate, so optimize total cost, not implementer prestige:\n\n- Prefer capable, authenticated, burnable, **low-usage** CLIs for bounded, objectively gated work\n  (tests, mechanical refactors, straightforward fixes) when their reliability keeps review and\n  rework economical — lanes push token burn away from the subscriptions the user is protecting.\n  Low usage alone does not establish burnable: discovery cannot see plans, limits, or per-run\n  cost, and a rarely-used CLI may be metered or deliberately avoided. Burnable comes from the\n  user's quota answer — or, in quick defaults, from your labeled opinion.\n- Avoid binding a lane to a CLI the user is protecting or orchestrates from, by default; bind it\n  only when the user asks for it or no acceptable alternative exists. Lanes are\n  **orchestrator-blind**: the same lane fires from every seat the user drives from, and from that\n  CLI's own seat it dispatches the CLI to itself.\n- Surplus placement breaks down when rework and review cost exceed the savings; when the\n  implementer is flaky; when correctness rides on security, concurrency, migrations, or unstated\n  domain knowledge; and when the output **is** the product (debate, architecture, research) —\n  review limits damage, it does not manufacture a good first attempt. Bind those lanes to stronger\n  implementers.\n- An explicit \"spare X\" answer removes X from proposed lanes by default, and overrides blanket\n  posture answers on any lane the user explicitly retains for X — ask whether the posture applies\n  there; omit the dial if unanswered. Never silently stretch one answer across an axis it\n  conflicts with.\n\nQuestion phrasings for the burn\u002Fspare and trust interview live in\n[references\u002Fsetup-dialogue.md](references\u002Fsetup-dialogue.md).\n\nThen propose the lanes. Name them after the work the user described; fall back to `feature`, `tests`,\n`ui`, `fast`, `complex`. Installed implementers only.\n\nShow:\n\n| Lane | Implementer | Model | Effort \u002F variant | Basis | Source (if updating) |\n| --- | --- | --- | --- | --- | --- |\n| feature | opencode | opencode\u002Fgrok | variant: high | your answer + schema requirement | — |\n| tests | codex | — | — | usage data | — |\n| ui | claude | — | — | my opinion (implementer) | — |\n\n**Basis** is mandatory on every lane: `your answer` \u002F `usage data` \u002F `repo` \u002F `my opinion` \u002F\n`schema requirement` (a dial the schema forces is neither evidence nor opinion — say so). A lane you\npicked from model-quality priors is `my opinion` — never present it as something the tooling\ndetermined, and “installed and authenticated” is capability, not evidence of fit. When a lane’s\nimplementer and its dials come from different places, split the label — see\n[references\u002Fsetup-dialogue.md](references\u002Fsetup-dialogue.md).\n\nThen the **complete** JSON (`version`: `delegate-fleet.v1`). One line of why per lane; flag auth or\nmodel uncertainty.\n\nSchema and dial table: [references\u002Fschema.md](references\u002Fschema.md).\n\n### 4. Scope\n\n- User said global \u002F all projects \u002F outside the project → `global`.\n- No git repo → `global` (say so).\n- Else ask once: global vs this repo only.\n\n### 5. Approve and write\n\nOn explicit yes, write **only** the chosen scope (validate first). Build the payload from that\nscope’s raw file (or an empty `lanes` object if new) — not from the effective merged `load` view,\nor a project write will shadow global-only lanes and a global write will promote project-only ones.\n\nCreate a uniquely named file under the platform temporary directory (`$TMPDIR`, `%TEMP%`, or Node\n`os.tmpdir()`; never hard-code `\u002Ftmp`, which breaks on native Windows), write the **exact approved\nJSON** into it with the orchestrator's file-writing tool, and use that populated path as\n`\u003Clanes-json>` below. Never validate an empty temp file. Remove the temp file after the\nvalidation\u002Fwrite attempt, whether it succeeds or fails.\n\n```bash\nnode \"\u003Cskill-dir>\u002Fscripts\u002Fconfig.mjs\" validate \"\u003Clanes-json>\"\nnode \"\u003Cskill-dir>\u002Fscripts\u002Fconfig.mjs\" write --scope global \"\u003Clanes-json>\"\n# or:  write --scope project --cwd \u002Fpath\u002Fto\u002Frepo \"\u003Clanes-json>\"\n```\n\nRe-read with `load`, then confirm the path written and the active lane names. Project writes bind\napproval to the exact config content; later changes fail closed until re-approved. On update, a short\nbefore\u002Fafter is enough.\n\n### 6. Ready to delegate\n\nStop after confirming. Tell the user the map is ready. For later work: read the lane’s\n`implementer`, load that `*-delegate` skill, and dispatch with `--lane \u003Cname>` (explicit\n`--model` \u002F `--effort` \u002F `--variant` still win when passed). Do not start a delegate task\nunless they ask.\n\n## Reconfigure\n\nSame flow. Show the effective current map, propose changes, approve, write one scope’s file.\nReinstalling the skills package must not rewrite these files — they live outside the package.\n\n\n## Limitations\n\n- Never dispatches work itself — only discovers CLIs and writes config after explicit approval.\n- Docs-only import — executable helpers (`scripts\u002F`) not included; see upstream for full runtime. Requires Node 18+.\n\n> Adapted from [amElnagdy\u002Fdelegate-skills](https:\u002F\u002Fgithub.com\u002FamElnagdy\u002Fdelegate-skills) (MIT) — docs-only, runtime not bundled.\n","# Delegate Setup\n\n## When to Use\n\n- You want to configure which implementer CLI handles which kind of work (fleet lanes).\n- You need to discover installed implementers and write lane config after user approval.\n\nYou are the **orchestrator** in **setup mode**. Discover installed implementer CLIs, propose a\n**fleet of lanes**, and write configuration only after the user approves.\n\nThis skill does **not** dispatch coding work. It only authors the lane map.\n\nOne concept: **lanes**. Never say “routes.”\n\nExample lane: **feature** → implementer `opencode`, model `opencode\u002Fgrok`, variant `high`\n(OpenCode uses `variant` for reasoning intensity, not `effort`).\n\n## When NOT to use this\n\n- The user wants a task implemented — use the matching `*-delegate` skill instead.\n- A one-off model change on a single dispatch — pass `--model` \u002F `--effort` \u002F `--variant` on that relay.\n\n## Hard rules\n\n1. Every lane **must** include `implementer`.\n2. Put dials on the same object (`model`, `effort` or `variant`, …) only if that implementer supports them — see [references\u002Fschema.md](references\u002Fschema.md).\n3. Show a human-readable lane table **and** the full JSON before every write; re-show after every tweak.\n4. Write **only** after an explicit approval (“yes”, “approve”, “write it”).\n5. Ask scope unless already clear: **global** (all projects) vs **this repo only**. Never create a project file just because cwd is a git repo. If there is no git repo, default to global and say so.\n6. Do not invent model identifiers.\n7. In interview or usage-scan mode, never write **any** dial the user did not give you and the schema does not require — omit it, so the CLI’s or relay’s own default applies.\n8. Prefer 3–5 useful lanes over a kitchen-sink map.\n9. Never edit `AGENTS.md`, `CLAUDE.md`, or other user agent-instruction files.\n10. Never run a `*-delegate` relay from this skill.\n\n(`\u003Cskill-dir>` is this skill’s install directory — the folder that contains this `SKILL.md`.)\n\n## Flow\n\n`discover → load → grounding menu → propose (with Basis) → scope → approve → write`\n\n### 1. Discover\n\n```bash\nnode \"\u003Cskill-dir>\u002Fscripts\u002Fdiscover.mjs\"\n```\n\nSummarize installed vs missing, auth (`true` \u002F `false` \u002F `null` = unknown), and whether models were\n`reported`, `aliases` (curated aliases in the registry, not live discovery — full model names also\nwork), `unsupported`, or `failed`.\n\n### 2. Load existing (effective map)\n\n```bash\nnode \"\u003Cskill-dir>\u002Fscripts\u002Fconfig.mjs\" load --cwd \"$PWD\"\n```\n\n- Neither present → “No lanes configured yet.”\n- Otherwise → table of **effective** lanes with a Source column (`global` \u002F `project`). Do not paste\n  both raw files unless asked.\n- If `projectPresent` is true and `projectTrusted` is false, label the project lanes **untrusted**.\n  They cannot dispatch until the user reviews and approves a project write.\n\n### 3. Propose\n\nDiscovery reports capability, never task fit. So ask **one** grounding question before proposing\nanything — one question, three options, not a wizard:\n\n> How should I pick the lanes? **(1) Quick defaults** — I decide, no questions.\n> **(2) Interview** — about four questions on how you want work allocated.\n> **(3) Usage scan** — I re-read your CLIs’ local session folders (counts and dates only, never the\n> conversations) and let the numbers place your lanes — if one CLI dominates, expect one question\n> about its role. Happy to do 2 and 3 together.\n\n- **Quick defaults** → propose immediately.\n- **Interview** → the four questions (allocation policy, never model rankings) and how to ask them\n  (one medium per round) live in [references\u002Fsetup-dialogue.md](references\u002Fsetup-dialogue.md) — read\n  it before you ask.\n- **Usage scan** → `node \"\u003Cskill-dir>\u002Fscripts\u002Fdiscover.mjs\" --usage`. Tell the user it is metadata\n  only before running it. Each discovered CLI gains `usage: { sessions, lastUsed }`; `null` means no\n  probe is wired — unknown, not unused.\n- **Both** → run the scan first, then ask only what the numbers cannot answer.\n- Inside a git repo, repo signals (languages, test weight, frontend share) are a fourth source of\n  evidence. They do not change the menu; they feed the proposal and the `repo` basis.\n\n**That menu is also the consent surface** — the option chosen sets how much of the map is yours to\ndecide:\n\n- **Quick defaults** — the user hired your opinion. A full map is legitimate, dials included; label\n  every lane `my opinion`, say plainly that the map is your opinion, and keep it cheap to revise.\n- **Interview \u002F usage scan** — evidence modes, so **every** dial is gated (rule 7): set one only from\n  the user’s answer, or where the schema requires it (opencode lanes require `model`). Omitting is\n  always safe — every dial has a default the user already lives with, and a CLI’s configured default\n  is their standing choice, better evidence than your priors. Choosing which installed implementer\n  gets a lane is still yours — Basis `my opinion` — but a dial that raises spend is not: offer your\n  dial picks only as an addendum after the proposal, see\n  [references\u002Fsetup-dialogue.md](references\u002Fsetup-dialogue.md).\n- **An unanswered question shrinks the map; it never licenses a substitution.** Propose fewer, more\n  conservative lanes, name the axis you are blind on (no quota answer → say the map is quota-blind),\n  and invite the answer anytime. Re-ask once at most; never backfill silence with priors.\n\n**Delegation economics.** The orchestrator reviews and lands every result — the review is the\nquality gate, so optimize total cost, not implementer prestige:\n\n- Prefer capable, authenticated, burnable, **low-usage** CLIs for bounded, objectively gated work\n  (tests, mechanical refactors, straightforward fixes) when their reliability keeps review and\n  rework economical — lanes push token burn away from the subscriptions the user is protecting.\n  Low usage alone does not establish burnable: discovery cannot see plans, limits, or per-run\n  cost, and a rarely-used CLI may be metered or deliberately avoided. Burnable comes from the\n  user's quota answer — or, in quick defaults, from your labeled opinion.\n- Avoid binding a lane to a CLI the user is protecting or orchestrates from, by default; bind it\n  only when the user asks for it or no acceptable alternative exists. Lanes are\n  **orchestrator-blind**: the same lane fires from every seat the user drives from, and from that\n  CLI's own seat it dispatches the CLI to itself.\n- Surplus placement breaks down when rework and review cost exceed the savings; when the\n  implementer is flaky; when correctness rides on security, concurrency, migrations, or unstated\n  domain knowledge; and when the output **is** the product (debate, architecture, research) —\n  review limits damage, it does not manufacture a good first attempt. Bind those lanes to stronger\n  implementers.\n- An explicit \"spare X\" answer removes X from proposed lanes by default, and overrides blanket\n  posture answers on any lane the user explicitly retains for X — ask whether the posture applies\n  there; omit the dial if unanswered. Never silently stretch one answer across an axis it\n  conflicts with.\n\nQuestion phrasings for the burn\u002Fspare and trust interview live in\n[references\u002Fsetup-dialogue.md](references\u002Fsetup-dialogue.md).\n\nThen propose the lanes. Name them after the work the user described; fall back to `feature`, `tests`,\n`ui`, `fast`, `complex`. Installed implementers only.\n\nShow:\n\n| Lane | Implementer | Model | Effort \u002F variant | Basis | Source (if updating) |\n| --- | --- | --- | --- | --- | --- |\n| feature | opencode | opencode\u002Fgrok | variant: high | your answer + schema requirement | — |\n| tests | codex | — | — | usage data | — |\n| ui | claude | — | — | my opinion (implementer) | — |\n\n**Basis** is mandatory on every lane: `your answer` \u002F `usage data` \u002F `repo` \u002F `my opinion` \u002F\n`schema requirement` (a dial the schema forces is neither evidence nor opinion — say so). A lane you\npicked from model-quality priors is `my opinion` — never present it as something the tooling\ndetermined, and “installed and authenticated” is capability, not evidence of fit. When a lane’s\nimplementer and its dials come from different places, split the label — see\n[references\u002Fsetup-dialogue.md](references\u002Fsetup-dialogue.md).\n\nThen the **complete** JSON (`version`: `delegate-fleet.v1`). One line of why per lane; flag auth or\nmodel uncertainty.\n\nSchema and dial table: [references\u002Fschema.md](references\u002Fschema.md).\n\n### 4. Scope\n\n- User said global \u002F all projects \u002F outside the project → `global`.\n- No git repo → `global` (say so).\n- Else ask once: global vs this repo only.\n\n### 5. Approve and write\n\nOn explicit yes, write **only** the chosen scope (validate first). Build the payload from that\nscope’s raw file (or an empty `lanes` object if new) — not from the effective merged `load` view,\nor a project write will shadow global-only lanes and a global write will promote project-only ones.\n\nCreate a uniquely named file under the platform temporary directory (`$TMPDIR`, `%TEMP%`, or Node\n`os.tmpdir()`; never hard-code `\u002Ftmp`, which breaks on native Windows), write the **exact approved\nJSON** into it with the orchestrator's file-writing tool, and use that populated path as\n`\u003Clanes-json>` below. Never validate an empty temp file. Remove the temp file after the\nvalidation\u002Fwrite attempt, whether it succeeds or fails.\n\n```bash\nnode \"\u003Cskill-dir>\u002Fscripts\u002Fconfig.mjs\" validate \"\u003Clanes-json>\"\nnode \"\u003Cskill-dir>\u002Fscripts\u002Fconfig.mjs\" write --scope global \"\u003Clanes-json>\"\n# or:  write --scope project --cwd \u002Fpath\u002Fto\u002Frepo \"\u003Clanes-json>\"\n```\n\nRe-read with `load`, then confirm the path written and the active lane names. Project writes bind\napproval to the exact config content; later changes fail closed until re-approved. On update, a short\nbefore\u002Fafter is enough.\n\n### 6. Ready to delegate\n\nStop after confirming. Tell the user the map is ready. For later work: read the lane’s\n`implementer`, load that `*-delegate` skill, and dispatch with `--lane \u003Cname>` (explicit\n`--model` \u002F `--effort` \u002F `--variant` still win when passed). Do not start a delegate task\nunless they ask.\n\n## Reconfigure\n\nSame flow. Show the effective current map, propose changes, approve, write one scope’s file.\nReinstalling the skills package must not rewrite these files — they live outside the package.\n\n\n## Limitations\n\n- Never dispatches work itself — only discovers CLIs and writes config after explicit approval.\n- Docs-only import — executable helpers (`scripts\u002F`) not included; see upstream for full runtime. Requires Node 18+.\n\n> Adapted from [amElnagdy\u002Fdelegate-skills](https:\u002F\u002Fgithub.com\u002FamElnagdy\u002Fdelegate-skills) (MIT) — docs-only, runtime not bundled.\n",{"name":5,"risk":29,"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 Node 18+. No implementer CLIs are required — the skill discovers what is available.","https:\u002F\u002Fgithub.com\u002FamElnagdy\u002Fdelegate-skills\u002Fblob\u002Fmaster\u002FLICENSE","main","f3312ba749561b6159f477dbfc9313c875d40a56",".agents\u002Fskills_archive\u002Fdelegate-setup","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 delegate-setup",{"tool":62,"command":63},"bunx","bunx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill delegate-setup",{"tool":65,"command":66},"pnpm","pnpm dlx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill delegate-setup","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fdelegate-setup\u002FSKILL.md",true,[70,76],{"path":71,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002Fschema.md","REFERENCE","参考文档",5131,"https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fdelegate-setup\u002Freferences\u002Fschema.md",{"path":77,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Fsetup-dialogue.md",6958,"https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fdelegate-setup\u002Freferences\u002Fsetup-dialogue.md",[81,108,127,148,176,200],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":92,"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",[87],{"categoryNo":88,"categoryName":89,"taxonomyType":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000011","运维与部署","SCENARIO","使用场景",[93,94,95,96,97,98,83,99,100,101,31,26,25,50,102,103,104,105,106,107],"ZeRO","trust","zero trust","architecture","assessment","verification","segmentation","devops-security","access","active","critical","scope","scripts","relevant","implementing",{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"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",[],[20,115,116,117,118,36,119,120,121,30,21,122,123,26,124,25,125,126,103,22],"zcode","zcode delegate","review","cli","tasks","run","Bash","read","orchestrator","files","desktop app","app",{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":133,"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",[],[134,135,136,29,37,137,138,33,32,139,140,141,142,25,50,143,144,145,146,147],"transcript","youtube transcript","youtube","codex","research","text","fetch","tooling","clean","local","output","deepapi","youtube transcripts","blob",{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":165,"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",[154,157,160],{"categoryNo":155,"categoryName":156,"taxonomyType":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":158,"categoryName":159,"taxonomyType":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":161,"categoryName":162,"taxonomyType":163,"taxonomyTypeDesc":164},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[134,135,136,166,29,167,37,137,33,168,169,170,171,140,172,25,50,173,174,175],"youtube transcript skills","gemini","search","api","Video","browse","api-integration","free","card","channels",{"skillNo":177,"name":178,"nameZh":6,"description":179,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":180,"categories":181,"keywords":186,"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",[182,185],{"categoryNo":183,"categoryName":184,"taxonomyType":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":158,"categoryName":159,"taxonomyType":90,"taxonomyTypeDesc":91},[136,187,188,118,29,189,190,191,192,33,170,193,194,195,196,50,197,143,198,199],"youtube notetaker","notetaker","workflow","official","notes","code","markdown","slides","annotations","README","study","dair-academy","viewer",{"skillNo":201,"name":202,"nameZh":6,"description":203,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":204,"categories":205,"keywords":207,"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",[206],{"categoryNo":155,"categoryName":156,"taxonomyType":90,"taxonomyTypeDesc":91},[208,136,209,210,29,167,168,211,212,169,170,171,140,213,172,25,50,173,214,146],"youtube full","full","google","server","dlp","credits","automatic"]