[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6F9PA06T3SSGFEVMXD7V6BM":3,"skill-same:01M6F9PA06T3SSGFEVMXD7V6BM":106},{"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":41,"linkOnly":42,"markdownContent":43,"markdownBody":44,"frontMatter":45,"refName":53,"commitSha":54,"skillDirectory":55,"forksCount":56,"repositoryHtmlUrl":57,"repositoryHomepageUrl":6,"ownerHtmlUrl":58,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":59,"install":60,"resources":73},"01M6F9PA06T3SSGFEVMXD7V6BM","omp-delegate",null,"Delegate coding tasks to Oh My Pi (`omp`) only when the user explicitly requests it, while the orchestrator retains review and landing responsibility.","boisenoise\u002Fskills-collections","boisenoise","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F193180?v=4","01M6CDBDQK6BDN55ZMA6B6PKBM","01M6CDBDVSJ3JPTBYN26FZ7TZK",12,"MIT","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-omp-delegate\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40],"omp delegate","omp","delegate","orchestrator","2026","when","login","agent-orchestration","critical","commands","community","files","only","review","read","node","Bash","api","git","run","tasks","orchestration","cli","2026-11-10 10:12:30",false,"---\nname: omp-delegate\ndescription: Delegate coding tasks to Oh My Pi (`omp`) 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 `omp` CLI installed and authenticated (`\u002Flogin` inside\n  omp, or a provider API-key environment variable), Node 18+, and git. The orchestrating\n  agent must be able to run shell commands and read files. Shell examples assume bash\u002Fzsh\n  (macOS\u002FLinux, or Git Bash\u002FWSL on Windows).\nmetadata:\n  version: 0.5.0\n---\n## Bundled upstream support\n\nSupporting files are included at skill-relative paths. See [UPSTREAM-NOTICE.md](UPSTREAM-NOTICE.md) for their pinned sources, licenses, hashes, and import changes.\n\n# Oh My Pi Delegate\n\n## When to Use\n\n- You want to delegate a bounded coding task to a separate `omp` implementer (`Oh My Pi`) and then review its diff yourself.\n- The user explicitly asked for delegation to this implementer.\n\nYou are the **orchestrator**. Delegate a bounded coding task to a separate **implementer** - Oh My\nPi (`omp`) - then review what it produced and land it yourself. You write the brief and own the\njudgment; the implementer makes changes in its own session; 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 binary is `omp`, not `pi`\n\nOh My Pi is a fork of Pi. This skill drives **`omp`** (`@oh-my-pi\u002Fpi-coding-agent`). The original\nPi CLI is a different binary (`pi`) with a different skill (`pi-delegate`). If `omp` is missing but\n`pi` is installed, you have Pi, not Oh My Pi.\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 `omp` CLI is not installed or authenticated.\n- The user asked for the original Pi CLI (`pi`) — use `pi-delegate`.\n- You need a sandboxed implementer. Oh My Pi has no sandbox. `--read-only` restricts the tool\n  surface; a write-capable run executes without prompts (`--yolo`).\n\n## Prerequisites (check once)\n\n1. Install omp with `bun install -g @oh-my-pi\u002Fpi-coding-agent` (or the install path from\n   https:\u002F\u002Fomp.sh).\n2. Authenticate: `\u002Flogin` inside omp for a subscription provider, or an API-key environment\n   variable for an API-key provider. Credentials live under `~\u002F.omp\u002F`.\n3. Confirm `omp --version` succeeds.\n4. Work in, or point `--cd` at, the target git repository.\n\n## Choose the model (optional)\n\nOmit `--model` (and `--provider`) to use omp's configured default for this project \u002F profile. The\ncatalog is **this install's** authenticated providers — not a fixed list in this skill.\n\nTo pick another model:\n\n1. **List what this install can actually run.** Do **not** pass `omp --list-models` — that flag is\n   gone and omp treats it as an unknown flag (exit 2). Use the `models` subcommand:\n   - `omp models` — every available model, grouped by provider\n   - `omp models --json` — the same catalog, machine-readable\n   - `omp models find \u003Csubstring>` — filter by provider, id, or name (example:\n     `omp models find sonnet`)\n   - `omp models \u003Cprovider>` — one provider's models\n2. **Pass that id to the relay.** `--model \u003Cpattern>` is omp's own `--model`: a fuzzy match against\n   the catalog (provider\u002Fid, a bare id, or a unique substring). `--provider \u003Cname>` pins the\n   provider when the pattern is ambiguous.\n3. The relay forwards only letters, digits, and `. _ : \u002F -`. Glob patterns with `*` are rejected.\n\n`--thinking \u003Clevel>` is a separate reasoning dial, not a model id. Allowed values: `off`, `auto`,\n`minimal`, `low`, `medium`, `high`, `xhigh`, `max`. The relay rejects anything else (including\n`inherit`) before dispatch — omp would otherwise warn and ignore a bad value.\n\nA fleet lane (`--lane`) can set `provider`, `model`, and `effort`. Lane `effort` becomes\n`--thinking`; an explicit `--thinking` \u002F `--model` \u002F `--provider` flag wins over the lane.\n\nThe relay does not forward `--api-key`, `--smol`, `--slow`, or `--plan`. Those stay omp's own CLI.\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\nOh My Pi sees only the text you send plus what it can inspect in the workspace - no chat history or\nshared context. Include the goal, current state, what to change, what to leave untouched, the\nproject's **actual** gates, and a report contract. Tell omp not to commit. Keep one task per brief.\nomp auto-loads `AGENTS.md`\u002F`CLAUDE.md` context files from the workspace and its parents, so repo\ninstructions reach it without inlining. See\n[references\u002Fwriting-the-brief.md](references\u002Fwriting-the-brief.md).\n\n### 2. Dispatch\n\nUse the bundled relay. It pipes the brief to `omp --mode json` on stdin, captures the JSON event\nstream, and writes `result.json`. (`\u003Cskill-dir>` is the installed folder containing this\n`SKILL.md`.)\n\n```bash\nnode \"\u003Cskill-dir>\u002Fscripts\u002Frelay.mjs\" --brief brief.txt --cd \u002Fpath\u002Fto\u002Frepo\n# list models first:                       omp models   (or: omp models --json)\n# choose a model:                          add --model \u003Cid from omp models>\n# choose a provider:                       add --provider \u003Cname>\n# set thinking level:                      add --thinking high\n# read-only run (review\u002Fdiagnosis):        add --read-only\n# trust project .omp resources:            add --approve\n# resume the most recent session:          add --resume-last  (delta brief only)\n# resume a specific session:               add --session \u003Cid> (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 relay writes artifacts under the system temp dir\nby default and never commits. See [references\u002Fdispatch-and-poll.md](references\u002Fdispatch-and-poll.md).\n\n### 3. Wait for completion\n\nThe relay blocks until omp finishes. Run it with the orchestrator's background-command facility,\nor background it in the shell and poll for `result.json`. A pre-run usage error exits 2 and writes\nno result; a missing `omp` exits 127 and writes `status: \"omp_unavailable\"`.\n\nTrust process state and the working tree over a progress display. Completion means the process\nexited and `result.json` exists. omp's full report is the `finalMessage` field in `result.json`\n(also printed in full on stdout between the report markers).\n\n### 4. Review - do not trust the self-report\n\nTreat omp'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\nSee [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\npass and the diff holds, and commit is authorized. If rework is needed, send a delta brief with `--resume-last` or\n`--session \u003Cid>`, then review again.\n\n## Autonomy and permissions\n\nOh My Pi has **no sandbox**. Print mode has no approval UI, so a write-capable relay run always\npasses `--yolo` (`tools.approvalMode: yolo`) — otherwise a user's `always-ask` or `write` config\nwould stall until the watchdog. The other controls are:\n\n1. `--read-only` restricts omp's callable tools to `--tools read,grep,glob`. It does not pass\n   `--yolo`. Installed extension code still runs with the user's host permissions if project\n   resources are trusted.\n2. The relay passes `--no-extensions --no-skills --no-rules` by default, so project `.omp`\n   extensions, skills, and rules stay undiscovered. `--approve` is the explicit opt-in for a\n   repository the user trusts.\n3. `touchedFiles` and the diff are the record of what changed. Inspect them after every run.\n\n## Authorization model\n\nDelegation is something the human opts into. Once they have (\"run this queue\", \"proceed\"),\ncommitting verified work is permitted only when included in the user-authorized task; delegation alone does not widen that scope. Two limits remain: **surface, don't\nabsorb** (report omp's design decisions, defensible-but-unasked turns, and non-blocking nitpicks)\nand **stop for scope changes** (if correct completion needs going beyond the brief, ask instead of\nexpanding the mandate). 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, stdin delivery, model listing, 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, commit\n  boundary, and rework through omp sessions.\n- [references\u002Fmulti-task-queues.md](references\u002Fmulti-task-queues.md) - sequential queues,\n  constraint carry-forward, progress tracking, and the final coherence pass.\n\n\n## Limitations\n\n- Runtime helper `scripts\u002Frelay.mjs` is bundled from the revision recorded in `UPSTREAM-NOTICE.md`. Requires the corresponding installed and authenticated CLI, Node 18+, and 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) — MIT; relay runtime bundled with local changes in UPSTREAM-NOTICE.md.\n","## Bundled upstream support\n\nSupporting files are included at skill-relative paths. See [UPSTREAM-NOTICE.md](UPSTREAM-NOTICE.md) for their pinned sources, licenses, hashes, and import changes.\n\n# Oh My Pi Delegate\n\n## When to Use\n\n- You want to delegate a bounded coding task to a separate `omp` implementer (`Oh My Pi`) and then review its diff yourself.\n- The user explicitly asked for delegation to this implementer.\n\nYou are the **orchestrator**. Delegate a bounded coding task to a separate **implementer** - Oh My\nPi (`omp`) - then review what it produced and land it yourself. You write the brief and own the\njudgment; the implementer makes changes in its own session; 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 binary is `omp`, not `pi`\n\nOh My Pi is a fork of Pi. This skill drives **`omp`** (`@oh-my-pi\u002Fpi-coding-agent`). The original\nPi CLI is a different binary (`pi`) with a different skill (`pi-delegate`). If `omp` is missing but\n`pi` is installed, you have Pi, not Oh My Pi.\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 `omp` CLI is not installed or authenticated.\n- The user asked for the original Pi CLI (`pi`) — use `pi-delegate`.\n- You need a sandboxed implementer. Oh My Pi has no sandbox. `--read-only` restricts the tool\n  surface; a write-capable run executes without prompts (`--yolo`).\n\n## Prerequisites (check once)\n\n1. Install omp with `bun install -g @oh-my-pi\u002Fpi-coding-agent` (or the install path from\n   https:\u002F\u002Fomp.sh).\n2. Authenticate: `\u002Flogin` inside omp for a subscription provider, or an API-key environment\n   variable for an API-key provider. Credentials live under `~\u002F.omp\u002F`.\n3. Confirm `omp --version` succeeds.\n4. Work in, or point `--cd` at, the target git repository.\n\n## Choose the model (optional)\n\nOmit `--model` (and `--provider`) to use omp's configured default for this project \u002F profile. The\ncatalog is **this install's** authenticated providers — not a fixed list in this skill.\n\nTo pick another model:\n\n1. **List what this install can actually run.** Do **not** pass `omp --list-models` — that flag is\n   gone and omp treats it as an unknown flag (exit 2). Use the `models` subcommand:\n   - `omp models` — every available model, grouped by provider\n   - `omp models --json` — the same catalog, machine-readable\n   - `omp models find \u003Csubstring>` — filter by provider, id, or name (example:\n     `omp models find sonnet`)\n   - `omp models \u003Cprovider>` — one provider's models\n2. **Pass that id to the relay.** `--model \u003Cpattern>` is omp's own `--model`: a fuzzy match against\n   the catalog (provider\u002Fid, a bare id, or a unique substring). `--provider \u003Cname>` pins the\n   provider when the pattern is ambiguous.\n3. The relay forwards only letters, digits, and `. _ : \u002F -`. Glob patterns with `*` are rejected.\n\n`--thinking \u003Clevel>` is a separate reasoning dial, not a model id. Allowed values: `off`, `auto`,\n`minimal`, `low`, `medium`, `high`, `xhigh`, `max`. The relay rejects anything else (including\n`inherit`) before dispatch — omp would otherwise warn and ignore a bad value.\n\nA fleet lane (`--lane`) can set `provider`, `model`, and `effort`. Lane `effort` becomes\n`--thinking`; an explicit `--thinking` \u002F `--model` \u002F `--provider` flag wins over the lane.\n\nThe relay does not forward `--api-key`, `--smol`, `--slow`, or `--plan`. Those stay omp's own CLI.\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\nOh My Pi sees only the text you send plus what it can inspect in the workspace - no chat history or\nshared context. Include the goal, current state, what to change, what to leave untouched, the\nproject's **actual** gates, and a report contract. Tell omp not to commit. Keep one task per brief.\nomp auto-loads `AGENTS.md`\u002F`CLAUDE.md` context files from the workspace and its parents, so repo\ninstructions reach it without inlining. See\n[references\u002Fwriting-the-brief.md](references\u002Fwriting-the-brief.md).\n\n### 2. Dispatch\n\nUse the bundled relay. It pipes the brief to `omp --mode json` on stdin, captures the JSON event\nstream, and writes `result.json`. (`\u003Cskill-dir>` is the installed folder containing this\n`SKILL.md`.)\n\n```bash\nnode \"\u003Cskill-dir>\u002Fscripts\u002Frelay.mjs\" --brief brief.txt --cd \u002Fpath\u002Fto\u002Frepo\n# list models first:                       omp models   (or: omp models --json)\n# choose a model:                          add --model \u003Cid from omp models>\n# choose a provider:                       add --provider \u003Cname>\n# set thinking level:                      add --thinking high\n# read-only run (review\u002Fdiagnosis):        add --read-only\n# trust project .omp resources:            add --approve\n# resume the most recent session:          add --resume-last  (delta brief only)\n# resume a specific session:               add --session \u003Cid> (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 relay writes artifacts under the system temp dir\nby default and never commits. See [references\u002Fdispatch-and-poll.md](references\u002Fdispatch-and-poll.md).\n\n### 3. Wait for completion\n\nThe relay blocks until omp finishes. Run it with the orchestrator's background-command facility,\nor background it in the shell and poll for `result.json`. A pre-run usage error exits 2 and writes\nno result; a missing `omp` exits 127 and writes `status: \"omp_unavailable\"`.\n\nTrust process state and the working tree over a progress display. Completion means the process\nexited and `result.json` exists. omp's full report is the `finalMessage` field in `result.json`\n(also printed in full on stdout between the report markers).\n\n### 4. Review - do not trust the self-report\n\nTreat omp'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\nSee [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\npass and the diff holds, and commit is authorized. If rework is needed, send a delta brief with `--resume-last` or\n`--session \u003Cid>`, then review again.\n\n## Autonomy and permissions\n\nOh My Pi has **no sandbox**. Print mode has no approval UI, so a write-capable relay run always\npasses `--yolo` (`tools.approvalMode: yolo`) — otherwise a user's `always-ask` or `write` config\nwould stall until the watchdog. The other controls are:\n\n1. `--read-only` restricts omp's callable tools to `--tools read,grep,glob`. It does not pass\n   `--yolo`. Installed extension code still runs with the user's host permissions if project\n   resources are trusted.\n2. The relay passes `--no-extensions --no-skills --no-rules` by default, so project `.omp`\n   extensions, skills, and rules stay undiscovered. `--approve` is the explicit opt-in for a\n   repository the user trusts.\n3. `touchedFiles` and the diff are the record of what changed. Inspect them after every run.\n\n## Authorization model\n\nDelegation is something the human opts into. Once they have (\"run this queue\", \"proceed\"),\ncommitting verified work is permitted only when included in the user-authorized task; delegation alone does not widen that scope. Two limits remain: **surface, don't\nabsorb** (report omp's design decisions, defensible-but-unasked turns, and non-blocking nitpicks)\nand **stop for scope changes** (if correct completion needs going beyond the brief, ask instead of\nexpanding the mandate). 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, stdin delivery, model listing, 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, commit\n  boundary, and rework through omp sessions.\n- [references\u002Fmulti-task-queues.md](references\u002Fmulti-task-queues.md) - sequential queues,\n  constraint carry-forward, progress tracking, and the final coherence pass.\n\n\n## Limitations\n\n- Runtime helper `scripts\u002Frelay.mjs` is bundled from the revision recorded in `UPSTREAM-NOTICE.md`. Requires the corresponding installed and authenticated CLI, Node 18+, and 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) — MIT; relay runtime bundled with local changes in UPSTREAM-NOTICE.md.\n",{"name":5,"risk":26,"source":46,"license":14,"category":25,"metadata":47,"date_added":49,"description":7,"source_repo":50,"source_type":28,"compatibility":51,"license_source":52},"https:\u002F\u002Fgithub.com\u002FamElnagdy\u002Fdelegate-skills",{"version":48},"0.5.0","2026-08-26","amElnagdy\u002Fdelegate-skills","Requires the `omp` CLI installed and authenticated (`\u002Flogin` inside omp, or a provider API-key environment variable), 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","7bf2279c8a65758319526a721d5c4b75683aec9c","skills\u002Fantigravity-omp-delegate",3,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections","https:\u002F\u002Fgithub.com\u002Fboisenoise","2026-11-12 14:21:24",{"source":8,"skillName":5,"commands":61,"prompt":71,"zipAvailable":72},[62,65,68],{"tool":63,"command":64},"npx","npx skills add boisenoise\u002Fskills-collections --skill omp-delegate",{"tool":66,"command":67},"bunx","bunx skills add boisenoise\u002Fskills-collections --skill omp-delegate",{"tool":69,"command":70},"pnpm","pnpm dlx skills add boisenoise\u002Fskills-collections --skill omp-delegate","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-omp-delegate\u002FSKILL.md",true,[74,80,84,88,92,98,102],{"path":75,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Fdispatch-and-poll.md","REFERENCE","参考文档",9174,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-omp-delegate\u002Freferences\u002Fdispatch-and-poll.md",{"path":81,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Fmulti-task-queues.md",2312,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-omp-delegate\u002Freferences\u002Fmulti-task-queues.md",{"path":85,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":86,"sourceHtmlUrl":87},"references\u002Freview-and-land.md",4791,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-omp-delegate\u002Freferences\u002Freview-and-land.md",{"path":89,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":90,"sourceHtmlUrl":91},"references\u002Fwriting-the-brief.md",6825,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-omp-delegate\u002Freferences\u002Fwriting-the-brief.md",{"path":93,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":96,"sourceHtmlUrl":97},"scripts\u002Frelay.mjs","SCRIPT","脚本",33105,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-omp-delegate\u002Fscripts\u002Frelay.mjs",{"path":99,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":100,"sourceHtmlUrl":101},"UPSTREAM-LICENSE.txt",1083,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-omp-delegate\u002FUPSTREAM-LICENSE.txt",{"path":103,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":104,"sourceHtmlUrl":105},"UPSTREAM-NOTICE.md",1437,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-omp-delegate\u002FUPSTREAM-NOTICE.md",[107,132,159,185,204,227],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":111,"licenseFileUrl":112,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":41},"01M6WNH92BHVFXHGPDZCPJ0AG0","web-access","Use Treg for public web or platform data only when existing search, browser and connected tools cannot cover the task, with explicit cost and data boundaries.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-web-access\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-web-access\u002FSKILL.md",[],[116,117,118,119,120,121,122,123,124,32,125,30,126,127,128,26,129,130,131,23,22],"web","access","web access","official","development","browser","search","data","Tools","fetch","youtube","free tools","platform","free","cover","normal",{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":111,"licenseFileUrl":136,"sourceHtmlUrl":137,"categories":138,"keywords":144,"publishedAt":41},"01M6WNF9XAYAB2CZDDJBAKNM93","treg","Use the Treg CLI or MCP catalog to discover, price and call authorized external tools with team-scoped credentials and a user-approved budget.","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-treg\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-treg\u002FSKILL.md",[139],{"categoryNo":140,"categoryName":141,"taxonomyType":142,"taxonomyTypeDesc":143},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[134,145,40,146,119,120,147,124,148,149,150,151,152,153,154,26,155,156,157,158,22],"MCP","github","license","Budget","credentials","team","catalog","use","call","discover","external tools","with","scoped","blob",{"skillNo":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":111,"licenseFileUrl":163,"sourceHtmlUrl":164,"categories":165,"keywords":171,"publishedAt":41},"01M6WN93MEAZ4E41DYAHJRPHQT","recruit","Turn a job description into an evidence-linked candidate shortlist through Treg, with job-related ranking and optional authorized business contact enrichment.","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-recruit\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-recruit\u002FSKILL.md",[166],{"categoryNo":167,"categoryName":168,"taxonomyType":169,"taxonomyTypeDesc":170},"01JBSEEDCAT000000000000038","人力资源","PROFESSION","适用职业",[161,146,119,147,172,173,174,175,176,177,26,178,179,180,156,181,182,183,184,158,134,22],"https","email","enrichment","business","evidence","phone","ranking","post","job description","for","person","candidate","reason",{"skillNo":186,"name":187,"nameZh":6,"description":188,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":111,"licenseFileUrl":189,"sourceHtmlUrl":190,"categories":191,"keywords":192,"publishedAt":41},"01M6WN8R5RXSMHM9B4D9FAFX42","rea-growth","Analyze a company’s public growth and content through Treg, distinguish observations from hypotheses, and produce an evidence-linked playbook within an approved budget.","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-rea-growth\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-rea-growth\u002FSKILL.md",[],[193,194,195,146,119,147,196,197,172,198,148,199,200,201,176,26,202,203,158,134,22],"growth","rea","rea growth","produce","content","playbook","marketing","analyze","public","observations","company",{"skillNo":205,"name":206,"nameZh":6,"description":207,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":111,"licenseFileUrl":208,"sourceHtmlUrl":209,"categories":210,"keywords":211,"publishedAt":41},"01M6WN2EVE3RQRGWAKBT4S7YT2","make-ugc","Create original AI UGC-style product videos through Treg: research hooks, approve a licensed presenter and voice, generate clips, add captions and report costs.","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-make-ugc\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-make-ugc\u002FSKILL.md",[],[212,213,146,214,119,215,147,216,217,218,219,220,26,221,222,223,224,225,226,158],"make","make ugc","research","create","Video","Captions","ads","short","hooks","head","style","niche","trending","talking-head","approve",{"skillNo":228,"name":229,"nameZh":6,"description":230,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":111,"licenseFileUrl":231,"sourceHtmlUrl":232,"categories":233,"keywords":234,"publishedAt":41},"01M6WN10ARAA63Y8K1YNGXJ2RM","lead-signals","Find and qualify public buying signals through Treg, rank fitting business accounts and optionally enrich authorized business contact information.","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-lead-signals\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-lead-signals\u002FSKILL.md",[],[235,236,237,146,119,147,238,239,175,240,241,26,242,243,244,245,246,247,248,158],"signals","lead","lead signals","how","find","ready","as","how to","qualify","people","information","enrich","changes","funding"]