[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F0EB7MZ7JHSXP4D6MKFJ45":3,"skill-same:01M7F0EB7MZ7JHSXP4D6MKFJ45":74},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":34,"commitSha":35,"skillDirectory":36,"forksCount":37,"repositoryHtmlUrl":38,"repositoryHomepageUrl":6,"ownerHtmlUrl":39,"ownerBlogUrl":6,"ownerDescription":40,"updatedAt":41,"install":42,"resources":55},"01M7F0EB7MZ7JHSXP4D6MKFJ45","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.","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fgrok-delegate\u002FSKILL.md",[],[],"2026-11-16 10:05:34",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\nSend the brief to Grok with the bundled helper. It wraps `grok -p`, captures the run, and writes a\nstructured `result.json` — so your only job is \"run a command, read a file.\" (`\u003Cskill-dir>` below is\nthis skill's installed directory — the folder containing this `SKILL.md`, i.e. the directory you loaded\nthe skill from. Claude Code prints it as \"Base directory for this skill\" when the skill loads; on other\norchestrators use that same directory — if unsure where it landed, run\n`find ~ -name relay.mjs -path '*grok-delegate*'` and substitute the directory above it.)\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. Pairing it with `--sandbox workspace` is what keeps the default\nsafe. 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\nSend the brief to Grok with the bundled helper. It wraps `grok -p`, captures the run, and writes a\nstructured `result.json` — so your only job is \"run a command, read a file.\" (`\u003Cskill-dir>` below is\nthis skill's installed directory — the folder containing this `SKILL.md`, i.e. the directory you loaded\nthe skill from. Claude Code prints it as \"Base directory for this skill\" when the skill loads; on other\norchestrators use that same directory — if unsure where it landed, run\n`find ~ -name relay.mjs -path '*grok-delegate*'` and substitute the directory above it.)\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. Pairing it with `--sandbox workspace` is what keeps the default\nsafe. 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":25,"license":15,"category":26,"metadata":27,"date_added":29,"description":7,"source_repo":30,"source_type":31,"compatibility":32,"license_source":33},"critical","https:\u002F\u002Fgithub.com\u002FamElnagdy\u002Fdelegate-skills","agent-orchestration",{"version":28},"0.5.0","2026-08-26","amElnagdy\u002Fdelegate-skills","community","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","d69096e239f2a89aabc2cd078c47664a9d3b1e11","05-技能与代理开发\u002Fgrok-delegate",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":43,"prompt":53,"zipAvailable":54},[44,47,50],{"tool":45,"command":46},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill grok-delegate",{"tool":48,"command":49},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill grok-delegate",{"tool":51,"command":52},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill grok-delegate","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fgrok-delegate\u002FSKILL.md",true,[56,62,66,70],{"path":57,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":60,"sourceHtmlUrl":61},"references\u002Fdispatch-and-poll.md","REFERENCE","参考文档",10851,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fgrok-delegate\u002Freferences\u002Fdispatch-and-poll.md",{"path":63,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":64,"sourceHtmlUrl":65},"references\u002Fmulti-task-queues.md",3841,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fgrok-delegate\u002Freferences\u002Fmulti-task-queues.md",{"path":67,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":68,"sourceHtmlUrl":69},"references\u002Freview-and-land.md",8136,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fgrok-delegate\u002Freferences\u002Freview-and-land.md",{"path":71,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Fwriting-the-brief.md",5772,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fgrok-delegate\u002Freferences\u002Fwriting-the-brief.md",[75,82,87,94,101,108],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7FFG485KY83TD6HSC4YPCMC","obsidian-clipper-template-creator","Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator\u002FSKILL.md",[],[],{"skillNo":83,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M7FFFY0QEM14SKWPDYGMXM2P","python-api","Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP\u002FmAP semantics, and source-style import diagnostics.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Fpython-api\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":19},"01M7FFFVZQZ2GJ0C0TGP7JHD20","file-evaluation","Folder-based PASCAL VOC AP\u002FmAP evaluation from ground-truth and detection text files.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Ffile-evaluation\u002FSKILL.md",[],[],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":19},"01M7FFFSFNYSE77SJ6PE1CK2DA","object-detection-metrics","Guides legacy Object-Detection-Metrics PASCAL VOC AP\u002FmAP evaluation from detection text folders and direct Python API classes.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002FSKILL.md",[],[],{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":19},"01M7FFFP0GCK1RVXBCPQ8APBMT","nx-workspace-patterns","Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fnx-workspace-patterns\u002FSKILL.md",[],[]]