[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F31VC6MKTS2WM9KAVAKMJR":3,"skill-same:01M7F31VC6MKTS2WM9KAVAKMJR":56},{"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":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7F31VC6MKTS2WM9KAVAKMJR","pluginstaller",null,"Add a Codex plugin from a GitHub repo to a repo or personal marketplace using the current Codex plugin layout and marketplace metadata.","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-技能与代理开发\u002Fpluginstaller\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: pluginstaller\ndescription: Add a Codex plugin from a GitHub repo to a repo or personal marketplace using the current Codex plugin layout and marketplace metadata.\n---\n\n# Pluginstaller\n\nUse when the user gives a GitHub repo for a Codex plugin and wants it available in Codex.\n\nFollow the current Codex plugin docs. Do not invent alternate install flows.\n\n## Inputs\n\n- GitHub repo URL or `owner\u002Frepo`\n- Install scope: `repo` or `personal`\n- If the repo contains more than one plugin root, ask which plugin folder to install.\n\n## Workflow\n\n0. If the user does not specify whether the plugin should be repo-scoped or personal, stop and ask.\n1. Fetch the repo and locate the plugin root by finding `.codex-plugin\u002Fplugin.json`.\n2. Read `.codex-plugin\u002Fplugin.json` and validate the canonical structure:\n   - `name`, `version`, and `description` should exist.\n   - Bundled paths such as `skills`, `apps`, and `mcpServers` should be relative to the plugin root and start with `.\u002F`.\n   - Only `plugin.json` should live inside `.codex-plugin\u002F`.\n3. Prefer the built-in `@plugin-creator` skill when the task is to scaffold a new local plugin or add an existing local plugin to a marketplace. Use the manual path below when you are wiring up a repo the user already provided.\n4. Copy the entire plugin directory, not just `SKILL.md`, into a marketplace-visible location. Default to the documented standard locations unless the repo already uses a different valid marketplace-relative path:\n   - `repo`: `$CWD\u002Fplugins\u002F\u003Cplugin-name>` and `$CWD\u002F.agents\u002Fplugins\u002Fmarketplace.json`\n   - `personal`: `~\u002F.codex\u002Fplugins\u002F\u003Cplugin-name>` and `~\u002F.agents\u002Fplugins\u002Fmarketplace.json`\n5. Preserve the full bundle at the plugin root, including sibling `skills\u002F`, `.app.json`, `.mcp.json`, `assets\u002F`, and any other plugin files. Do not move those files under `.codex-plugin\u002F`.\n6. Create or update the marketplace file with the documented schema:\n   - top-level marketplace `name`\n   - optional `interface.displayName`\n   - plugin entry `name`\n   - `source.source = \"local\"`\n   - `source.path` relative to the marketplace root:\n     - `repo`: `.\u002Fplugins\u002F\u003Cplugin-name>`\n     - `personal`: `.\u002F.codex\u002Fplugins\u002F\u003Cplugin-name>`\n   - `policy.installation`\n   - `policy.authentication`\n   - `category`\n7. Use marketplace values that match the docs unless the user says otherwise:\n   - `policy.installation = \"AVAILABLE\"`\n   - `policy.authentication = \"ON_INSTALL\"`\n   - `category` from `interface.category` when present, otherwise `Productivity`\n8. Merge into any existing marketplace file instead of replacing it.\n9. Restart Codex and verify the plugin appears in `\u002Fplugins`.\n10. Report the runtime behavior accurately:\n   - The marketplace entry points to the source plugin directory.\n   - Codex installs the plugin into `~\u002F.codex\u002Fplugins\u002Fcache\u002F\u003Cmarketplace>\u002F\u003Cplugin>\u002F\u003Cversion>\u002F`.\n   - For local plugins, the installed cache version is `local`.\n   - Plugin enabled or disabled state is stored in `~\u002F.codex\u002Fconfig.toml`.\n\n## Rules\n\n- Prefer the terms `repo marketplace` and `personal marketplace` over `workspace` and `global`.\n- Do not present copying into `plugins\u002F` as the complete install. The marketplace entry is what makes the plugin discoverable in Codex.\n- Do not flatten or rename the plugin bundle.\n- Keep the plugin `name` stable and consistent across folder, manifest, and marketplace entry.\n- Keep manifest and marketplace paths relative and `.\u002F`-prefixed where the docs require it.\n- Treat the documented repo and personal plugin directories as defaults, not absolute requirements, as long as the marketplace `source.path` remains valid and stays inside the marketplace root.\n- If the repo already ships a marketplace file, prefer it as the source of truth for marketplace ordering and metadata, and only add or update the plugin entry that is needed.\n- If the manifest is missing required basics or uses invalid root-relative paths, fix the plugin structure before claiming installation is complete.\n\n## Scope guide\n\nUse `repo` when the plugin should live with one repo or be shared through that repo's marketplace. Use `personal` when the plugin should be available from the user's own Codex setup across projects.\n","# Pluginstaller\n\nUse when the user gives a GitHub repo for a Codex plugin and wants it available in Codex.\n\nFollow the current Codex plugin docs. Do not invent alternate install flows.\n\n## Inputs\n\n- GitHub repo URL or `owner\u002Frepo`\n- Install scope: `repo` or `personal`\n- If the repo contains more than one plugin root, ask which plugin folder to install.\n\n## Workflow\n\n0. If the user does not specify whether the plugin should be repo-scoped or personal, stop and ask.\n1. Fetch the repo and locate the plugin root by finding `.codex-plugin\u002Fplugin.json`.\n2. Read `.codex-plugin\u002Fplugin.json` and validate the canonical structure:\n   - `name`, `version`, and `description` should exist.\n   - Bundled paths such as `skills`, `apps`, and `mcpServers` should be relative to the plugin root and start with `.\u002F`.\n   - Only `plugin.json` should live inside `.codex-plugin\u002F`.\n3. Prefer the built-in `@plugin-creator` skill when the task is to scaffold a new local plugin or add an existing local plugin to a marketplace. Use the manual path below when you are wiring up a repo the user already provided.\n4. Copy the entire plugin directory, not just `SKILL.md`, into a marketplace-visible location. Default to the documented standard locations unless the repo already uses a different valid marketplace-relative path:\n   - `repo`: `$CWD\u002Fplugins\u002F\u003Cplugin-name>` and `$CWD\u002F.agents\u002Fplugins\u002Fmarketplace.json`\n   - `personal`: `~\u002F.codex\u002Fplugins\u002F\u003Cplugin-name>` and `~\u002F.agents\u002Fplugins\u002Fmarketplace.json`\n5. Preserve the full bundle at the plugin root, including sibling `skills\u002F`, `.app.json`, `.mcp.json`, `assets\u002F`, and any other plugin files. Do not move those files under `.codex-plugin\u002F`.\n6. Create or update the marketplace file with the documented schema:\n   - top-level marketplace `name`\n   - optional `interface.displayName`\n   - plugin entry `name`\n   - `source.source = \"local\"`\n   - `source.path` relative to the marketplace root:\n     - `repo`: `.\u002Fplugins\u002F\u003Cplugin-name>`\n     - `personal`: `.\u002F.codex\u002Fplugins\u002F\u003Cplugin-name>`\n   - `policy.installation`\n   - `policy.authentication`\n   - `category`\n7. Use marketplace values that match the docs unless the user says otherwise:\n   - `policy.installation = \"AVAILABLE\"`\n   - `policy.authentication = \"ON_INSTALL\"`\n   - `category` from `interface.category` when present, otherwise `Productivity`\n8. Merge into any existing marketplace file instead of replacing it.\n9. Restart Codex and verify the plugin appears in `\u002Fplugins`.\n10. Report the runtime behavior accurately:\n   - The marketplace entry points to the source plugin directory.\n   - Codex installs the plugin into `~\u002F.codex\u002Fplugins\u002Fcache\u002F\u003Cmarketplace>\u002F\u003Cplugin>\u002F\u003Cversion>\u002F`.\n   - For local plugins, the installed cache version is `local`.\n   - Plugin enabled or disabled state is stored in `~\u002F.codex\u002Fconfig.toml`.\n\n## Rules\n\n- Prefer the terms `repo marketplace` and `personal marketplace` over `workspace` and `global`.\n- Do not present copying into `plugins\u002F` as the complete install. The marketplace entry is what makes the plugin discoverable in Codex.\n- Do not flatten or rename the plugin bundle.\n- Keep the plugin `name` stable and consistent across folder, manifest, and marketplace entry.\n- Keep manifest and marketplace paths relative and `.\u002F`-prefixed where the docs require it.\n- Treat the documented repo and personal plugin directories as defaults, not absolute requirements, as long as the marketplace `source.path` remains valid and stays inside the marketplace root.\n- If the repo already ships a marketplace file, prefer it as the source of truth for marketplace ordering and metadata, and only add or update the plugin entry that is needed.\n- If the manifest is missing required basics or uses invalid root-relative paths, fix the plugin structure before claiming installation is complete.\n\n## Scope guide\n\nUse `repo` when the plugin should live with one repo or be shared through that repo's marketplace. Use `personal` when the plugin should be available from the user's own Codex setup across projects.\n",{"name":5,"description":7},"main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","05-技能与代理开发\u002Fpluginstaller",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":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill pluginstaller",{"tool":38,"command":39},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill pluginstaller",{"tool":41,"command":42},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill pluginstaller","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fpluginstaller\u002FSKILL.md",true,[46,52],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"agents\u002Fopenai.yaml","REFERENCE","参考文档",324,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fpluginstaller\u002Fagents\u002Fopenai.yaml",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Finstall-scope.md",1146,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fpluginstaller\u002Freferences\u002Finstall-scope.md",[57,64,69,76,83,90],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"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":65,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"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":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"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":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"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":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"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":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"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",[],[]]