[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M756TXPT39K2PQJH95SY4Q80":3,"skill-same:01M756TXPT39K2PQJH95SY4Q80":57},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M756TXPT39K2PQJH95SY4Q80","migrate-plugin",null,"Move a repository-root or sibling-workspace universal agent plugin into its npm package so the package distributes its manifest, vendor manifests, skills, and agents, and bundle the package's CLI with tsdown so it runs from an installed plugin directory with no node_modules. Use this skill when packaging an existing plugin for npm, relocating a top-level or plugins\u002F\u003Cname> plugin into a package, fixing a package that omits plugin assets, or making a plugin's bundled CLI self-contained, even if the user says only 'ship this plugin through npm', 'move the plugin into the package', or 'the CLI can't find its dependencies when installed as a plugin.'","cyberuni\u002Funiversal-plugin","cyberuni","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F65646890?v=4","01M756SKHC8BY8C4GQSZ9FTK9F","CyberUni","01M756SKJF0TPEBQ7YC0QVGZN6",1,"MIT","https:\u002F\u002Fgithub.com\u002Fcyberuni\u002Funiversal-plugin\u002Fblob\u002Fmain\u002Fpackages\u002Funiversal-plugin\u002Fskills\u002Fmigrate-plugin\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: migrate-plugin\ndescription: \"Move a repository-root or sibling-workspace universal agent plugin into its npm package so the package distributes its manifest, vendor manifests, skills, and agents, and bundle the package's CLI with tsdown so it runs from an installed plugin directory with no node_modules. Use this skill when packaging an existing plugin for npm, relocating a top-level or plugins\u002F\u003Cname> plugin into a package, fixing a package that omits plugin assets, or making a plugin's bundled CLI self-contained, even if the user says only 'ship this plugin through npm', 'move the plugin into the package', or 'the CLI can't find its dependencies when installed as a plugin.'\"\n---\n\n# Migrate Universal Plugin to npm\n\n## Scope\n\nMove one existing universal plugin into its owning npm package. The plugin may\nsit at the repository root or in its own workspace member such as\n`plugins\u002F\u003Cname>\u002F`. The package becomes the plugin root and must contain every\nruntime artifact it needs after installation — including a CLI that runs\nwithout `node_modules`.\n\nThis skill does not create a plugin from scratch, publish a package, or move\nproject-local agent configuration unrelated to the plugin.\n\n## 1. Inspect and plan\n\nIdentify the destination package directory and read its `package.json`.\nBefore changing manifest fields or component compatibility behavior, consult the\n[Agent Plugins Specification](https:\u002F\u002Fgithub.com\u002Fagentplugins\u002Fagent-plugins-spec)\nand its versioned specification: it is the canonical reference for the current\nstandard. Keep an existing schema version pinned unless the user explicitly\nrequests a standards upgrade.\nInventory these plugin assets in the source root when they exist:\n\n- `plugin.json`\n- vendor manifest directories for Claude Code, Cursor, Codex, and Copilot CLI\n- `.plugin\u002F` (for example a `pins.json` that skills read at runtime)\n- `skills\u002F`, `agents\u002F`, `commands\u002F`, `hooks\u002F`, `rules\u002F`, `output-styles\u002F`\n- `.mcp.json`, `.lsp.json`, and plugin-owned `assets\u002F`\n\nAlso inventory what exists only to host the plugin in its old place: a\nworkspace-member `package.json` (for example a private `@scope\u002F\u003Cname>-plugin`),\nand the `pnpm-workspace.yaml` or `workspaces` glob that includes it.\n\nLeave project configuration in place unless it is required solely to maintain\nthe moved plugin. In particular, do not move `.agents\u002Fskills\u002F`, plans, or a\nmarketplace catalog such as `.claude-plugin\u002Fmarketplace.json`.\n\nBefore modifying files, report the exact source-to-destination mapping and any\ndestination collisions. A `readme.md` on both sides is the usual one: merge the\nplugin readme into the package readme as its own section rather than\noverwriting either. Ask for confirmation if a destination contains a different\nfile that would be overwritten.\n\n## 2. Move the plugin root\n\nMove each inventoried asset under the package directory with `git mv`,\npreserving its relative path, so history follows the files:\n\n```text\nthe canonical manifest\nvendor manifests\n.plugin\u002F\nskills\nagents\n```\n\nThe source root must no longer retain duplicate distributable plugin assets.\nWhen the source was its own workspace member, delete its `package.json`, drop\nthe now-empty workspace glob, and reinstall so the lockfile loses the member.\nDo not move a project-local skill merely because it is under `.agents\u002Fskills\u002F`.\n\n## 3. Configure npm packaging\n\nAdd every moved plugin artifact to the destination package's `package.json`\n`files` allowlist. At minimum, include the canonical manifest, each present\nvendor manifest directory, and every present component directory. A typical\nconfiguration is:\n\n```json\n{\n  \"files\": [\n    \"bin\",\n    \"dist\",\n    \"plugin.json\",\n    \".claude-plugin\",\n    \".cursor-plugin\",\n    \".codex-plugin\",\n    \".plugin\",\n    \"skills\",\n    \"agents\"\n  ]\n}\n```\n\nRetain existing package entries such as `bin`, `dist`, and `references`.\nNever replace the allowlist wholesale.\n\n## 4. Bundle the CLI with tsdown\n\nAn installed agent plugin is a copy of a source checkout, not an npm install,\nso its directory has no reliable `node_modules`. A CLI whose build leaves\ndependencies external fails there. When the package ships a CLI, build it so\nevery runtime dependency is inlined into the CLI entry, while any library entry\nkeeps its dependencies external.\n\nSplit `tsdown.config.ts` into two configs that share an `outDir`:\n\n```ts\nimport { defineConfig } from 'tsdown'\n\n\u002F\u002F Two configs, because the entries want opposite dependency treatment. They share an\n\u002F\u002F `outDir`, which is safe: tsdown hoists `clean` and runs it once across every config\n\u002F\u002F before any build writes, so neither wipes the other.\nconst shared = {\n\toutDir: 'dist',\n\tformat: 'esm',\n\tplatform: 'node',\n\tclean: true,\n} as const\n\nexport default defineConfig([\n\t{\n\t\t\u002F\u002F Library entry. Dependencies stay EXTERNAL: their types surface in the public\n\t\t\u002F\u002F `.d.ts`, and a consumer that also uses them must share one copy.\n\t\t...shared,\n\t\tentry: { index: 'src\u002Findex.ts' },\n\t\tdts: true,\n\t},\n\t{\n\t\t\u002F\u002F CLI entry. Every runtime dependency is inlined so it runs with no node_modules.\n\t\t...shared,\n\t\tentry: { cli: 'src\u002Fcli.ts' },\n\t\tdts: false,\n\t\tdeps: {\n\t\t\talwaysBundle: [\u002F^commander(\\\u002F|$)\u002F, \u002F^some-dep(\\\u002F|$)\u002F],\n\t\t\tonlyBundle: false,\n\t\t},\n\t},\n])\n```\n\nRules for the CLI config:\n\n- **`alwaysBundle` lists exactly the package's own `dependencies`.** Those are\n  the only ones tsdown externalizes by default; their transitive dependencies\n  are inlined automatically. Use `^name(\\\u002F|$)` regexes so subpath imports\n  (`some-dep\u002Fworktree`) are caught too.\n- **Omit a dependency consumed only through `import type`.** TypeScript strips\n  it before bundling, and a package whose entry is raw `.ts` cannot be bundled.\n- **`onlyBundle: false`** silences the \"bundled a dependency\" warnings that are\n  the point of this config.\n- **Keep the existing output extensions.** If `bin` and `exports` already name\n  `.mjs`, leave tsdown's default; if they name `.js`, add\n  `outExtensions: () => ({ js: '.js' })` to `shared`. Never move published\n  paths as a side effect.\n- **Keep the entry's invocation contract.** When `bin` points straight at the\n  CLI output, `src\u002Fcli.ts` must keep its `#!\u002Fusr\u002Fbin\u002Fenv node` shebang (tsdown\n  preserves it and sets the execute bit). When `bin` is a wrapper that imports\n  the output and calls an exported function, leave the wrapper as is.\n- **Resolve runtime files relative to the output.** A CLI that reads\n  `..\u002Fpackage.json` through `import.meta.url` still works only if `src\u002F` and\n  `dist\u002F` sit at the same depth and `package.json` ships — confirm both.\n\nVerify the bundle, not just the build:\n\n1. `grep -En \"from ['\\\"](dep-a|dep-b)\" dist\u002Fcli.*` prints nothing, while the\n   library output still imports them.\n2. Pack into a scratch directory, extract, confirm the extracted `package\u002F` has\n   no `node_modules`, then run the CLI through its `bin` path: `--version` and\n   one read-only command. Do not run it from the workspace, where hoisted\n   `node_modules` hides a missing inline.\n\nSkills that invoke the CLI through `npx \u003Ccli>@\u003Cversion>` can then prefer the\nshipped CLI. That changes skill behavior and often a frozen spec, so offer it\nas a follow-up instead of doing it inside this migration.\n\n## 5. Preserve release synchronization\n\nPoint every version and build step at the new plugin root:\n\n- `universal-plugin plugin version --from-package --root \u003Cpkg>` reads `packagePath` from\n  `\u003Cpkg>\u002F.agents\u002Funiversal-plugin.json`, not from the manifest extension. With\n  no `packagePath` it reads `\u003Cpkg>\u002Fpackage.json`, so a package that holds its\n  own plugin needs no config file for it. If the repository instead runs its\n  own sync script, repoint that script's manifest path and leave it.\n- Change every `universal-plugin plugin build --root \u003Cold>` in `package.json`\n  scripts to the package directory, then run it and confirm it reports the\n  vendor manifests as built and the catalog as unchanged or refolded.\n- Repoint a local-directory `source` in the repository's marketplace catalog to\n  the package directory.\n\nUpdate any checked-in skill lockfile that records an absolute source path for a\nmoved skill. Do not modify unrelated agent configuration.\n\n## 6. Repoint tooling and prose\n\nSearch the repository for the old plugin path and update live references:\n\n- lint and format excludes for generated vendor manifests (for example\n  `biome.json` `files.includes` negations), knip workspaces, turbo filters\n- `AGENTS.md`, `CONTRIBUTING.md`, readmes, docs pages, and spec frontmatter\n  such as `project-path`\n- guards scoped to the package directory, such as a vocabulary or lint check —\n  confirm moved skills did not enter a scope that rejects their wording\n\nLeave historical records as written: changelogs, ADRs, research notes, and\ndecision or gate ledgers describe the layout at the time.\n\n## 7. Verify the result\n\n1. Run the repository's full verification (lint, build, typecheck, test).\n2. Run `npm pack --dry-run` from the destination package. Confirm it lists\n   `plugin.json`, every required vendor manifest, `.plugin\u002F` when present,\n   `skills\u002F`, `agents\u002F`, and the bundled CLI.\n3. Confirm step 4's no-`node_modules` run passed.\n4. Search the repository again for stale references to the old asset paths.\n5. Review the diff to confirm no project-local `.agents` content or marketplace\n   catalog was moved into the package.\n6. Add a changeset for the package when the repository uses changesets.\n\nCommit the move and the CLI bundling as separate commits: each is revertable on\nits own.\n\nReport the package path, files added to the npm tarball, checks run, and any\nintentionally retained root-local files.\n","# Migrate Universal Plugin to npm\n\n## Scope\n\nMove one existing universal plugin into its owning npm package. The plugin may\nsit at the repository root or in its own workspace member such as\n`plugins\u002F\u003Cname>\u002F`. The package becomes the plugin root and must contain every\nruntime artifact it needs after installation — including a CLI that runs\nwithout `node_modules`.\n\nThis skill does not create a plugin from scratch, publish a package, or move\nproject-local agent configuration unrelated to the plugin.\n\n## 1. Inspect and plan\n\nIdentify the destination package directory and read its `package.json`.\nBefore changing manifest fields or component compatibility behavior, consult the\n[Agent Plugins Specification](https:\u002F\u002Fgithub.com\u002Fagentplugins\u002Fagent-plugins-spec)\nand its versioned specification: it is the canonical reference for the current\nstandard. Keep an existing schema version pinned unless the user explicitly\nrequests a standards upgrade.\nInventory these plugin assets in the source root when they exist:\n\n- `plugin.json`\n- vendor manifest directories for Claude Code, Cursor, Codex, and Copilot CLI\n- `.plugin\u002F` (for example a `pins.json` that skills read at runtime)\n- `skills\u002F`, `agents\u002F`, `commands\u002F`, `hooks\u002F`, `rules\u002F`, `output-styles\u002F`\n- `.mcp.json`, `.lsp.json`, and plugin-owned `assets\u002F`\n\nAlso inventory what exists only to host the plugin in its old place: a\nworkspace-member `package.json` (for example a private `@scope\u002F\u003Cname>-plugin`),\nand the `pnpm-workspace.yaml` or `workspaces` glob that includes it.\n\nLeave project configuration in place unless it is required solely to maintain\nthe moved plugin. In particular, do not move `.agents\u002Fskills\u002F`, plans, or a\nmarketplace catalog such as `.claude-plugin\u002Fmarketplace.json`.\n\nBefore modifying files, report the exact source-to-destination mapping and any\ndestination collisions. A `readme.md` on both sides is the usual one: merge the\nplugin readme into the package readme as its own section rather than\noverwriting either. Ask for confirmation if a destination contains a different\nfile that would be overwritten.\n\n## 2. Move the plugin root\n\nMove each inventoried asset under the package directory with `git mv`,\npreserving its relative path, so history follows the files:\n\n```text\nthe canonical manifest\nvendor manifests\n.plugin\u002F\nskills\nagents\n```\n\nThe source root must no longer retain duplicate distributable plugin assets.\nWhen the source was its own workspace member, delete its `package.json`, drop\nthe now-empty workspace glob, and reinstall so the lockfile loses the member.\nDo not move a project-local skill merely because it is under `.agents\u002Fskills\u002F`.\n\n## 3. Configure npm packaging\n\nAdd every moved plugin artifact to the destination package's `package.json`\n`files` allowlist. At minimum, include the canonical manifest, each present\nvendor manifest directory, and every present component directory. A typical\nconfiguration is:\n\n```json\n{\n  \"files\": [\n    \"bin\",\n    \"dist\",\n    \"plugin.json\",\n    \".claude-plugin\",\n    \".cursor-plugin\",\n    \".codex-plugin\",\n    \".plugin\",\n    \"skills\",\n    \"agents\"\n  ]\n}\n```\n\nRetain existing package entries such as `bin`, `dist`, and `references`.\nNever replace the allowlist wholesale.\n\n## 4. Bundle the CLI with tsdown\n\nAn installed agent plugin is a copy of a source checkout, not an npm install,\nso its directory has no reliable `node_modules`. A CLI whose build leaves\ndependencies external fails there. When the package ships a CLI, build it so\nevery runtime dependency is inlined into the CLI entry, while any library entry\nkeeps its dependencies external.\n\nSplit `tsdown.config.ts` into two configs that share an `outDir`:\n\n```ts\nimport { defineConfig } from 'tsdown'\n\n\u002F\u002F Two configs, because the entries want opposite dependency treatment. They share an\n\u002F\u002F `outDir`, which is safe: tsdown hoists `clean` and runs it once across every config\n\u002F\u002F before any build writes, so neither wipes the other.\nconst shared = {\n\toutDir: 'dist',\n\tformat: 'esm',\n\tplatform: 'node',\n\tclean: true,\n} as const\n\nexport default defineConfig([\n\t{\n\t\t\u002F\u002F Library entry. Dependencies stay EXTERNAL: their types surface in the public\n\t\t\u002F\u002F `.d.ts`, and a consumer that also uses them must share one copy.\n\t\t...shared,\n\t\tentry: { index: 'src\u002Findex.ts' },\n\t\tdts: true,\n\t},\n\t{\n\t\t\u002F\u002F CLI entry. Every runtime dependency is inlined so it runs with no node_modules.\n\t\t...shared,\n\t\tentry: { cli: 'src\u002Fcli.ts' },\n\t\tdts: false,\n\t\tdeps: {\n\t\t\talwaysBundle: [\u002F^commander(\\\u002F|$)\u002F, \u002F^some-dep(\\\u002F|$)\u002F],\n\t\t\tonlyBundle: false,\n\t\t},\n\t},\n])\n```\n\nRules for the CLI config:\n\n- **`alwaysBundle` lists exactly the package's own `dependencies`.** Those are\n  the only ones tsdown externalizes by default; their transitive dependencies\n  are inlined automatically. Use `^name(\\\u002F|$)` regexes so subpath imports\n  (`some-dep\u002Fworktree`) are caught too.\n- **Omit a dependency consumed only through `import type`.** TypeScript strips\n  it before bundling, and a package whose entry is raw `.ts` cannot be bundled.\n- **`onlyBundle: false`** silences the \"bundled a dependency\" warnings that are\n  the point of this config.\n- **Keep the existing output extensions.** If `bin` and `exports` already name\n  `.mjs`, leave tsdown's default; if they name `.js`, add\n  `outExtensions: () => ({ js: '.js' })` to `shared`. Never move published\n  paths as a side effect.\n- **Keep the entry's invocation contract.** When `bin` points straight at the\n  CLI output, `src\u002Fcli.ts` must keep its `#!\u002Fusr\u002Fbin\u002Fenv node` shebang (tsdown\n  preserves it and sets the execute bit). When `bin` is a wrapper that imports\n  the output and calls an exported function, leave the wrapper as is.\n- **Resolve runtime files relative to the output.** A CLI that reads\n  `..\u002Fpackage.json` through `import.meta.url` still works only if `src\u002F` and\n  `dist\u002F` sit at the same depth and `package.json` ships — confirm both.\n\nVerify the bundle, not just the build:\n\n1. `grep -En \"from ['\\\"](dep-a|dep-b)\" dist\u002Fcli.*` prints nothing, while the\n   library output still imports them.\n2. Pack into a scratch directory, extract, confirm the extracted `package\u002F` has\n   no `node_modules`, then run the CLI through its `bin` path: `--version` and\n   one read-only command. Do not run it from the workspace, where hoisted\n   `node_modules` hides a missing inline.\n\nSkills that invoke the CLI through `npx \u003Ccli>@\u003Cversion>` can then prefer the\nshipped CLI. That changes skill behavior and often a frozen spec, so offer it\nas a follow-up instead of doing it inside this migration.\n\n## 5. Preserve release synchronization\n\nPoint every version and build step at the new plugin root:\n\n- `universal-plugin plugin version --from-package --root \u003Cpkg>` reads `packagePath` from\n  `\u003Cpkg>\u002F.agents\u002Funiversal-plugin.json`, not from the manifest extension. With\n  no `packagePath` it reads `\u003Cpkg>\u002Fpackage.json`, so a package that holds its\n  own plugin needs no config file for it. If the repository instead runs its\n  own sync script, repoint that script's manifest path and leave it.\n- Change every `universal-plugin plugin build --root \u003Cold>` in `package.json`\n  scripts to the package directory, then run it and confirm it reports the\n  vendor manifests as built and the catalog as unchanged or refolded.\n- Repoint a local-directory `source` in the repository's marketplace catalog to\n  the package directory.\n\nUpdate any checked-in skill lockfile that records an absolute source path for a\nmoved skill. Do not modify unrelated agent configuration.\n\n## 6. Repoint tooling and prose\n\nSearch the repository for the old plugin path and update live references:\n\n- lint and format excludes for generated vendor manifests (for example\n  `biome.json` `files.includes` negations), knip workspaces, turbo filters\n- `AGENTS.md`, `CONTRIBUTING.md`, readmes, docs pages, and spec frontmatter\n  such as `project-path`\n- guards scoped to the package directory, such as a vocabulary or lint check —\n  confirm moved skills did not enter a scope that rejects their wording\n\nLeave historical records as written: changelogs, ADRs, research notes, and\ndecision or gate ledgers describe the layout at the time.\n\n## 7. Verify the result\n\n1. Run the repository's full verification (lint, build, typecheck, test).\n2. Run `npm pack --dry-run` from the destination package. Confirm it lists\n   `plugin.json`, every required vendor manifest, `.plugin\u002F` when present,\n   `skills\u002F`, `agents\u002F`, and the bundled CLI.\n3. Confirm step 4's no-`node_modules` run passed.\n4. Search the repository again for stale references to the old asset paths.\n5. Review the diff to confirm no project-local `.agents` content or marketplace\n   catalog was moved into the package.\n6. Add a changeset for the package when the repository uses changesets.\n\nCommit the move and the CLI bundling as separate commits: each is revertable on\nits own.\n\nReport the package path, files added to the npm tarball, checks run, and any\nintentionally retained root-local files.\n",{"name":5,"description":7},"main","1abd213d96b54bf10606ffe06dd2896fdf3faf4b","packages\u002Funiversal-plugin\u002Fskills\u002Fmigrate-plugin",0,"https:\u002F\u002Fgithub.com\u002Fcyberuni\u002Funiversal-plugin","https:\u002F\u002Fcyberuni.github.io\u002Funiversal-plugin\u002F","https:\u002F\u002Fgithub.com\u002Fcyberuni","https:\u002F\u002Fwww.youtube.com\u002F@cyberuni","2026-11-14 20:29:04",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add cyberuni\u002Funiversal-plugin --skill migrate-plugin",{"tool":39,"command":40},"bunx","bunx skills add cyberuni\u002Funiversal-plugin --skill migrate-plugin",{"tool":42,"command":43},"pnpm","pnpm dlx skills add cyberuni\u002Funiversal-plugin --skill migrate-plugin","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fcyberuni\u002Funiversal-plugin\u002Fblob\u002Fmain\u002Fpackages\u002Funiversal-plugin\u002Fskills\u002Fmigrate-plugin\u002FSKILL.md",true,[47,53],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"evals\u002Fevals.json","REFERENCE","参考文档",1077,"https:\u002F\u002Fgithub.com\u002Fcyberuni\u002Funiversal-plugin\u002Fblob\u002Fmain\u002Fpackages\u002Funiversal-plugin\u002Fskills\u002Fmigrate-plugin\u002Fevals\u002Fevals.json",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"evals\u002Ftrigger-queries.json",1385,"https:\u002F\u002Fgithub.com\u002Fcyberuni\u002Funiversal-plugin\u002Fblob\u002Fmain\u002Fpackages\u002Funiversal-plugin\u002Fskills\u002Fmigrate-plugin\u002Fevals\u002Ftrigger-queries.json",[58,65,72,79,86,93],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M756VH3K76XSF636AV1E8WAM","upgrade-plugin","Use this skill when upgrading pinned `npx universal-plugin@\u003Cversion>` calls across a project to a newer version.","https:\u002F\u002Fgithub.com\u002Fcyberuni\u002Funiversal-plugin\u002Fblob\u002Fmain\u002Fpackages\u002Funiversal-plugin\u002Fskills\u002Fupgrade-plugin\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M756VB8VEBTV5M607P0R6ESG","remove-plugin","Use this skill to remove a universal agent plugin's artifacts — delete the generated vendor manifests for Claude Code, Cursor, or Codex, clear a stale or shadowing manifest left by an older build, or take the whole plugin out of a project. Trigger on \"delete the generated manifests\", \"remove the vendor manifests\", \"clean the plugin build output\", \"drop Codex support\", \"get rid of this plugin\", or \"stop shipping this plugin\".","https:\u002F\u002Fgithub.com\u002Fcyberuni\u002Funiversal-plugin\u002Fblob\u002Fmain\u002Fpackages\u002Funiversal-plugin\u002Fskills\u002Fremove-plugin\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M756TQ9GGV2ZX10VWKRJY38K","marketplace","Use this skill to run a repository's own plugin marketplace — generate the catalogs Claude Code, Codex, GitHub Copilot CLI, and Cursor read, list a plugin that lives elsewhere (an npm package, a GitHub repo, or `\u003Cplugin>@\u003Cmarketplace>`), change one listed entry in place, check every catalog against the schema its runtime loads, and write the README install section. Trigger on \"set up a local marketplace\", \"let users install this from my repo\", \"generate marketplace catalogs\", \"add a plugin to the marketplace\", \"list this npm package in my marketplace\", \"switch this entry to a url source\", \"bump the ref on this entry\", \"change the category of a marketplace entry\", \"make this repo installable\", \"add install instructions to the README\", or \"check my marketplace catalogs\".","https:\u002F\u002Fgithub.com\u002Fcyberuni\u002Funiversal-plugin\u002Fblob\u002Fmain\u002Fpackages\u002Funiversal-plugin\u002Fskills\u002Fmarketplace\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M756TKWBQAAYZ17DGRJK5RTJ","\u003Cskill-name>","Use this skill when \u003Ctrigger>. \u003COne-line summary.>","https:\u002F\u002Fgithub.com\u002Fcyberuni\u002Funiversal-plugin\u002Fblob\u002Fmain\u002Fpackages\u002Funiversal-plugin\u002Fskills\u002Finit-universal-plugin\u002Fassets\u002Ftemplates\u002Fskill.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M756SX1CMP0684KN2RTDVVG5","adopt-upx","Use this skill when the user wants to make their skills use upx — the fast local-first package runner shipped as @repobuddy\u002Fupx. Trigger on phrases like \"make my skills use upx\", \"adopt the upx runner\", \"speed up npx calls\", \"switch to upx\", or \"rewrite npx pins to upx\". Rewrites `npx \u003Cpkg>@\u003Cversion>` references to a caret range on `upx` (`^\u003Cmajor>`, or `^0.\u003Cminor>` for a 0.x pin) across one skill, a named set, or every skill in the project.","https:\u002F\u002Fgithub.com\u002Fcyberuni\u002Funiversal-plugin\u002Fblob\u002Fmain\u002Fpackages\u002Funiversal-plugin\u002Fskills\u002Fadopt-upx\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M756SSYSH9QK2WGD4RNXW9JG","subagent-driven-development","Use this skill when committing changes in this repository, even if the user does not explicitly mention the required pre-commit checks.","https:\u002F\u002Fgithub.com\u002Fcyberuni\u002Funiversal-plugin\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsubagent-driven-development\u002FSKILL.md",[],[]]