[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78FEZ2R1M8K7Z5VYAS10260":3,"skill-same:01M78FEZ2R1M8K7Z5VYAS10260":47},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M78FEZ2R1M8K7Z5VYAS10260","integrate-agentgear",null,"This skill should be used when adding agentgear to a Rust binary that ships a Claude Code plugin, or migrating a hand-rolled install, self-heal, or per-harness config-merge engine onto its derive.","uwuclxdy\u002Fagentgear","uwuclxdy","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F37777261?v=4","01M78FES2PH9ZDP62KXN460J8R","cloudy","01M78FES3A93W91VPJ704RMFRG",2,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fuwuclxdy\u002Fagentgear\u002Fblob\u002Fmommy\u002Fskills\u002Fintegrate-agentgear\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: integrate-agentgear\ndescription: \"This skill should be used when adding agentgear to a Rust binary that ships a Claude Code plugin, or migrating a hand-rolled install, self-heal, or per-harness config-merge engine onto its derive.\"\nwhen_to_use: \"Use when a binary should install its own CC plugin, when a plugin needs to reach non-CC harnesses without hand-writing a translator per harness, or when deciding whether a given plugin is a fit.\"\n---\n\n# integrate-agentgear\n\nOne `#[derive(PluginHost)]` struct gives a host the full install \u002F uninstall \u002F update \u002F\nself-heal \u002F doctor lifecycle. agentgear drives the `claude plugin` CLI for those ops and bakes the\nplugin tree into the binary. It writes that one Claude-Code plugin into 23 other harnesses'\nnative config files, detect-gated, never clobbering user config (`copilot-cli` is a 25th target,\norchestrated through its own plugin CLI rather than a per-surface config translate). The host declares intent once;\nagentgear delivers it per harness.\n\nThis skill is the process. The exhaustive API lives in the repo's `wiki\u002F` pages (mapped at the end); cite them rather than restating them.\n\n## fit check (do this first)\n\nAnswer these before writing any code. A \"no\" changes the plan.\n\n1. **Does one binary both ship and install the plugin?** agentgear's embed model assumes the `PluginHost` binary IS the artifact that carries and installs the plugin tree. A plugin whose binary is a separate, independently-versioned artifact the plugin locates at runtime (say, one it finds on PATH) has no clean agentgear story yet.\n2. **The plugin's own binary distribution stays the host's job.** `Source` models where the\n   plugin *tree* comes from, never where the host's compiled binary comes from. Keep any\n   curl+checksum \u002F PATH-resolution \u002F version-GC installer the host already has; agentgear does not\n   replace it.\n3. **Which harnesses does it target?** A Claude-Code-only plugin needs only the default `claude`\n   backend, so the 24-harness translate does nothing for it. That is fine: the win there is the\n   automated lifecycle (setup \u002F self-heal \u002F doctor \u002F version-guard), not translation. Only name\n   extra `agents = [...]` when the plugin genuinely ships to those harnesses.\n4. **Does it hand-roll CC registry state directly?** Writing `known_marketplaces.json` or\n   `installed_plugins.json` by hand is the exact anti-pattern agentgear removes: the\n   CLI is the only supported writer. Migrating that is a correctness upgrade, not just a line cut.\n\n## greenfield: minimal setup\n\nThe smallest working host is Claude-only. Four things (shapes from `examples\u002Fhello-mcp`):\n\n- **`Cargo.toml`**: agentgear as both a normal and a build dependency. Default features\n  (`derive` + `claude` + `embed`) cover a Claude-only host:\n  ```toml\n  [dependencies]\n  agentgear = \"0.1\"\n  [build-dependencies]\n  agentgear = \"0.1\"\n  ```\n- **`build.rs`**: one line. It reads `plugin.json`, guards the version, and (with `embed`)\n  compresses the tree into the binary:\n  ```rust\n  fn main() { agentgear::build::assert_plugin_version(); }\n  ```\n  A missing `build.rs` is a compile error, not a silent loss (the derive checks for its marker).\n- **the derive struct**, in the lib (not just `main.rs`) so tests can read the metadata without\n  spawning the binary:\n  ```rust\n  use agentgear::PluginHost;\n  #[derive(PluginHost)]\n  #[plugin(name = \"my-plugin\")]\n  pub struct MyPlugin;\n  ```\n- **the `plugin\u002F` tree**, next to `Cargo.toml`. The only required file is\n  `plugin\u002F.claude-plugin\u002Fplugin.json`; its `name` must equal the derive's `name`, its `version`\n  must equal `CARGO_PKG_VERSION`, and `author` is required (it becomes the marketplace owner).\n\nThen wire the binary's own subcommands to the lifecycle methods (`setup` → `install`, `uninstall`, `doctor`, and for a fuller surface `update`, `self-heal`, `check-restart`). Point the plugin's `SessionStart` hook at `self_heal`, gated as `let session = agentgear::SessionSource::from_stdin(); if MyPlugin::heal_needed_report(session)?.needed() { MyPlugin::self_heal(session)?; }` (Claude Code pipes the SessionStart payload on stdin; read it once): the pre-check reads files and spawns no CLI, so a healthy `claude` install skips the heal's `claude` calls. Point `UserPromptSubmit` at `restart_pending()`.\n\nThe full attribute table, the six-subcommand `main.rs`, and the tree rules are in\n`wiki\u002FGetting-Started.md` and `wiki\u002FPlugin-Tree.md`. Do not restate them here; read them.\n\n## brownfield: migrating a hand-rolled installer\n\nAdopt the derive first (greenfield steps), get one green `setup` \u002F `doctor`, then delete the\nplumbing it replaces. Delete in this order, verifying after each:\n\n| hand-rolled thing | replaced by |\n|---|---|\n| marketplace-register + plugin-install code (shell or Rust), incl. any `known_marketplaces.json` write | `install(Scope::User, Source::Embedded)` |\n| direct `claude plugin ...` shell calls \u002F a custom CLI wrapper | agentgear's `ClaudeCli` (locate, env-scrub, non-interactive, tolerant `--json`); no host code shells out to `claude` |\n| a committed `marketplace.json` | generated into the versioned dir at materialize; never ship one |\n| a per-client config-merge engine (per-harness JSON\u002FTOML\u002FYAML writers, \"which client do I support\" descriptor files) | the built-in backends + `confedit`'s atomic read-modify-write; name harnesses in `agents = [...]` instead of writing translators |\n| a hand-rolled tree materialize \u002F diff-copy | agentgear's `materialize` (tree hashing, atomic versioned-dir flip) |\n| manual `SessionStart` self-heal logic | point the existing hook at `self_heal(session)`, gated on `heal_needed_report(session)?.needed()` — read the payload once into `session` (`let session = agentgear::SessionSource::from_stdin();`) |\n| a hand-maintained CC-version floor check | agentgear gates on `claude --version` before any mutating call |\n| a hand-written `statusLine` writer in `~\u002F.claude\u002Fsettings.json` (refuse\u002Fforce flags on a foreign value) | delete it; agentgear writes no status-line slot anymore — a host ships a `statusline` print subcommand and the user wires it manually |\n\nOne real migration deleted ~1,100 net lines (20 per-client descriptor files plus a parse-and-merge engine plus its tests), replaced by ~160 lines of CLI glue. That commit is the reference for scope.\n\nGrep the tree afterward for the deleted symbols and any surviving `Command::new(\"claude\")` \u002F\n`known_marketplaces` \u002F `marketplace.json` reference; a mechanical delete leaves stragglers.\n\n## multi-harness\n\n- `agents = [\"claude\", \"codex\", \"opencode\", ...]` on the derive sets the fan-out list every\n  lifecycle op walks. The 25 valid ids (closed list, unknown id = compile error) are: `claude`,\n  `codex`, `opencode`, `gemini`, `cursor`, `cline`, `devin`, `qwen-code`, `copilot-cli`,\n  `vscode-copilot`, `jetbrains-copilot`, `kimi`, `kiro`, `zed`, `omp`, `openclaw`, `kilo`,\n  `antigravity`, `antigravity-cli`, `pi`, `goose`, `amp`, `crush`, `droid`, `augment`.\n- **Each non-CC backend is a cargo feature named after its id** (dashes kept). List every backend\n  you name in `agents` under `features`, or use `all-agents`:\n  ```toml\n  agentgear = { version = \"0.1\", features = [\"codex\", \"opencode\", \"gemini\"] }\n  ```\n  A backend named in `agents` whose feature is off is a compile error in the host crate, with the\n  exact `features = [...]` fix in the message. `claude` is always on.\n- `install_into(scope, source, &[\"codex\"])` narrows a single run to a subset of `AGENTS` at\n  runtime (the `--agent \u003Cid>` pattern). `backend_for(id)` resolves one id to its backend for a\n  status\u002Fpicker view. `examples\u002Fmulti-installer` is the reference.\n- **`${AGENTGEAR_CLIENT}` expands to each harness's own id** (`claude`, `codex`, …) in a hook's\n  `command` and an MCP server's `command`\u002F`args`; `claude` and `copilot-cli` expand it across the\n  whole materialized tree. Migrate any baked-in `--client claude-code` to the token: the literal\n  rides through every backend unchanged and evaluates true on all of them, so a hook binary that\n  branches on its caller sees the wrong harness. Unlike `${CLAUDE_PLUGIN_ROOT}` (skipped, below),\n  this token is expanded, so a command carrying it stays portable.\n\nPer-harness fidelity (what each backend translates, what it skips and why) is in `wiki\u002FAgent-Backends.md`, `wiki\u002FHarness-Comparison.md` and the `wiki\u002FCapability-*.md` pages. Read them before promising a surface reaches a backend.\n\n## what does NOT migrate yet (gap blockers)\n\nCheck these against the target plugin before promising a full migration.\n\n- **statusLine is no longer written by agentgear at all; any settings key is unmodeled.** The\n  automatic slot wiring (declaration, five slot backends, stash-and-restore) is retired: a host\n  ships a `statusline` print subcommand and the user wires it manually. Any settings key outside\n  the plugin tree is unmodeled: the components IR\n  carries five surfaces (mcp servers, hooks, commands, agents, skills) and nothing else reaches a\n  harness's own settings file.\n- **codex `notify` hooks \u002F opencode hooks.** agentgear's codex backend writes `hooks.json`, which stays inert until the user trusts it via codex's `\u002Fhooks` TUI; opencode has no declarative hook surface at all (in-process JS\u002FTS plugin only). A plugin relying on either cannot fully migrate its hook path yet.\n- **`${CLAUDE_PLUGIN_ROOT}` in an mcp\u002Fhook command.** Every non-CC backend silently skips a\n  command carrying that token (it only expands inside CC). Use bare executable names so the surface\n  survives translation. Watch for the `cargo:warning` at build and doctor's \"no portable ... to\n  register\" line.\n\n## verify\n\n- `setup` then `doctor` on a scratch `HOME` install the plugin and report healthy; `uninstall`\n  strips exactly what was written.\n- The hand-rolled plumbing named in the migration table is gone (grep the deleted symbols).\n- A `plugin.json` \u002F `Cargo.toml` version mismatch fails the build (the guard, not a runtime error).\n- For a multi-harness host, install into a scratch profile for each named backend and confirm its\n  native config file carries the plugin, gated on `detect()`.\n- Hermetic-test discipline (env overrides to clear, why `claude`\u002F`copilot-cli` need an `#[ignore]`d\n  real-CLI run) is in `wiki\u002FTesting-Your-Host.md`.\n\n## reference map\n\n| need | read |\n|---|---|\n| every `#[plugin(...)]` attr, defaults, the tree rules | `wiki\u002FGetting-Started.md`, `wiki\u002FPlugin-Tree.md` |\n| lifecycle method signatures, `Scope`, `Source`, reports | `wiki\u002FTypes-and-Errors.md` |\n| which backend translates what, event maps, skips | `wiki\u002FAgent-Backends.md`, `wiki\u002FHarness-Comparison.md`, `wiki\u002FCapability-*.md` |\n| test harness rules | `wiki\u002FTesting-Your-Host.md` |\n","# integrate-agentgear\n\nOne `#[derive(PluginHost)]` struct gives a host the full install \u002F uninstall \u002F update \u002F\nself-heal \u002F doctor lifecycle. agentgear drives the `claude plugin` CLI for those ops and bakes the\nplugin tree into the binary. It writes that one Claude-Code plugin into 23 other harnesses'\nnative config files, detect-gated, never clobbering user config (`copilot-cli` is a 25th target,\norchestrated through its own plugin CLI rather than a per-surface config translate). The host declares intent once;\nagentgear delivers it per harness.\n\nThis skill is the process. The exhaustive API lives in the repo's `wiki\u002F` pages (mapped at the end); cite them rather than restating them.\n\n## fit check (do this first)\n\nAnswer these before writing any code. A \"no\" changes the plan.\n\n1. **Does one binary both ship and install the plugin?** agentgear's embed model assumes the `PluginHost` binary IS the artifact that carries and installs the plugin tree. A plugin whose binary is a separate, independently-versioned artifact the plugin locates at runtime (say, one it finds on PATH) has no clean agentgear story yet.\n2. **The plugin's own binary distribution stays the host's job.** `Source` models where the\n   plugin *tree* comes from, never where the host's compiled binary comes from. Keep any\n   curl+checksum \u002F PATH-resolution \u002F version-GC installer the host already has; agentgear does not\n   replace it.\n3. **Which harnesses does it target?** A Claude-Code-only plugin needs only the default `claude`\n   backend, so the 24-harness translate does nothing for it. That is fine: the win there is the\n   automated lifecycle (setup \u002F self-heal \u002F doctor \u002F version-guard), not translation. Only name\n   extra `agents = [...]` when the plugin genuinely ships to those harnesses.\n4. **Does it hand-roll CC registry state directly?** Writing `known_marketplaces.json` or\n   `installed_plugins.json` by hand is the exact anti-pattern agentgear removes: the\n   CLI is the only supported writer. Migrating that is a correctness upgrade, not just a line cut.\n\n## greenfield: minimal setup\n\nThe smallest working host is Claude-only. Four things (shapes from `examples\u002Fhello-mcp`):\n\n- **`Cargo.toml`**: agentgear as both a normal and a build dependency. Default features\n  (`derive` + `claude` + `embed`) cover a Claude-only host:\n  ```toml\n  [dependencies]\n  agentgear = \"0.1\"\n  [build-dependencies]\n  agentgear = \"0.1\"\n  ```\n- **`build.rs`**: one line. It reads `plugin.json`, guards the version, and (with `embed`)\n  compresses the tree into the binary:\n  ```rust\n  fn main() { agentgear::build::assert_plugin_version(); }\n  ```\n  A missing `build.rs` is a compile error, not a silent loss (the derive checks for its marker).\n- **the derive struct**, in the lib (not just `main.rs`) so tests can read the metadata without\n  spawning the binary:\n  ```rust\n  use agentgear::PluginHost;\n  #[derive(PluginHost)]\n  #[plugin(name = \"my-plugin\")]\n  pub struct MyPlugin;\n  ```\n- **the `plugin\u002F` tree**, next to `Cargo.toml`. The only required file is\n  `plugin\u002F.claude-plugin\u002Fplugin.json`; its `name` must equal the derive's `name`, its `version`\n  must equal `CARGO_PKG_VERSION`, and `author` is required (it becomes the marketplace owner).\n\nThen wire the binary's own subcommands to the lifecycle methods (`setup` → `install`, `uninstall`, `doctor`, and for a fuller surface `update`, `self-heal`, `check-restart`). Point the plugin's `SessionStart` hook at `self_heal`, gated as `let session = agentgear::SessionSource::from_stdin(); if MyPlugin::heal_needed_report(session)?.needed() { MyPlugin::self_heal(session)?; }` (Claude Code pipes the SessionStart payload on stdin; read it once): the pre-check reads files and spawns no CLI, so a healthy `claude` install skips the heal's `claude` calls. Point `UserPromptSubmit` at `restart_pending()`.\n\nThe full attribute table, the six-subcommand `main.rs`, and the tree rules are in\n`wiki\u002FGetting-Started.md` and `wiki\u002FPlugin-Tree.md`. Do not restate them here; read them.\n\n## brownfield: migrating a hand-rolled installer\n\nAdopt the derive first (greenfield steps), get one green `setup` \u002F `doctor`, then delete the\nplumbing it replaces. Delete in this order, verifying after each:\n\n| hand-rolled thing | replaced by |\n|---|---|\n| marketplace-register + plugin-install code (shell or Rust), incl. any `known_marketplaces.json` write | `install(Scope::User, Source::Embedded)` |\n| direct `claude plugin ...` shell calls \u002F a custom CLI wrapper | agentgear's `ClaudeCli` (locate, env-scrub, non-interactive, tolerant `--json`); no host code shells out to `claude` |\n| a committed `marketplace.json` | generated into the versioned dir at materialize; never ship one |\n| a per-client config-merge engine (per-harness JSON\u002FTOML\u002FYAML writers, \"which client do I support\" descriptor files) | the built-in backends + `confedit`'s atomic read-modify-write; name harnesses in `agents = [...]` instead of writing translators |\n| a hand-rolled tree materialize \u002F diff-copy | agentgear's `materialize` (tree hashing, atomic versioned-dir flip) |\n| manual `SessionStart` self-heal logic | point the existing hook at `self_heal(session)`, gated on `heal_needed_report(session)?.needed()` — read the payload once into `session` (`let session = agentgear::SessionSource::from_stdin();`) |\n| a hand-maintained CC-version floor check | agentgear gates on `claude --version` before any mutating call |\n| a hand-written `statusLine` writer in `~\u002F.claude\u002Fsettings.json` (refuse\u002Fforce flags on a foreign value) | delete it; agentgear writes no status-line slot anymore — a host ships a `statusline` print subcommand and the user wires it manually |\n\nOne real migration deleted ~1,100 net lines (20 per-client descriptor files plus a parse-and-merge engine plus its tests), replaced by ~160 lines of CLI glue. That commit is the reference for scope.\n\nGrep the tree afterward for the deleted symbols and any surviving `Command::new(\"claude\")` \u002F\n`known_marketplaces` \u002F `marketplace.json` reference; a mechanical delete leaves stragglers.\n\n## multi-harness\n\n- `agents = [\"claude\", \"codex\", \"opencode\", ...]` on the derive sets the fan-out list every\n  lifecycle op walks. The 25 valid ids (closed list, unknown id = compile error) are: `claude`,\n  `codex`, `opencode`, `gemini`, `cursor`, `cline`, `devin`, `qwen-code`, `copilot-cli`,\n  `vscode-copilot`, `jetbrains-copilot`, `kimi`, `kiro`, `zed`, `omp`, `openclaw`, `kilo`,\n  `antigravity`, `antigravity-cli`, `pi`, `goose`, `amp`, `crush`, `droid`, `augment`.\n- **Each non-CC backend is a cargo feature named after its id** (dashes kept). List every backend\n  you name in `agents` under `features`, or use `all-agents`:\n  ```toml\n  agentgear = { version = \"0.1\", features = [\"codex\", \"opencode\", \"gemini\"] }\n  ```\n  A backend named in `agents` whose feature is off is a compile error in the host crate, with the\n  exact `features = [...]` fix in the message. `claude` is always on.\n- `install_into(scope, source, &[\"codex\"])` narrows a single run to a subset of `AGENTS` at\n  runtime (the `--agent \u003Cid>` pattern). `backend_for(id)` resolves one id to its backend for a\n  status\u002Fpicker view. `examples\u002Fmulti-installer` is the reference.\n- **`${AGENTGEAR_CLIENT}` expands to each harness's own id** (`claude`, `codex`, …) in a hook's\n  `command` and an MCP server's `command`\u002F`args`; `claude` and `copilot-cli` expand it across the\n  whole materialized tree. Migrate any baked-in `--client claude-code` to the token: the literal\n  rides through every backend unchanged and evaluates true on all of them, so a hook binary that\n  branches on its caller sees the wrong harness. Unlike `${CLAUDE_PLUGIN_ROOT}` (skipped, below),\n  this token is expanded, so a command carrying it stays portable.\n\nPer-harness fidelity (what each backend translates, what it skips and why) is in `wiki\u002FAgent-Backends.md`, `wiki\u002FHarness-Comparison.md` and the `wiki\u002FCapability-*.md` pages. Read them before promising a surface reaches a backend.\n\n## what does NOT migrate yet (gap blockers)\n\nCheck these against the target plugin before promising a full migration.\n\n- **statusLine is no longer written by agentgear at all; any settings key is unmodeled.** The\n  automatic slot wiring (declaration, five slot backends, stash-and-restore) is retired: a host\n  ships a `statusline` print subcommand and the user wires it manually. Any settings key outside\n  the plugin tree is unmodeled: the components IR\n  carries five surfaces (mcp servers, hooks, commands, agents, skills) and nothing else reaches a\n  harness's own settings file.\n- **codex `notify` hooks \u002F opencode hooks.** agentgear's codex backend writes `hooks.json`, which stays inert until the user trusts it via codex's `\u002Fhooks` TUI; opencode has no declarative hook surface at all (in-process JS\u002FTS plugin only). A plugin relying on either cannot fully migrate its hook path yet.\n- **`${CLAUDE_PLUGIN_ROOT}` in an mcp\u002Fhook command.** Every non-CC backend silently skips a\n  command carrying that token (it only expands inside CC). Use bare executable names so the surface\n  survives translation. Watch for the `cargo:warning` at build and doctor's \"no portable ... to\n  register\" line.\n\n## verify\n\n- `setup` then `doctor` on a scratch `HOME` install the plugin and report healthy; `uninstall`\n  strips exactly what was written.\n- The hand-rolled plumbing named in the migration table is gone (grep the deleted symbols).\n- A `plugin.json` \u002F `Cargo.toml` version mismatch fails the build (the guard, not a runtime error).\n- For a multi-harness host, install into a scratch profile for each named backend and confirm its\n  native config file carries the plugin, gated on `detect()`.\n- Hermetic-test discipline (env overrides to clear, why `claude`\u002F`copilot-cli` need an `#[ignore]`d\n  real-CLI run) is in `wiki\u002FTesting-Your-Host.md`.\n\n## reference map\n\n| need | read |\n|---|---|\n| every `#[plugin(...)]` attr, defaults, the tree rules | `wiki\u002FGetting-Started.md`, `wiki\u002FPlugin-Tree.md` |\n| lifecycle method signatures, `Scope`, `Source`, reports | `wiki\u002FTypes-and-Errors.md` |\n| which backend translates what, event maps, skips | `wiki\u002FAgent-Backends.md`, `wiki\u002FHarness-Comparison.md`, `wiki\u002FCapability-*.md` |\n| test harness rules | `wiki\u002FTesting-Your-Host.md` |\n",{"name":5,"description":7,"when_to_use":24},"Use when a binary should install its own CC plugin, when a plugin needs to reach non-CC harnesses without hand-writing a translator per harness, or when deciding whether a given plugin is a fit.","mommy","e40710e581477ffe0956c9d2bdd7cbde58d4080c","skills\u002Fintegrate-agentgear",0,"https:\u002F\u002Fgithub.com\u002Fuwuclxdy\u002Fagentgear","https:\u002F\u002Fgithub.com\u002Fuwuclxdy","GLM? weird way to spell AGI 😹","2026-11-14 22:32:17",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add uwuclxdy\u002Fagentgear --skill integrate-agentgear",{"tool":39,"command":40},"bunx","bunx skills add uwuclxdy\u002Fagentgear --skill integrate-agentgear",{"tool":42,"command":43},"pnpm","pnpm dlx skills add uwuclxdy\u002Fagentgear --skill integrate-agentgear","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fuwuclxdy\u002Fagentgear\u002Fblob\u002Fmommy\u002Fskills\u002Fintegrate-agentgear\u002FSKILL.md",true,[],[48,55],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M78FEX4NCXJM36PQ7Z1BE0CQ","demo","Demonstration skill bundled with the kitchen-sink example plugin.","https:\u002F\u002Fgithub.com\u002Fuwuclxdy\u002Fagentgear\u002Fblob\u002Fmommy\u002Fexamples\u002Fkitchen-sink\u002Fplugin\u002Fskills\u002Fdemo\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M78FEV88S98BJNMN5CCM9TJG","ez-skill","fixture skill exercising the agentgear skills surface","https:\u002F\u002Fgithub.com\u002Fuwuclxdy\u002Fagentgear\u002Fblob\u002Fmommy\u002Fcrates\u002Fhost-fixture\u002Fplugin\u002Fskills\u002Fez-skill\u002FSKILL.md",[],[]]