[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6F73WB4CVWRJA3T48FFEMRY":3,"skill-same:01M6F73WB4CVWRJA3T48FFEMRY":91},{"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":40,"linkOnly":41,"markdownContent":42,"markdownBody":43,"frontMatter":44,"refName":52,"commitSha":53,"skillDirectory":54,"forksCount":55,"repositoryHtmlUrl":56,"repositoryHomepageUrl":6,"ownerHtmlUrl":57,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":58,"install":59,"resources":72},"01M6F73WB4CVWRJA3T48FFEMRY","grok-delegate",null,"Delegate coding tasks to the Grok Build CLI 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-grok-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],"grok delegate","grok","delegate","when","review","agent-orchestration","critical","community","files","only","orchestrator","read","node","xai","access","Bash","api","beta","run","tasks","orchestration","cli","2026-11-10 10:12:30",false,"---\nname: grok-delegate\ndescription: Delegate coding tasks to the Grok Build CLI only when the user explicitly\n  requests it, while the orchestrator retains review and landing responsibility.\nrisk: critical\ncategory: agent-orchestration\nsource: https:\u002F\u002Fgithub.com\u002FamElnagdy\u002Fdelegate-skills\nsource_repo: amElnagdy\u002Fdelegate-skills\nsource_type: community\ndate_added: '2026-08-26'\nlicense: MIT\nlicense_source: https:\u002F\u002Fgithub.com\u002FamElnagdy\u002Fdelegate-skills\u002Fblob\u002Fmaster\u002FLICENSE\ncompatibility: Requires the `grok` CLI (Grok Build) installed and authenticated (`grok\n  login`, or `XAI_API_KEY`; beta access needs an eligible xAI subscription), Node\n  18+, and git. The orchestrating agent must be able to run shell commands and read\n  files. Shell examples assume bash\u002Fzsh (macOS\u002FLinux, or Git Bash\u002FWSL on Windows).\nmetadata:\n  version: 0.5.0\n---\n# Grok Delegate\n\n## When to Use\n\n- You want to delegate a bounded coding task to a separate `grok` implementer (`Grok Build`) and then review its diff yourself.\n- The user explicitly asked for delegation to this implementer.\n\nYou are the **orchestrator**. This skill lets you hand a bounded coding task to a separate\n**implementer** — the Grok Build CLI (`grok`) — then review what it produced and land it yourself. You\nwrite the brief and own the judgment; Grok does the typing under an explicit autonomy profile; you\nverify and commit.\n\nNothing here is specific to one orchestrating agent. The loop needs only the ability to run a shell\ncommand and read a file, so it works the same whether you are Claude Code, Cursor, OpenCode with a\nselected model, or any comparable agent. (It is designed for Claude Code and Cursor; treat other\norchestrators as designed-for, not yet proven.)\n\n## When NOT to use this\n\n- The task is small enough to just do inline — delegation overhead is not worth it.\n- The `grok` CLI is not installed, not authenticated, or the account lacks Grok Build beta access.\n- You want to write the code yourself, or you only need a review without an implementer run.\n\n## Prerequisites (check once)\n\n1. `grok version` succeeds. If not, install on any platform with\n   `npm i -g @xai-official\u002Fgrok` (or use the installer from xAI's official Grok CLI docs) and\n   authenticate (`grok login`, or `grok login --device-auth` on headless hosts, or set\n   `XAI_API_KEY`).\n2. **Confirm which `grok` is on PATH.** `command -v grok` shows the active binary and `grok version`\n   its version — the relay records the version it ran into `result.json`, so a stale binary is visible\n   after the fact.\n3. You are in (or will point `--cd` at) the target git repository.\n\n## The loop\n\nRun these five steps per task. Steps 1, 4, and 5 are your judgment; 2 and 3 are mechanical.\n\n### 1. Write the brief\n\nGrok sees **only** the text you send — no orchestrator chat history, no shared context. Everything the\ntask needs goes in the brief: the goal, the current state, what to change, what to leave untouched,\nthe project's **actual** gate commands (discover them from the repo's CLAUDE.md\u002FAGENTS.md\u002FMakefile —\ndo not assume), and a report contract. Tell Grok it will **not** commit (you will). Keep one task per\nbrief. Full guidance and a template: [references\u002Fwriting-the-brief.md](references\u002Fwriting-the-brief.md).\n\n### 2. Dispatch\n\nThis distribution contains documentation only; `scripts\u002Frelay.mjs` is absent. Obtain,\npin and review the upstream runtime separately before using these example commands.\nDo not search the whole home directory for an arbitrary relay and assume it is trusted.\nVerify the actual CLI version and supported permission flags before dispatch.\n\n```bash\nnode \"\u003Cskill-dir>\u002Fscripts\u002Frelay.mjs\" --brief brief.txt --cd \u002Fpath\u002Fto\u002Frepo\n# read-only (review\u002Fdiagnosis; best-effort — verify touchedFiles): add --read-only\n# continue the previous Grok session:       add --resume-last  (send only the delta brief)\n# hard time limit (watchdog):               add --timeout 2h  (default: off; implementation runs routinely need 1-2h)\n# see all options:                          node ...\u002Frelay.mjs --help\n```\n\nThe helper defaults to a write-capable (`workspace-write`) autonomy profile — `--always-approve` plus\n`--sandbox workspace` — and writes its artifacts to a temp dir, so the repo under review stays clean.\nIt **never commits** — see step 5. Mechanics, flags, and the `result.json` shape:\n[references\u002Fdispatch-and-poll.md](references\u002Fdispatch-and-poll.md).\n\n### 3. Wait for completion\n\nThe helper blocks until Grok finishes, so back it with whatever your orchestrator offers and resume\nwhen it returns:\n\n- **Claude Code:** run the Bash call with `run_in_background: true`; you are notified on completion.\n- **Plain shell \u002F other agents:** run it in the foreground for short tasks, or background it and poll\n  the result file — `… &` in bash\u002Fzsh (including Git Bash\u002FWSL), or your shell's equivalent (`Start-Job`\n  in PowerShell, `start \u002Fb` in cmd). The run is done when `result.json` exists with a `status`. (A\n  pre-run usage error — bad args or an empty brief — instead exits with code 2 and a stderr message and\n  writes no result file, so check the exit code too. A missing `grok` binary exits 127 but *does* write\n  a `result.json` with status `grok_unavailable`.)\n\nDo not trust progress trackers over reality: a run is finished when `result.json` is written and the\nprocess has exited. Read the working tree, not a status line. The implementer's full report is\nthe `finalMessage` field in `result.json` (also printed in full on stdout between the report markers).\n\n### 4. Review — do not trust the self-report\n\nGrok's `result.json` includes its own summary and gate claims. **Re-verify, don't accept:**\n\n- **Re-run the project's gates yourself** (the test\u002Flint\u002Fbuild commands from step 1). Never take\n  \"gates passed\" on faith.\n- **Read the diff** against the brief: did Grok do what was asked, nothing more (scope creep) and\n  nothing less? `touchedFiles` in the result is your starting point.\n- **Run the relevant guard skills** on the diff if you have them installed (clean-code-guard,\n  test-guard, etc. from `guard-skills`) — this skill produces the work; those skills judge it.\n- For schema\u002Fmigration changes, round-trip them; for removals, grep for dangling references.\n\nFull checklist: [references\u002Freview-and-land.md](references\u002Freview-and-land.md).\n\n### 5. Land it\n\n**The orchestrator commits.** Only after the gates pass and the diff holds:\n\n- Commit the verified work yourself, with a clear message.\n- If it needs changes, send a delta brief with `--resume-last` (don't restate the whole task) and\n  review again.\n\n## Autonomy model\n\nGrok's default permission mode is `ask`, which **blocks on approval prompts in a headless pipe**. The\nrelay therefore always sets autonomy explicitly:\n\n| Relay flag | What Grok gets | Use when |\n| --- | --- | --- |\n| *(default)* | `--always-approve --sandbox workspace` | Normal implementation — writes scoped to the working tree |\n| `--read-only` | `--sandbox read-only --permission-mode plan` | Review \u002F diagnosis — **best-effort, not enforced** (see caveat below) |\n| `--full-access` | `--always-approve --sandbox off` | Explicit opt-in when the task needs unrestricted tools |\n\n`--always-approve` alone would approve *all* tools (writes, shell, network) — closer to unrestricted\nthan to a workspace-scoped write. The effective filesystem\u002Fnetwork boundary must be verified for the installed version; a workspace sandbox is not a universal host boundary. Reach for `--full-access` only when the human asks for it.\n\n**`--read-only` is best-effort, not a hard guarantee.** The read-only sandbox restricts out-of-workspace\nfilesystem\u002Fnetwork access, not grok's own edit tool, and headless `plan` mode is advisory — a run\nverified here still wrote the working tree when told to. Use `--read-only` to *signal* review intent,\nbut always confirm `touchedFiles` afterward; treat the diff, not the flag, as the guarantee. The relay\nautomates a reporting tripwire: it compares parsed git porcelain and fingerprints the working-tree\nidentity and index entries of Git-visible paths that were already dirty. `readOnlyViolation` is `true`\nwhen either signal proves a change, `false` when coverage is complete and detects none, and `null` when\ncoverage is incomplete. Ignored paths, submodule internals, perfect restores, and attribution of\nconcurrent changes remain outside it, so the diff\nreview stays the guarantee.\n\n## Authorization model\n\nDelegation is something the human opts into. Once they have (\"run this queue\", \"proceed\"), committing\nverified, gate-passing work is the agreed contract — that is the whole point. Two limits on that\nmandate: **surface, don't absorb** (report Grok's design decisions, defensible-but-unasked turns, and\nnon-blocking nitpicks rather than silently keeping them) and **stop for scope changes** (if correct\ncompletion needs going beyond the brief, ask — don't expand the mandate yourself). The full treatment\nis in [references\u002Freview-and-land.md](references\u002Freview-and-land.md).\n\n## References\n\n- [references\u002Fwriting-the-brief.md](references\u002Fwriting-the-brief.md) — how to write a brief Grok can\n  execute blind: structure, XML blocks, the report contract, embedding the real gate commands.\n- [references\u002Fdispatch-and-poll.md](references\u002Fdispatch-and-poll.md) — `relay.mjs` flags, the\n  `result.json` contract, backgrounding per orchestrator, and recovery when a run misbehaves.\n- [references\u002Freview-and-land.md](references\u002Freview-and-land.md) — the review checklist, the commit\n  boundary, and the rework cycle via `--resume-last`.\n- [references\u002Fmulti-task-queues.md](references\u002Fmulti-task-queues.md) — running a sequential queue:\n  carrying constraints forward, progress tracking, and the end-of-run coherence check.\n\n\n## Limitations\n\n- Docs-only import — executable `scripts\u002Frelay.mjs` not included; see upstream for full runtime. Requires `grok` 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","# Grok Delegate\n\n## When to Use\n\n- You want to delegate a bounded coding task to a separate `grok` implementer (`Grok Build`) and then review its diff yourself.\n- The user explicitly asked for delegation to this implementer.\n\nYou are the **orchestrator**. This skill lets you hand a bounded coding task to a separate\n**implementer** — the Grok Build CLI (`grok`) — then review what it produced and land it yourself. You\nwrite the brief and own the judgment; Grok does the typing under an explicit autonomy profile; you\nverify and commit.\n\nNothing here is specific to one orchestrating agent. The loop needs only the ability to run a shell\ncommand and read a file, so it works the same whether you are Claude Code, Cursor, OpenCode with a\nselected model, or any comparable agent. (It is designed for Claude Code and Cursor; treat other\norchestrators as designed-for, not yet proven.)\n\n## When NOT to use this\n\n- The task is small enough to just do inline — delegation overhead is not worth it.\n- The `grok` CLI is not installed, not authenticated, or the account lacks Grok Build beta access.\n- You want to write the code yourself, or you only need a review without an implementer run.\n\n## Prerequisites (check once)\n\n1. `grok version` succeeds. If not, install on any platform with\n   `npm i -g @xai-official\u002Fgrok` (or use the installer from xAI's official Grok CLI docs) and\n   authenticate (`grok login`, or `grok login --device-auth` on headless hosts, or set\n   `XAI_API_KEY`).\n2. **Confirm which `grok` is on PATH.** `command -v grok` shows the active binary and `grok version`\n   its version — the relay records the version it ran into `result.json`, so a stale binary is visible\n   after the fact.\n3. You are in (or will point `--cd` at) the target git repository.\n\n## The loop\n\nRun these five steps per task. Steps 1, 4, and 5 are your judgment; 2 and 3 are mechanical.\n\n### 1. Write the brief\n\nGrok sees **only** the text you send — no orchestrator chat history, no shared context. Everything the\ntask needs goes in the brief: the goal, the current state, what to change, what to leave untouched,\nthe project's **actual** gate commands (discover them from the repo's CLAUDE.md\u002FAGENTS.md\u002FMakefile —\ndo not assume), and a report contract. Tell Grok it will **not** commit (you will). Keep one task per\nbrief. Full guidance and a template: [references\u002Fwriting-the-brief.md](references\u002Fwriting-the-brief.md).\n\n### 2. Dispatch\n\nThis distribution contains documentation only; `scripts\u002Frelay.mjs` is absent. Obtain,\npin and review the upstream runtime separately before using these example commands.\nDo not search the whole home directory for an arbitrary relay and assume it is trusted.\nVerify the actual CLI version and supported permission flags before dispatch.\n\n```bash\nnode \"\u003Cskill-dir>\u002Fscripts\u002Frelay.mjs\" --brief brief.txt --cd \u002Fpath\u002Fto\u002Frepo\n# read-only (review\u002Fdiagnosis; best-effort — verify touchedFiles): add --read-only\n# continue the previous Grok session:       add --resume-last  (send only the delta brief)\n# hard time limit (watchdog):               add --timeout 2h  (default: off; implementation runs routinely need 1-2h)\n# see all options:                          node ...\u002Frelay.mjs --help\n```\n\nThe helper defaults to a write-capable (`workspace-write`) autonomy profile — `--always-approve` plus\n`--sandbox workspace` — and writes its artifacts to a temp dir, so the repo under review stays clean.\nIt **never commits** — see step 5. Mechanics, flags, and the `result.json` shape:\n[references\u002Fdispatch-and-poll.md](references\u002Fdispatch-and-poll.md).\n\n### 3. Wait for completion\n\nThe helper blocks until Grok finishes, so back it with whatever your orchestrator offers and resume\nwhen it returns:\n\n- **Claude Code:** run the Bash call with `run_in_background: true`; you are notified on completion.\n- **Plain shell \u002F other agents:** run it in the foreground for short tasks, or background it and poll\n  the result file — `… &` in bash\u002Fzsh (including Git Bash\u002FWSL), or your shell's equivalent (`Start-Job`\n  in PowerShell, `start \u002Fb` in cmd). The run is done when `result.json` exists with a `status`. (A\n  pre-run usage error — bad args or an empty brief — instead exits with code 2 and a stderr message and\n  writes no result file, so check the exit code too. A missing `grok` binary exits 127 but *does* write\n  a `result.json` with status `grok_unavailable`.)\n\nDo not trust progress trackers over reality: a run is finished when `result.json` is written and the\nprocess has exited. Read the working tree, not a status line. The implementer's full report is\nthe `finalMessage` field in `result.json` (also printed in full on stdout between the report markers).\n\n### 4. Review — do not trust the self-report\n\nGrok's `result.json` includes its own summary and gate claims. **Re-verify, don't accept:**\n\n- **Re-run the project's gates yourself** (the test\u002Flint\u002Fbuild commands from step 1). Never take\n  \"gates passed\" on faith.\n- **Read the diff** against the brief: did Grok do what was asked, nothing more (scope creep) and\n  nothing less? `touchedFiles` in the result is your starting point.\n- **Run the relevant guard skills** on the diff if you have them installed (clean-code-guard,\n  test-guard, etc. from `guard-skills`) — this skill produces the work; those skills judge it.\n- For schema\u002Fmigration changes, round-trip them; for removals, grep for dangling references.\n\nFull checklist: [references\u002Freview-and-land.md](references\u002Freview-and-land.md).\n\n### 5. Land it\n\n**The orchestrator commits.** Only after the gates pass and the diff holds:\n\n- Commit the verified work yourself, with a clear message.\n- If it needs changes, send a delta brief with `--resume-last` (don't restate the whole task) and\n  review again.\n\n## Autonomy model\n\nGrok's default permission mode is `ask`, which **blocks on approval prompts in a headless pipe**. The\nrelay therefore always sets autonomy explicitly:\n\n| Relay flag | What Grok gets | Use when |\n| --- | --- | --- |\n| *(default)* | `--always-approve --sandbox workspace` | Normal implementation — writes scoped to the working tree |\n| `--read-only` | `--sandbox read-only --permission-mode plan` | Review \u002F diagnosis — **best-effort, not enforced** (see caveat below) |\n| `--full-access` | `--always-approve --sandbox off` | Explicit opt-in when the task needs unrestricted tools |\n\n`--always-approve` alone would approve *all* tools (writes, shell, network) — closer to unrestricted\nthan to a workspace-scoped write. The effective filesystem\u002Fnetwork boundary must be verified for the installed version; a workspace sandbox is not a universal host boundary. Reach for `--full-access` only when the human asks for it.\n\n**`--read-only` is best-effort, not a hard guarantee.** The read-only sandbox restricts out-of-workspace\nfilesystem\u002Fnetwork access, not grok's own edit tool, and headless `plan` mode is advisory — a run\nverified here still wrote the working tree when told to. Use `--read-only` to *signal* review intent,\nbut always confirm `touchedFiles` afterward; treat the diff, not the flag, as the guarantee. The relay\nautomates a reporting tripwire: it compares parsed git porcelain and fingerprints the working-tree\nidentity and index entries of Git-visible paths that were already dirty. `readOnlyViolation` is `true`\nwhen either signal proves a change, `false` when coverage is complete and detects none, and `null` when\ncoverage is incomplete. Ignored paths, submodule internals, perfect restores, and attribution of\nconcurrent changes remain outside it, so the diff\nreview stays the guarantee.\n\n## Authorization model\n\nDelegation is something the human opts into. Once they have (\"run this queue\", \"proceed\"), committing\nverified, gate-passing work is the agreed contract — that is the whole point. Two limits on that\nmandate: **surface, don't absorb** (report Grok's design decisions, defensible-but-unasked turns, and\nnon-blocking nitpicks rather than silently keeping them) and **stop for scope changes** (if correct\ncompletion needs going beyond the brief, ask — don't expand the mandate yourself). The full treatment\nis in [references\u002Freview-and-land.md](references\u002Freview-and-land.md).\n\n## References\n\n- [references\u002Fwriting-the-brief.md](references\u002Fwriting-the-brief.md) — how to write a brief Grok can\n  execute blind: structure, XML blocks, the report contract, embedding the real gate commands.\n- [references\u002Fdispatch-and-poll.md](references\u002Fdispatch-and-poll.md) — `relay.mjs` flags, the\n  `result.json` contract, backgrounding per orchestrator, and recovery when a run misbehaves.\n- [references\u002Freview-and-land.md](references\u002Freview-and-land.md) — the review checklist, the commit\n  boundary, and the rework cycle via `--resume-last`.\n- [references\u002Fmulti-task-queues.md](references\u002Fmulti-task-queues.md) — running a sequential queue:\n  carrying constraints forward, progress tracking, and the end-of-run coherence check.\n\n\n## Limitations\n\n- Docs-only import — executable `scripts\u002Frelay.mjs` not included; see upstream for full runtime. Requires `grok` 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":24,"source":45,"license":14,"category":23,"metadata":46,"date_added":48,"description":7,"source_repo":49,"source_type":25,"compatibility":50,"license_source":51},"https:\u002F\u002Fgithub.com\u002FamElnagdy\u002Fdelegate-skills",{"version":47},"0.5.0","2026-08-26","amElnagdy\u002Fdelegate-skills","Requires the `grok` CLI (Grok Build) installed and authenticated (`grok login`, or `XAI_API_KEY`; beta access needs an eligible xAI subscription), 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-grok-delegate",3,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections","https:\u002F\u002Fgithub.com\u002Fboisenoise","2026-11-11 14:20:43",{"source":8,"skillName":5,"commands":60,"prompt":70,"zipAvailable":71},[61,64,67],{"tool":62,"command":63},"npx","npx skills add boisenoise\u002Fskills-collections --skill grok-delegate",{"tool":65,"command":66},"bunx","bunx skills add boisenoise\u002Fskills-collections --skill grok-delegate",{"tool":68,"command":69},"pnpm","pnpm dlx skills add boisenoise\u002Fskills-collections --skill grok-delegate","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-grok-delegate\u002FSKILL.md",true,[73,79,83,87],{"path":74,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":77,"sourceHtmlUrl":78},"references\u002Fdispatch-and-poll.md","REFERENCE","参考文档",11105,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-grok-delegate\u002Freferences\u002Fdispatch-and-poll.md",{"path":80,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002Fmulti-task-queues.md",3841,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-grok-delegate\u002Freferences\u002Fmulti-task-queues.md",{"path":84,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":85,"sourceHtmlUrl":86},"references\u002Freview-and-land.md",8136,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-grok-delegate\u002Freferences\u002Freview-and-land.md",{"path":88,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":89,"sourceHtmlUrl":90},"references\u002Fwriting-the-brief.md",5882,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-grok-delegate\u002Freferences\u002Fwriting-the-brief.md",[92,117,144,170,189,212],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":96,"licenseFileUrl":97,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":40},"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",[],[101,32,102,103,104,105,106,107,108,29,109,27,110,111,112,24,113,114,115,21,116],"web","web access","official","development","browser","search","data","Tools","fetch","youtube","free tools","platform","free","cover","normal","2026",{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":96,"licenseFileUrl":121,"sourceHtmlUrl":122,"categories":123,"keywords":129,"publishedAt":40},"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",[124],{"categoryNo":125,"categoryName":126,"taxonomyType":127,"taxonomyTypeDesc":128},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[119,130,39,131,103,104,132,108,133,134,135,136,137,138,139,24,140,141,142,143,116],"MCP","github","license","Budget","credentials","team","catalog","use","call","discover","external tools","with","scoped","blob",{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":96,"licenseFileUrl":148,"sourceHtmlUrl":149,"categories":150,"keywords":156,"publishedAt":40},"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",[151],{"categoryNo":152,"categoryName":153,"taxonomyType":154,"taxonomyTypeDesc":155},"01JBSEEDCAT000000000000038","人力资源","PROFESSION","适用职业",[146,131,103,132,157,158,159,160,161,162,24,163,164,165,141,166,167,168,169,143,119,116],"https","email","enrichment","business","evidence","phone","ranking","post","job description","for","person","candidate","reason",{"skillNo":171,"name":172,"nameZh":6,"description":173,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":96,"licenseFileUrl":174,"sourceHtmlUrl":175,"categories":176,"keywords":177,"publishedAt":40},"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",[],[178,179,180,131,103,132,181,182,157,183,133,184,185,186,161,24,187,188,143,119,116],"growth","rea","rea growth","produce","content","playbook","marketing","analyze","public","observations","company",{"skillNo":190,"name":191,"nameZh":6,"description":192,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":96,"licenseFileUrl":193,"sourceHtmlUrl":194,"categories":195,"keywords":196,"publishedAt":40},"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",[],[197,198,131,199,103,200,132,201,202,203,204,205,24,206,207,208,209,210,211,143],"make","make ugc","research","create","Video","Captions","ads","short","hooks","head","style","niche","trending","talking-head","approve",{"skillNo":213,"name":214,"nameZh":6,"description":215,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":96,"licenseFileUrl":216,"sourceHtmlUrl":217,"categories":218,"keywords":219,"publishedAt":40},"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",[],[220,221,222,131,103,132,223,224,160,225,226,24,227,228,229,230,231,232,233,143],"signals","lead","lead signals","how","find","ready","as","how to","qualify","people","information","enrich","changes","funding"]