[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7E3G46CSRPG52SZX9YGNZCP":3,"skill-same:01M7E3G46CSRPG52SZX9YGNZCP":72},{"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":14,"repositoryHtmlUrl":37,"repositoryHomepageUrl":37,"ownerHtmlUrl":38,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":39,"install":40,"resources":53},"01M7E3G46CSRPG52SZX9YGNZCP","agy-delegate",null,"Delegate coding tasks to the Google Antigravity CLI (`agy`) only when the user explicitly requests it, while the orchestrator retains review and landing responsibility.","Mr-Nobody-Anonymous\u002FAll-skills","Mr-Nobody-Anonymous","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F184253119?v=4","01M7AEXFJHKTYQW5R0ZCQQTWFV","anonymous","01M7C00M3GQR4QKP9GZA42GFAK",0,"MIT","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fagent-orchestration\u002Fagy-delegate\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: agy-delegate\ndescription: Delegate coding tasks to the Google Antigravity CLI (`agy`) only when\n  the user explicitly requests it, while the orchestrator retains review and landing\n  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 `agy` CLI installed and authenticated, Node.js, and git.\n  The orchestrator must be able to run shell commands and read files. Shell examples\n  assume bash\u002Fzsh (macOS\u002FLinux, or Git Bash\u002FWSL on Windows).\nmetadata:\n  version: 0.5.0\n---\n# Antigravity Delegate\n\n## When to Use\n\n- You want to delegate a bounded coding task to a separate `agy` implementer (`Google Antigravity`) 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 Google Antigravity CLI (`agy`) - then review what it produced and land it\nyourself. You write the brief and own the judgment; Antigravity does the typing in its own\nconversation; you verify 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 any comparable agent can drive it. It is designed for and run on Claude\nCode; treat other orchestrators 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 `agy` CLI is not installed or not authenticated. Install it from Antigravity's CLI docs and run\n  the first-launch setup.\n- You want to write the code yourself, or you only need Antigravity's opinion on code you wrote (a\n  `--read-only` dispatch covers review without edits, but a plain review may not need delegation at all).\n\n## Prerequisites (check once)\n\n1. `agy help` succeeds. If not, install the Antigravity CLI and complete first-launch setup.\n2. `agy models` succeeds. That proves the CLI can authenticate and list the available model labels.\n3. You are in (or will point `--cd` at) the target git repository.\n\nThese checks do not prove that a headless write will be approved. In `--print` mode, Antigravity\ncannot prompt for a write permission and may auto-deny it. The relay detects that denial instead of\nreporting completion.\n\n## Choose the implementer model\n\n`agy` has a configured default model, so `--model` is optional. Use it when the human has a preferred\nAntigravity model label for the task. Otherwise let Antigravity use its own current default rather than\nguessing.\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\nAntigravity sees only the text you send plus what it can inspect in the workspace - no chat history, no\nshared context. Everything the task needs goes in the brief: the goal, the current state, what to\nchange, what to leave untouched, the project's **actual** gate commands, and a report contract. Tell\nAntigravity it will **not** commit (you will). Keep one task per brief. Full guidance and a template:\n[references\u002Fwriting-the-brief.md](references\u002Fwriting-the-brief.md).\n\n### 2. Dispatch\n\nSend the brief to Antigravity with the bundled helper. It wraps `agy --print`, captures the run, and\nwrites a structured `result.json` - so your only job is \"run a command, read a file.\" (`\u003Cskill-dir>`\nbelow is this skill's installed directory - the 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 label:                 add --model \"\u003Clabel from agy models>\"\n# reasoning effort (low, medium, high): add --effort high\n# read-only (plan mode — no edits):     add --read-only\n# enable Antigravity terminal sandbox:  add --sandbox\n# resume the most recent conversation:  add --resume-last  (delta brief only)\n# see all options:                      node ...\u002Frelay.mjs --help\n```\n\nThe helper starts a fresh Antigravity project by default and passes `--add-dir \u003Crepo>` (the `--cd`\npath, absolute) so `agy` has an explicit workspace. It does **not** pass `--dangerously-skip-permissions` by default.\nMechanics, flags, and the `result.json` shape: [references\u002Fdispatch-and-poll.md](references\u002Fdispatch-and-poll.md).\n\n### 3. Wait for completion\n\nThe helper blocks until Antigravity finishes, so back it with whatever your orchestrator offers and\nresume when 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.\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\nAntigravity's `result.json` includes its own final message and any gate claims. **Re-verify, don't\naccept:**\n\n- **Re-run the project's gates yourself** (the test\u002Flint\u002Fbuild commands from step 1).\n- **Read the diff** against the brief: did Antigravity do what was asked, nothing more and nothing less?\n  `touchedFiles` in the result is your starting point.\n- **Run the relevant guard skills** on the diff if you have them installed.\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\nThe implementer edits the working tree; **the orchestrator commits.** Only after the gates pass and the\ndiff holds:\n\n- Commit the verified work yourself, with a clear message.\n- If it needs changes, send a delta brief with `--resume-last` and review again.\n\n## Permission model\n\nAntigravity owns its own permission policy. The relay does not bypass it by default. Use\n`--dangerously-skip-permissions` only when the human explicitly accepts that Antigravity may\nauto-approve tool permission requests. `--read-only` runs `agy` in plan mode (`--mode plan`),\nremoving write and edit paths, and is mutually exclusive with `--dangerously-skip-permissions`.\nUse `--sandbox` when you want Antigravity's terminal sandbox enabled for the run.\nAntigravity's own help says `--dangerously-skip-permissions` auto-approves all tool permission\nrequests without prompting, including a request to act outside the sandbox. Do not treat\n`--sandbox` as an enforced boundary when the flags are combined; treat the run as full access.\nIf headless `--print` auto-denies a write, the relay reports `status: \"failed\"` and exits non-zero.\nThe relay fingerprints the working tree before and after a `--read-only` run to report\n`readOnlyViolation` in `result.json`. Settings allow-rules are not documented here as a fix\nbecause they have not been demonstrated to apply to this headless path. Do not add the bypass\nflag without explicit human approval.\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 on that mandate: **surface, don't\nabsorb** (report Antigravity's design decisions, defensible-but-unasked turns, and non-blocking\nnitpicks rather than silently keeping them) and **stop for scope changes** (if correct completion needs\ngoing beyond the brief, ask - don't expand the mandate yourself). The full treatment is in\n[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 Antigravity\n  can execute blind: structure, XML blocks, the report contract, and 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 `agy` 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","# Antigravity Delegate\n\n## When to Use\n\n- You want to delegate a bounded coding task to a separate `agy` implementer (`Google Antigravity`) 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 Google Antigravity CLI (`agy`) - then review what it produced and land it\nyourself. You write the brief and own the judgment; Antigravity does the typing in its own\nconversation; you verify 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 any comparable agent can drive it. It is designed for and run on Claude\nCode; treat other orchestrators 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 `agy` CLI is not installed or not authenticated. Install it from Antigravity's CLI docs and run\n  the first-launch setup.\n- You want to write the code yourself, or you only need Antigravity's opinion on code you wrote (a\n  `--read-only` dispatch covers review without edits, but a plain review may not need delegation at all).\n\n## Prerequisites (check once)\n\n1. `agy help` succeeds. If not, install the Antigravity CLI and complete first-launch setup.\n2. `agy models` succeeds. That proves the CLI can authenticate and list the available model labels.\n3. You are in (or will point `--cd` at) the target git repository.\n\nThese checks do not prove that a headless write will be approved. In `--print` mode, Antigravity\ncannot prompt for a write permission and may auto-deny it. The relay detects that denial instead of\nreporting completion.\n\n## Choose the implementer model\n\n`agy` has a configured default model, so `--model` is optional. Use it when the human has a preferred\nAntigravity model label for the task. Otherwise let Antigravity use its own current default rather than\nguessing.\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\nAntigravity sees only the text you send plus what it can inspect in the workspace - no chat history, no\nshared context. Everything the task needs goes in the brief: the goal, the current state, what to\nchange, what to leave untouched, the project's **actual** gate commands, and a report contract. Tell\nAntigravity it will **not** commit (you will). Keep one task per brief. Full guidance and a template:\n[references\u002Fwriting-the-brief.md](references\u002Fwriting-the-brief.md).\n\n### 2. Dispatch\n\nSend the brief to Antigravity with the bundled helper. It wraps `agy --print`, captures the run, and\nwrites a structured `result.json` - so your only job is \"run a command, read a file.\" (`\u003Cskill-dir>`\nbelow is this skill's installed directory - the 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 label:                 add --model \"\u003Clabel from agy models>\"\n# reasoning effort (low, medium, high): add --effort high\n# read-only (plan mode — no edits):     add --read-only\n# enable Antigravity terminal sandbox:  add --sandbox\n# resume the most recent conversation:  add --resume-last  (delta brief only)\n# see all options:                      node ...\u002Frelay.mjs --help\n```\n\nThe helper starts a fresh Antigravity project by default and passes `--add-dir \u003Crepo>` (the `--cd`\npath, absolute) so `agy` has an explicit workspace. It does **not** pass `--dangerously-skip-permissions` by default.\nMechanics, flags, and the `result.json` shape: [references\u002Fdispatch-and-poll.md](references\u002Fdispatch-and-poll.md).\n\n### 3. Wait for completion\n\nThe helper blocks until Antigravity finishes, so back it with whatever your orchestrator offers and\nresume when 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.\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\nAntigravity's `result.json` includes its own final message and any gate claims. **Re-verify, don't\naccept:**\n\n- **Re-run the project's gates yourself** (the test\u002Flint\u002Fbuild commands from step 1).\n- **Read the diff** against the brief: did Antigravity do what was asked, nothing more and nothing less?\n  `touchedFiles` in the result is your starting point.\n- **Run the relevant guard skills** on the diff if you have them installed.\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\nThe implementer edits the working tree; **the orchestrator commits.** Only after the gates pass and the\ndiff holds:\n\n- Commit the verified work yourself, with a clear message.\n- If it needs changes, send a delta brief with `--resume-last` and review again.\n\n## Permission model\n\nAntigravity owns its own permission policy. The relay does not bypass it by default. Use\n`--dangerously-skip-permissions` only when the human explicitly accepts that Antigravity may\nauto-approve tool permission requests. `--read-only` runs `agy` in plan mode (`--mode plan`),\nremoving write and edit paths, and is mutually exclusive with `--dangerously-skip-permissions`.\nUse `--sandbox` when you want Antigravity's terminal sandbox enabled for the run.\nAntigravity's own help says `--dangerously-skip-permissions` auto-approves all tool permission\nrequests without prompting, including a request to act outside the sandbox. Do not treat\n`--sandbox` as an enforced boundary when the flags are combined; treat the run as full access.\nIf headless `--print` auto-denies a write, the relay reports `status: \"failed\"` and exits non-zero.\nThe relay fingerprints the working tree before and after a `--read-only` run to report\n`readOnlyViolation` in `result.json`. Settings allow-rules are not documented here as a fix\nbecause they have not been demonstrated to apply to this headless path. Do not add the bypass\nflag without explicit human approval.\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 on that mandate: **surface, don't\nabsorb** (report Antigravity's design decisions, defensible-but-unasked turns, and non-blocking\nnitpicks rather than silently keeping them) and **stop for scope changes** (if correct completion needs\ngoing beyond the brief, ask - don't expand the mandate yourself). The full treatment is in\n[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 Antigravity\n  can execute blind: structure, XML blocks, the report contract, and 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 `agy` 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 `agy` CLI installed and authenticated, Node.js, and git. The orchestrator 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","2d1750717747097b602acf30bd09a7cbd4b4c6ea","awesome_skills\u002Fagent-orchestration\u002Fagy-delegate","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous","2026-11-09 11:45:36",{"source":8,"skillName":5,"commands":41,"prompt":51,"zipAvailable":52},[42,45,48],{"tool":43,"command":44},"npx","npx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill agy-delegate",{"tool":46,"command":47},"bunx","bunx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill agy-delegate",{"tool":49,"command":50},"pnpm","pnpm dlx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill agy-delegate","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fagent-orchestration\u002Fagy-delegate\u002FSKILL.md",true,[54,60,64,68],{"path":55,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":58,"sourceHtmlUrl":59},"references\u002Fdispatch-and-poll.md","REFERENCE","参考文档",9380,"https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fagent-orchestration\u002Fagy-delegate\u002Freferences\u002Fdispatch-and-poll.md",{"path":61,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":62,"sourceHtmlUrl":63},"references\u002Fmulti-task-queues.md",2960,"https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fagent-orchestration\u002Fagy-delegate\u002Freferences\u002Fmulti-task-queues.md",{"path":65,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":66,"sourceHtmlUrl":67},"references\u002Freview-and-land.md",5408,"https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fagent-orchestration\u002Fagy-delegate\u002Freferences\u002Freview-and-land.md",{"path":69,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":70,"sourceHtmlUrl":71},"references\u002Fwriting-the-brief.md",5460,"https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fagent-orchestration\u002Fagy-delegate\u002Freferences\u002Fwriting-the-brief.md",[73,81,88,95,102,109],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":80},"01M7FFFZPC2025JQQHPHDX154J","dei-assessment","Assess diversity, equity, and inclusion with metrics. TRIGGERS - Use when user needs help with dei-assessment related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-assessment\u002FSKILL.md",[],[],"2026-11-16 10:05:34",{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":80},"01M7FFFWN8H4WA7A6Y398QKB6J","dei-action-plan","Create DEI action plans with goals and initiatives. TRIGGERS - Use when user needs help with dei-action-plan related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-action-plan\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":80},"01M7FFFSHTM0QZRVZ2NRJTJ0PY","culture-fit-assessment","Design culture add assessment processes. TRIGGERS - Use when user needs help with culture-fit-assessment related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fculture-fit-assessment\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":80},"01M7FFFMA12RKEQA38KHJSXXPS","cowork-to-code-bridge","Use an already-installed, independently verified cowork-to-code bridge to run narrowly approved actions on the user's own macOS, Linux, or WSL2 machine through a local file queue.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcowork-to-code-bridge\u002FSKILL.md",[],[],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":80},"01M7FFFH1F6M8YRGW5V487GH1K","counter-offer-response","Draft counter-offer responses for retention. TRIGGERS - Use when user needs help with counter-offer-response related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcounter-offer-response\u002FSKILL.md",[],[],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":80},"01M7FFFDGEHV8Y7J9N40HZXW52","continuous-feedback-system","Design continuous feedback systems. TRIGGERS - Use when user needs help with continuous-feedback-system related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcontinuous-feedback-system\u002FSKILL.md",[],[]]