[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6NTQT4M7P1RNNJARCGRHS1Q":3,"skill-same:01M6NTQT4M7P1RNNJARCGRHS1Q":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},"01M6NTQT4M7P1RNNJARCGRHS1Q","aider-delegate",null,"Delegate coding tasks to Aider (`aider`) 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\u002Faider-delegate\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"aider","aider delegate","delegate","read","agent-orchestration","critical","local","community","files","only","orchestrator","review","model","Bash","api","SET","run","tasks","orchestration","cli","2026-11-10 10:12:30",false,"---\nname: aider-delegate\ndescription: Delegate coding tasks to Aider (`aider`) 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 `aider` CLI (`python -m pip install aider-chat`), Node\n  18+, and git. Aider must be able to authenticate to a model before dispatch - export\n  the provider key it expects (`OPENAI_API_KEY`, `ANTHROPIC_API_KEY`, …) or set it\n  in Aider's own config; a local OpenAI-compatible endpoint still needs a non-empty\n  `OPENAI_API_KEY`. The orchestrating agent must be able to run shell commands and\n  read files. Shell examples assume bash\u002Fzsh (macOS\u002FLinux, or Git Bash\u002FWSL on Windows).\nmetadata:\n  version: 0.5.0\n---\n# Aider Delegate\n\n## When to Use\n\n- You want to delegate a bounded coding task to a separate `aider` implementer (`Aider`) and then review its diff yourself.\n- The user explicitly asked for delegation to this implementer.\n\nYou are the **orchestrator**. Hand a bounded coding task to a separate **implementer** - Aider - then\nreview what it produced and land it yourself. You write the brief and own the judgment; Aider does the\ntyping in its own run; you verify and commit.\n\nThe loop needs only a shell command and file access, so any comparable orchestrator can drive it.\n\n## The one thing to know about Aider\n\n**Aider commits by default.** Two of its defaults would destroy the reviewable diff this skill exists\nto produce:\n\n- `--auto-commits` (default `True`) - Aider commits its own edits after each exchange.\n- `--dirty-commits` (default `True`) - Aider commits **your** pre-existing uncommitted work before it\n  starts editing.\n\nThe relay always passes `--no-auto-commits` and `--no-dirty-commits`, and neither is configurable\nthrough it. If you ever drive `aider` by hand instead of through the relay, pass both yourself, or the\nwork lands as commits you never reviewed. The relay also passes `--no-gitignore`, because Aider\notherwise writes `.aider*` into `.gitignore` on startup and dirties the tree you are about to read.\n\n## When NOT to use this\n\n- The task is small enough to do inline; delegation overhead is not worth it.\n- The `aider` CLI is not installed, or no model is configured for it.\n- You want the implementer to manage its own commits. Aider can, but this skill deliberately turns\n  that off - the diff is the deliverable.\n\n## Prerequisites (check once)\n\n1. Install Aider - `python -m pip install aider-chat`, or the standalone installer from the\n   [Aider install docs](https:\u002F\u002Faider.chat\u002Fdocs\u002Finstall.html).\n2. Configure a model. Aider reads provider keys from the environment (`OPENAI_API_KEY`,\n   `ANTHROPIC_API_KEY`, …) or its own config; see [Aider's model docs](https:\u002F\u002Faider.chat\u002Fdocs\u002Fllms.html).\n3. Confirm `aider --version` succeeds.\n4. Work in, or point `--cd` at, the target git repository.\n\n## Choose the model\n\nAider uses its own configured model when `--model` is omitted. Pass `--model \u003Cname>` to pick another.\n\n## Local and self-hosted models\n\nAider talks to any OpenAI-compatible endpoint, so this is also the skill for delegating to a model\nrunning on the user's own hardware - llama.cpp's server, Ollama, vLLM, LM Studio, or anything else\nthat serves the same API. Pair `--model` with `--api-base`:\n\n```bash\nnode \"\u003Cskill-dir>\u002Fscripts\u002Frelay.mjs\" --brief brief.txt --cd \u002Fpath\u002Fto\u002Frepo \\\n  --model openai\u002F\u003Cserved-model-name> --api-base http:\u002F\u002F127.0.0.1:\u003Cport>\u002Fv1\n```\n\nThree things differ from a hosted provider:\n\n- **The `openai\u002F` prefix is required.** It tells Aider to speak the OpenAI protocol to your endpoint;\n  the part after it is whatever name your server reports, not a provider catalog name.\n- **A placeholder key is still needed.** Export any non-empty `OPENAI_API_KEY`. The client library\n  requires the header even when the server ignores its value.\n- **Ask for a smaller edit format.** Local models often fail Aider's default `diff` format, which\n  requires exact search\u002Freplace blocks. `--edit-format whole` trades tokens for reliability; keep the\n  brief's scope tight with `--file` so whole-file rewrites stay cheap.\n\nA local endpoint that is not running looks like a hang, not an error: Aider retries the connection\nuntil the relay's `--timeout` watchdog fires and reports `status: \"timeout\"`. Confirm the server is up\nbefore dispatching a long brief.\n\n### Staying offline\n\nNo account or provider registration is involved: Aider is a pip install, the endpoint is yours, and\n`OPENAI_API_KEY` only has to be non-empty. The relay pins the flags that would otherwise reach the\nnetwork on their own - `--no-check-update`, `--no-analytics` (Aider's own default is `random`, which\nopts some sessions in by itself), and `--no-detect-urls`, without which Aider offers to scrape any URL\nin the brief and `--yes-always` accepts that offer silently.\n\n`--no-suggest-shell-commands` closes the remaining path by which a run could reach the network without\nbeing asked to. What stays outside the relay's control is the brief itself: instructions that tell\nAider to install a package or call an API will still be carried out, and `--auto-lint` runs the\nrepository's own tooling. Offline here means nothing in the dispatch path reaches out on its own - not\nthat a sandbox is stopping it.\n\n## The loop\n\nRun these five steps per task. Steps 1, 4, and 5 require judgment; 2 and 3 are mechanical.\n\n### 1. Write the brief\n\nAider sees only the text you send plus the files in its editing scope - no chat history or shared\ncontext. Include the goal, current state, what to change, what to leave untouched, the project's\n**actual** gates, and a report contract. Keep one task per brief. See\n[references\u002Fwriting-the-brief.md](references\u002Fwriting-the-brief.md).\n\n### 2. Dispatch\n\nUse the bundled helper. It wraps Aider's headless `--message-file` mode, captures the run, and writes\n`result.json`. (`\u003Cskill-dir>` is the installed folder containing this `SKILL.md`.)\n\n```bash\nnode \"\u003Cskill-dir>\u002Fscripts\u002Frelay.mjs\" --brief brief.txt --cd \u002Fpath\u002Fto\u002Frepo\n# choose a model:                        add --model \u003Cname>\n# point at an OpenAI-compatible server:  add --api-base \u003Curl>\n# scope the edit surface:                add --file \u003Cpath> (repeatable), --read \u003Cpath> for context only\n# dry run, no files modified:            add --read-only\n# continue the previous chat:            add --resume-last  (delta brief only)\n# hard time limit (watchdog):            add --timeout 2h  (the 30m default suits short runs; implementation briefs routinely need 1-2h)\n# see all options:                       node ...\u002Frelay.mjs --help\n```\n\nThe child process's cwd pins the workspace. The brief is delivered with `--message-file`, so it never\nrides argv: it stays out of the host process list and clear of the OS argument size cap. The relay\nwrites artifacts under the system temp dir by default and never commits. See\n[references\u002Fdispatch-and-poll.md](references\u002Fdispatch-and-poll.md).\n\n### 3. Wait for completion\n\nThe helper blocks until Aider finishes. Run it with the orchestrator's background-command facility, or\nbackground it in the shell and poll for `result.json`. A pre-run usage error exits 2 and writes no\nresult; a missing `aider` exits 127 and writes `status: \"aider_unavailable\"`.\n\nTrust process state and the working tree over a progress display. Completion means the process exited\nand `result.json` exists. Aider's report is the `finalMessage` field in `result.json` (also printed in\nfull on stdout between the report markers).\n\nAider exits 0 even when it never reached a model, so the relay scans the run for Aider's own endpoint\nand authentication errors and reports `status: \"failed\"` when it finds one. Treat a `failed` status\nwith an `error` mentioning the endpoint as a configuration problem, not a coding failure.\n\n### 4. Review - do not trust the self-report\n\nTreat Aider's final message and gate claims as claims:\n\n- Re-run the project's gates yourself.\n- Read the diff against the brief, starting with `touchedFiles`.\n- Run relevant guard skills if installed.\n- Round-trip migrations and grep for dangling references after removals or renames.\n\nAider's `--auto-lint` is on by default, so it may have already run a linter and fixed its own\ncomplaints. That is Aider's lint, not your gates - run yours anyway. See\n[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.** Commit only after the gates pass\nand the diff holds. If rework is needed, send a delta brief with `--resume-last`, then review again.\n\n## Autonomy and permissions\n\nThe relay passes `--yes-always`, Aider's own term for auto-confirming every prompt, because a headless\nrun cannot answer one. **Understand what that consents to in advance.** Auto-confirmation applies to\nevery prompt Aider would otherwise raise, and Aider's prompts are not limited to file edits: left at\nits defaults it also offers to run shell commands it has suggested, and `--yes-always` would accept\nthose with nobody reading them. The relay therefore pins `--no-suggest-shell-commands`, which removes\nthat path.\n\nWhat remains is not a sandbox, and nothing here pretends otherwise. Aider has no permission modes and\nno isolation: within its file scope it edits freely, and `--auto-lint` (on by default) runs whatever\nlinter the repository configures. A brief that tells Aider to run a command still gets a command run.\nDelegation is the authorization; if a run must not be able to touch the host, run it in a container or\na throwaway worktree, because no flag in this relay will give you that.\n\n**File selection is not a security boundary.** `--file`, `--read`, and `--subtree-only` set what Aider\nputs in its chat context, which is a scoping and token-cost decision. They do not confine what it can\nreach. See [references\u002Fwriting-the-brief.md](references\u002Fwriting-the-brief.md).\n\n`--read-only` maps to Aider's `--dry-run`, which performs the run without modifying files. The relay\ndoes not independently verify that claim - it reports what `git status --porcelain` shows and warns if\na `--read-only` run left the tree changed. `touchedFiles` and the diff, not a flag, are the guarantee.\n\n## Resume\n\nAider has no session ids. Its resume unit is the chat history file it keeps in the repository\n(`.aider.chat.history.md`), so `--resume-last` maps to Aider's `--restore-chat-history` and\n`--history-file` pins a specific one. Because that history lives in the repo, resume is per-worktree,\nnot per-user: two clones of the same project do not share it.\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. Two limits remain: **surface, don't absorb**\n(report Aider's design decisions, defensible-but-unasked turns, and non-blocking nitpicks) and **stop\nfor scope changes** (if correct completion needs going beyond the brief, ask instead of expanding the\nmandate). See [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) - structure, report contract,\n  real gates, file scope, and delta briefs.\n- [references\u002Fdispatch-and-poll.md](references\u002Fdispatch-and-poll.md) - flags, artifacts,\n  `result.json`, polling, and failure recovery.\n- [references\u002Freview-and-land.md](references\u002Freview-and-land.md) - review checklist, the commit\n  boundary, and rework through Aider's chat history.\n- [references\u002Fmulti-task-queues.md](references\u002Fmulti-task-queues.md) - sequential queues, constraint\n  carry-forward, progress tracking, and the final coherence pass.\n\n\n## Limitations\n\n- Docs-only import — executable `scripts\u002Frelay.mjs` not included; see upstream for full runtime. Requires `aider` 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","# Aider Delegate\n\n## When to Use\n\n- You want to delegate a bounded coding task to a separate `aider` implementer (`Aider`) and then review its diff yourself.\n- The user explicitly asked for delegation to this implementer.\n\nYou are the **orchestrator**. Hand a bounded coding task to a separate **implementer** - Aider - then\nreview what it produced and land it yourself. You write the brief and own the judgment; Aider does the\ntyping in its own run; you verify and commit.\n\nThe loop needs only a shell command and file access, so any comparable orchestrator can drive it.\n\n## The one thing to know about Aider\n\n**Aider commits by default.** Two of its defaults would destroy the reviewable diff this skill exists\nto produce:\n\n- `--auto-commits` (default `True`) - Aider commits its own edits after each exchange.\n- `--dirty-commits` (default `True`) - Aider commits **your** pre-existing uncommitted work before it\n  starts editing.\n\nThe relay always passes `--no-auto-commits` and `--no-dirty-commits`, and neither is configurable\nthrough it. If you ever drive `aider` by hand instead of through the relay, pass both yourself, or the\nwork lands as commits you never reviewed. The relay also passes `--no-gitignore`, because Aider\notherwise writes `.aider*` into `.gitignore` on startup and dirties the tree you are about to read.\n\n## When NOT to use this\n\n- The task is small enough to do inline; delegation overhead is not worth it.\n- The `aider` CLI is not installed, or no model is configured for it.\n- You want the implementer to manage its own commits. Aider can, but this skill deliberately turns\n  that off - the diff is the deliverable.\n\n## Prerequisites (check once)\n\n1. Install Aider - `python -m pip install aider-chat`, or the standalone installer from the\n   [Aider install docs](https:\u002F\u002Faider.chat\u002Fdocs\u002Finstall.html).\n2. Configure a model. Aider reads provider keys from the environment (`OPENAI_API_KEY`,\n   `ANTHROPIC_API_KEY`, …) or its own config; see [Aider's model docs](https:\u002F\u002Faider.chat\u002Fdocs\u002Fllms.html).\n3. Confirm `aider --version` succeeds.\n4. Work in, or point `--cd` at, the target git repository.\n\n## Choose the model\n\nAider uses its own configured model when `--model` is omitted. Pass `--model \u003Cname>` to pick another.\n\n## Local and self-hosted models\n\nAider talks to any OpenAI-compatible endpoint, so this is also the skill for delegating to a model\nrunning on the user's own hardware - llama.cpp's server, Ollama, vLLM, LM Studio, or anything else\nthat serves the same API. Pair `--model` with `--api-base`:\n\n```bash\nnode \"\u003Cskill-dir>\u002Fscripts\u002Frelay.mjs\" --brief brief.txt --cd \u002Fpath\u002Fto\u002Frepo \\\n  --model openai\u002F\u003Cserved-model-name> --api-base http:\u002F\u002F127.0.0.1:\u003Cport>\u002Fv1\n```\n\nThree things differ from a hosted provider:\n\n- **The `openai\u002F` prefix is required.** It tells Aider to speak the OpenAI protocol to your endpoint;\n  the part after it is whatever name your server reports, not a provider catalog name.\n- **A placeholder key is still needed.** Export any non-empty `OPENAI_API_KEY`. The client library\n  requires the header even when the server ignores its value.\n- **Ask for a smaller edit format.** Local models often fail Aider's default `diff` format, which\n  requires exact search\u002Freplace blocks. `--edit-format whole` trades tokens for reliability; keep the\n  brief's scope tight with `--file` so whole-file rewrites stay cheap.\n\nA local endpoint that is not running looks like a hang, not an error: Aider retries the connection\nuntil the relay's `--timeout` watchdog fires and reports `status: \"timeout\"`. Confirm the server is up\nbefore dispatching a long brief.\n\n### Staying offline\n\nNo account or provider registration is involved: Aider is a pip install, the endpoint is yours, and\n`OPENAI_API_KEY` only has to be non-empty. The relay pins the flags that would otherwise reach the\nnetwork on their own - `--no-check-update`, `--no-analytics` (Aider's own default is `random`, which\nopts some sessions in by itself), and `--no-detect-urls`, without which Aider offers to scrape any URL\nin the brief and `--yes-always` accepts that offer silently.\n\n`--no-suggest-shell-commands` closes the remaining path by which a run could reach the network without\nbeing asked to. What stays outside the relay's control is the brief itself: instructions that tell\nAider to install a package or call an API will still be carried out, and `--auto-lint` runs the\nrepository's own tooling. Offline here means nothing in the dispatch path reaches out on its own - not\nthat a sandbox is stopping it.\n\n## The loop\n\nRun these five steps per task. Steps 1, 4, and 5 require judgment; 2 and 3 are mechanical.\n\n### 1. Write the brief\n\nAider sees only the text you send plus the files in its editing scope - no chat history or shared\ncontext. Include the goal, current state, what to change, what to leave untouched, the project's\n**actual** gates, and a report contract. Keep one task per brief. See\n[references\u002Fwriting-the-brief.md](references\u002Fwriting-the-brief.md).\n\n### 2. Dispatch\n\nUse the bundled helper. It wraps Aider's headless `--message-file` mode, captures the run, and writes\n`result.json`. (`\u003Cskill-dir>` is the installed folder containing this `SKILL.md`.)\n\n```bash\nnode \"\u003Cskill-dir>\u002Fscripts\u002Frelay.mjs\" --brief brief.txt --cd \u002Fpath\u002Fto\u002Frepo\n# choose a model:                        add --model \u003Cname>\n# point at an OpenAI-compatible server:  add --api-base \u003Curl>\n# scope the edit surface:                add --file \u003Cpath> (repeatable), --read \u003Cpath> for context only\n# dry run, no files modified:            add --read-only\n# continue the previous chat:            add --resume-last  (delta brief only)\n# hard time limit (watchdog):            add --timeout 2h  (the 30m default suits short runs; implementation briefs routinely need 1-2h)\n# see all options:                       node ...\u002Frelay.mjs --help\n```\n\nThe child process's cwd pins the workspace. The brief is delivered with `--message-file`, so it never\nrides argv: it stays out of the host process list and clear of the OS argument size cap. The relay\nwrites artifacts under the system temp dir by default and never commits. See\n[references\u002Fdispatch-and-poll.md](references\u002Fdispatch-and-poll.md).\n\n### 3. Wait for completion\n\nThe helper blocks until Aider finishes. Run it with the orchestrator's background-command facility, or\nbackground it in the shell and poll for `result.json`. A pre-run usage error exits 2 and writes no\nresult; a missing `aider` exits 127 and writes `status: \"aider_unavailable\"`.\n\nTrust process state and the working tree over a progress display. Completion means the process exited\nand `result.json` exists. Aider's report is the `finalMessage` field in `result.json` (also printed in\nfull on stdout between the report markers).\n\nAider exits 0 even when it never reached a model, so the relay scans the run for Aider's own endpoint\nand authentication errors and reports `status: \"failed\"` when it finds one. Treat a `failed` status\nwith an `error` mentioning the endpoint as a configuration problem, not a coding failure.\n\n### 4. Review - do not trust the self-report\n\nTreat Aider's final message and gate claims as claims:\n\n- Re-run the project's gates yourself.\n- Read the diff against the brief, starting with `touchedFiles`.\n- Run relevant guard skills if installed.\n- Round-trip migrations and grep for dangling references after removals or renames.\n\nAider's `--auto-lint` is on by default, so it may have already run a linter and fixed its own\ncomplaints. That is Aider's lint, not your gates - run yours anyway. See\n[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.** Commit only after the gates pass\nand the diff holds. If rework is needed, send a delta brief with `--resume-last`, then review again.\n\n## Autonomy and permissions\n\nThe relay passes `--yes-always`, Aider's own term for auto-confirming every prompt, because a headless\nrun cannot answer one. **Understand what that consents to in advance.** Auto-confirmation applies to\nevery prompt Aider would otherwise raise, and Aider's prompts are not limited to file edits: left at\nits defaults it also offers to run shell commands it has suggested, and `--yes-always` would accept\nthose with nobody reading them. The relay therefore pins `--no-suggest-shell-commands`, which removes\nthat path.\n\nWhat remains is not a sandbox, and nothing here pretends otherwise. Aider has no permission modes and\nno isolation: within its file scope it edits freely, and `--auto-lint` (on by default) runs whatever\nlinter the repository configures. A brief that tells Aider to run a command still gets a command run.\nDelegation is the authorization; if a run must not be able to touch the host, run it in a container or\na throwaway worktree, because no flag in this relay will give you that.\n\n**File selection is not a security boundary.** `--file`, `--read`, and `--subtree-only` set what Aider\nputs in its chat context, which is a scoping and token-cost decision. They do not confine what it can\nreach. See [references\u002Fwriting-the-brief.md](references\u002Fwriting-the-brief.md).\n\n`--read-only` maps to Aider's `--dry-run`, which performs the run without modifying files. The relay\ndoes not independently verify that claim - it reports what `git status --porcelain` shows and warns if\na `--read-only` run left the tree changed. `touchedFiles` and the diff, not a flag, are the guarantee.\n\n## Resume\n\nAider has no session ids. Its resume unit is the chat history file it keeps in the repository\n(`.aider.chat.history.md`), so `--resume-last` maps to Aider's `--restore-chat-history` and\n`--history-file` pins a specific one. Because that history lives in the repo, resume is per-worktree,\nnot per-user: two clones of the same project do not share it.\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. Two limits remain: **surface, don't absorb**\n(report Aider's design decisions, defensible-but-unasked turns, and non-blocking nitpicks) and **stop\nfor scope changes** (if correct completion needs going beyond the brief, ask instead of expanding the\nmandate). See [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) - structure, report contract,\n  real gates, file scope, and delta briefs.\n- [references\u002Fdispatch-and-poll.md](references\u002Fdispatch-and-poll.md) - flags, artifacts,\n  `result.json`, polling, and failure recovery.\n- [references\u002Freview-and-land.md](references\u002Freview-and-land.md) - review checklist, the commit\n  boundary, and rework through Aider's chat history.\n- [references\u002Fmulti-task-queues.md](references\u002Fmulti-task-queues.md) - sequential queues, constraint\n  carry-forward, progress tracking, and the final coherence pass.\n\n\n## Limitations\n\n- Docs-only import — executable `scripts\u002Frelay.mjs` not included; see upstream for full runtime. Requires `aider` 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 `aider` CLI (`python -m pip install aider-chat`), Node 18+, and git. Aider must be able to authenticate to a model before dispatch - export the provider key it expects (`OPENAI_API_KEY`, `ANTHROPIC_API_KEY`, …) or set it in Aider's own config; a local OpenAI-compatible endpoint still needs a non-empty `OPENAI_API_KEY`. 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\u002Faider-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 aider-delegate",{"tool":62,"command":63},"bunx","bunx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill aider-delegate",{"tool":65,"command":66},"pnpm","pnpm dlx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill aider-delegate","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Faider-delegate\u002FSKILL.md",true,[70,76,80,84],{"path":71,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002Fdispatch-and-poll.md","REFERENCE","参考文档",9182,"https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Faider-delegate\u002Freferences\u002Fdispatch-and-poll.md",{"path":77,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Fmulti-task-queues.md",2868,"https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Faider-delegate\u002Freferences\u002Fmulti-task-queues.md",{"path":81,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Freview-and-land.md",5108,"https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Faider-delegate\u002Freferences\u002Freview-and-land.md",{"path":85,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":86,"sourceHtmlUrl":87},"references\u002Fwriting-the-brief.md",5681,"https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Faider-delegate\u002Freferences\u002Fwriting-the-brief.md",[89,116,128,152,179,203],{"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,27,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",[],[20,123,124,29,37,36,35,34,31,30,125,21,28,27,26,25,126,127,23,22],"zcode","zcode delegate","node","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,24,148,149,150,151],"transcript","youtube transcript","youtube","safe","github","codex","research","license","https","text","fetch","tooling","clean","output","deepapi","youtube transcripts","blob",{"skillNo":153,"name":154,"nameZh":6,"description":155,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":156,"categories":157,"keywords":169,"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",[158,161,164],{"categoryNo":159,"categoryName":160,"taxonomyType":98,"taxonomyTypeDesc":99},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":162,"categoryName":163,"taxonomyType":98,"taxonomyTypeDesc":99},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":165,"categoryName":166,"taxonomyType":167,"taxonomyTypeDesc":168},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[135,136,137,170,138,171,139,140,142,172,32,173,174,145,175,25,50,176,177,178],"youtube transcript skills","gemini","search","Video","browse","api-integration","free","card","channels",{"skillNo":180,"name":181,"nameZh":6,"description":182,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":183,"categories":184,"keywords":189,"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",[185,188],{"categoryNo":186,"categoryName":187,"taxonomyType":98,"taxonomyTypeDesc":99},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":162,"categoryName":163,"taxonomyType":98,"taxonomyTypeDesc":99},[137,190,191,37,138,192,193,194,195,142,173,196,197,198,199,50,200,24,201,202],"youtube notetaker","notetaker","workflow","official","notes","code","markdown","slides","annotations","README","study","dair-academy","viewer",{"skillNo":204,"name":205,"nameZh":6,"description":206,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":207,"categories":208,"keywords":210,"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",[209],{"categoryNo":159,"categoryName":160,"taxonomyType":98,"taxonomyTypeDesc":99},[211,137,212,213,138,171,172,214,215,32,173,174,145,216,175,25,50,176,217,150],"youtube full","full","google","server","dlp","credits","automatic"]