[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71BYTKQFMS80HSAG4TXGKSC":3,"skill-same:01M71BYTKQFMS80HSAG4TXGKSC":96},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":6,"ownerHtmlUrl":49,"ownerBlogUrl":6,"ownerDescription":50,"updatedAt":51,"install":52,"resources":65},"01M71BYTKQFMS80HSAG4TXGKSC","plugin-creator",null,"Create and scaffold plugin directories for Codex with a required `.codex-plugin\u002Fplugin.json`, optional plugin folders\u002Ffiles, valid manifest defaults, and personal-marketplace entries by default. Use when Codex needs to create a new personal plugin, add optional plugin structure, generate or update marketplace entries for plugin ordering and availability metadata, or update an existing local plugin during development with the CLI-driven cachebuster and reinstall flow.","nexuslinkproductions\u002Fyuri-os","nexuslinkproductions","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F273246263?v=4","01M718YX9NZRCW50B59B8ZVDKN","Marcel Spatz","01M718YXAQ7530F4B1VKN6SFQV",2,"MIT","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002F.system\u002Fplugin-creator\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"plugin creator","creator","plugin","create","with","valid","manifest","when","Existing","use","files","new","local","entries","scaffold plugin","default","for","development","directories","availability","2026-11-10 10:12:30",false,"---\nname: plugin-creator\ndescription: Create and scaffold plugin directories for Codex with a required `.codex-plugin\u002Fplugin.json`, optional plugin folders\u002Ffiles, valid manifest defaults, and personal-marketplace entries by default. Use when Codex needs to create a new personal plugin, add optional plugin structure, generate or update marketplace entries for plugin ordering and availability metadata, or update an existing local plugin during development with the CLI-driven cachebuster and reinstall flow.\n---\n\n# Plugin Creator\n\n## Quick Start\n\n1. Run the scaffold script:\n\n```bash\n# Plugin names are normalized to lower-case hyphen-case and must be \u003C= 64 chars.\n# The generated folder and plugin.json name are always the same.\n# Run from the skill root (the directory containing this `SKILL.md`).\n# By default creates in `~\u002Fplugins\u002F\u003Cplugin-name>`.\npython3 scripts\u002Fcreate_basic_plugin.py \u003Cplugin-name>\n```\n\n2. Edit `\u003Cplugin-path>\u002F.codex-plugin\u002Fplugin.json` when the request gives specific metadata.\n   The scaffold starts with valid defaults and must not contain `[TODO: ...]` placeholders.\n\n3. Generate or update the personal marketplace entry when the plugin should appear in Codex UI ordering:\n\n```bash\n# Personal marketplace entries default to `~\u002F.agents\u002Fplugins\u002Fmarketplace.json`.\npython3 scripts\u002Fcreate_basic_plugin.py my-plugin --with-marketplace\n```\n\nOnly specify `--marketplace-name \u003Cname>` when the default `personal` marketplace name is already\ntaken or installed and you need to seed a different new marketplace file:\n\n```bash\npython3 scripts\u002Fcreate_basic_plugin.py my-plugin \\\n  --with-marketplace \\\n  --marketplace-name team-local\n```\n\nOnly use a repo\u002Fteam marketplace when the user specifically asks for that destination:\n\n```bash\npython3 scripts\u002Fcreate_basic_plugin.py my-plugin \\\n  --path \u003Crepo-root>\u002Fplugins \\\n  --marketplace-path \u003Crepo-root>\u002F.agents\u002Fplugins\u002Fmarketplace.json \\\n  --with-marketplace\n```\n\nWhen the user specifies a marketplace path, make sure that marketplace is actually installed before\ntelling the user to reinstall from it. The default personal marketplace file at\n`~\u002F.agents\u002Fplugins\u002Fmarketplace.json` is discovered implicitly, but other marketplace paths are not.\nOn Windows, use the equivalent path under the user profile.\n\n4. Generate\u002Fadjust optional companion folders as needed:\n\n```bash\npython3 scripts\u002Fcreate_basic_plugin.py my-plugin \\\n  --path \u003Cparent-plugin-directory> \\\n  --marketplace-path \u003Cmarketplace-json-path> \\\n  --with-skills --with-hooks --with-scripts --with-assets --with-mcp --with-apps --with-marketplace\n```\n\n`\u003Cparent-plugin-directory>` is the directory where the plugin folder `\u003Cplugin-name>` will be\ncreated (for example `~\u002Fplugins`).\n\n5. Before handing back a generated plugin, run:\n\n```bash\npython3 scripts\u002Fvalidate_plugin.py \u003Cplugin-path>\n```\n\nFor updates to an existing local plugin during development, keep the scaffold flow as-is and use the\nreference instead of hand-editing marketplace files:\n\n```bash\npython3 scripts\u002Fupdate_plugin_cachebuster.py \u003Cplugin-path>\n```\n\nPrefer the helper default cachebuster unless the user explicitly asks for a specific override.\nSee `references\u002Finstalling-and-updating.md` for the expected cachebuster and reinstall flow while iterating on an existing local plugin.\n\n## What this skill creates\n\n- Default marketplace-backed scaffolds use the personal marketplace file at\n  `~\u002F.agents\u002Fplugins\u002Fmarketplace.json`, with plugins generally being stored in\n  `~\u002Fplugins\u002F\u003Cplugin-name>\u002F`.\n- Creates plugin root at `\u002F\u003Cparent-plugin-directory>\u002F\u003Cplugin-name>\u002F`.\n- Always creates `\u002F\u003Cparent-plugin-directory>\u002F\u003Cplugin-name>\u002F.codex-plugin\u002Fplugin.json`.\n- Fills the manifest with the validated schema shape that the ingestion path accepts.\n- Creates or updates `~\u002F.agents\u002Fplugins\u002Fmarketplace.json` when `--with-marketplace` is set.\n  - If the marketplace file does not exist yet, seed a personal marketplace root before adding the first plugin entry.\n- `\u003Cplugin-name>` is normalized using skill-creator naming rules:\n  - `My Plugin` → `my-plugin`\n  - `My--Plugin` → `my-plugin`\n  - underscores, spaces, and punctuation are converted to `-`\n  - result is lower-case hyphen-delimited with consecutive hyphens collapsed\n- Supports optional creation of:\n  - `skills\u002F`\n  - `hooks\u002F`\n  - `scripts\u002F`\n  - `assets\u002F`\n  - `.mcp.json`\n  - `.app.json`\n\n## Marketplace workflow\n\n- Personal-marketplace creation defaults to `~\u002F.agents\u002Fplugins\u002Fmarketplace.json`. Here,\n  \"personal marketplace\" means the marketplace whose file is at that path.\n- Repo\u002Fteam marketplace creation is opt-in through both `--path` and `--marketplace-path`, only\n  when the user specifically requests it.\n- `--marketplace-name` is an exception path. Use it only when the default `personal` marketplace\n  name is already taken and you need to seed a different new marketplace file.\n- Do not use `--marketplace-name` to rename an existing marketplace file in place. If the file\n  already exists, its top-level `name` must already match.\n- If the user specifies a different marketplace path, treat that marketplace as needing explicit installation via `codex plugin marketplace add`.\n- Prefer `scripts\u002Fread_marketplace_name.py` when you need the marketplace name from any\n  `marketplace.json` file. With no argument it reads the default personal marketplace; with an\n  explicit path it works for repo\u002Fteam marketplaces too.\n- In either location, the generated source path remains `.\u002Fplugins\u002F\u003Cplugin-name>`.\n- Marketplace root metadata supports top-level `name` plus optional `interface.displayName`.\n- Treat plugin order in `plugins[]` as render order in Codex. Append new entries unless a user explicitly asks to reorder the list.\n- `displayName` belongs inside the marketplace `interface` object, not individual `plugins[]` entries.\n- Each generated marketplace entry must include all of:\n  - `policy.installation`\n  - `policy.authentication`\n  - `category`\n- Default new entries to:\n  - `policy.installation: \"AVAILABLE\"`\n  - `policy.authentication: \"ON_INSTALL\"`\n- Override defaults only when the user explicitly specifies another allowed value.\n- Allowed `policy.installation` values:\n  - `NOT_AVAILABLE`\n  - `AVAILABLE`\n  - `INSTALLED_BY_DEFAULT`\n- Allowed `policy.authentication` values:\n  - `ON_INSTALL`\n  - `ON_USE`\n- Treat `policy.products` as an override. Omit it unless the user explicitly requests product gating.\n- The generated plugin entry shape is:\n\n```json\n{\n  \"name\": \"plugin-name\",\n  \"source\": {\n    \"source\": \"local\",\n    \"path\": \".\u002Fplugins\u002Fplugin-name\"\n  },\n  \"policy\": {\n    \"installation\": \"AVAILABLE\",\n    \"authentication\": \"ON_INSTALL\"\n  },\n  \"category\": \"Productivity\"\n}\n```\n\n- Use `--force` only when intentionally replacing an existing marketplace entry for the same plugin name.\n- If the target marketplace file does not exist yet, create it with top-level `\"name\"`, an `\"interface\"` object containing `\"displayName\"`, and a `plugins` array, then add the new entry.\n\n- For a brand-new marketplace file, the root object should look like:\n\n```json\n{\n  \"name\": \"personal\",\n  \"interface\": {\n    \"displayName\": \"Personal\"\n  },\n  \"plugins\": [\n    {\n      \"name\": \"plugin-name\",\n      \"source\": {\n        \"source\": \"local\",\n        \"path\": \".\u002Fplugins\u002Fplugin-name\"\n      },\n      \"policy\": {\n        \"installation\": \"AVAILABLE\",\n        \"authentication\": \"ON_INSTALL\"\n      },\n      \"category\": \"Productivity\"\n    }\n  ]\n}\n```\n\n## Required behavior\n\n- Outer folder name and `plugin.json` `\"name\"` are always the same normalized plugin name.\n- Do not remove required structure; keep `.codex-plugin\u002Fplugin.json` present.\n- Do not leave `[TODO: ...]` placeholders in plugin manifests.\n- Keep `apps` and `mcpServers` out of `plugin.json` unless their companion files are actually created.\n- Omit unsupported plugin manifest fields that validation rejects, including `hooks`.\n- If creating files inside an existing plugin path, use `--force` only when overwrite is intentional.\n- Preserve any existing marketplace `interface.displayName`.\n- When generating marketplace entries, always write `policy.installation`, `policy.authentication`, and `category` even if their values are defaults.\n- Add `policy.products` only when the user explicitly asks for that override.\n- Keep marketplace `source.path` relative to the selected marketplace root as `.\u002Fplugins\u002F\u003Cplugin-name>`.\n- Only use `--marketplace-name` when creating a new marketplace file whose name should not be\n  `personal` because that name is already taken or installed elsewhere.\n- If Codex would need approval to write the marketplace file, ask for that approval before\n  proceeding. If the user prefers to run the write themselves, provide the exact scaffold command\n  and then continue from validation or subsequent plugin edits instead of leaving the workflow\n  vague.\n- For updates to an existing local plugin during development, do not hand-edit marketplace config\n  or `marketplace.json`. Use the update flow documented in\n  `references\u002Finstalling-and-updating.md` and `scripts\u002Fupdate_plugin_cachebuster.py`.\n- Do not tell the user to run `codex plugin marketplace add` for the default personal-marketplace\n  flow. That command is for explicit non-default marketplace configuration, not for the standard\n  `~\u002F.agents\u002Fplugins\u002Fmarketplace.json` path.\n- If the user provided a non-default `--marketplace-path`, make sure that marketplace is installed\n  before giving reinstall instructions. Use `codex plugin marketplace add \u003Cpath-to-marketplace-root>`\n  when that explicit marketplace has not been configured yet.\n- When the workflow created or updated a marketplace-backed plugin, end the final user-facing\n  response with a short Codex app handoff. Say `To view this in the Codex app:` and write\n  `View \u003Cnormalized plugin name>` and `Share \u003Cnormalized plugin name>` as Markdown links, not raw\n  URLs or code spans.\n- The View deeplink uses `codex:\u002F\u002Fplugins\u002F\u003Cnormalized plugin name>?marketplacePath=\u003Cabsolute marketplace.json path>`.\n  The Share deeplink uses the same URL with `&mode=share`.\n- Replace the placeholders with the real normalized plugin name and absolute `marketplace.json`\n  path from the scaffolded plugin. URL-encode the path segment and query value when needed.\n- Do not add `pluginName` or `hostId` query parameters to these deeplinks. Codex derives both after\n  the user clicks the link.\n- Do not emit the `View \u003Cnormalized plugin name>` or `Share \u003Cnormalized plugin name>` links when no marketplace entry was\n  created or updated.\n\n## Reference to exact spec sample\n\nFor the exact canonical sample JSON for both plugin manifests and marketplace entries, use:\n\n- `references\u002Fplugin-json-spec.md`\n- `references\u002Finstalling-and-updating.md` for update\u002Freinstall guidance while\n  iterating on an existing local plugin, plus the new-thread pickup behavior after reinstall\n\n## Validation\n\nAfter editing `SKILL.md`, run:\n\n```bash\npython3 ..\u002Fskill-creator\u002Fscripts\u002Fquick_validate.py .\n```\n\nBefore handing back a generated plugin, run:\n\n```bash\npython3 scripts\u002Fvalidate_plugin.py \u003Cplugin-path>\n```\n","# Plugin Creator\n\n## Quick Start\n\n1. Run the scaffold script:\n\n```bash\n# Plugin names are normalized to lower-case hyphen-case and must be \u003C= 64 chars.\n# The generated folder and plugin.json name are always the same.\n# Run from the skill root (the directory containing this `SKILL.md`).\n# By default creates in `~\u002Fplugins\u002F\u003Cplugin-name>`.\npython3 scripts\u002Fcreate_basic_plugin.py \u003Cplugin-name>\n```\n\n2. Edit `\u003Cplugin-path>\u002F.codex-plugin\u002Fplugin.json` when the request gives specific metadata.\n   The scaffold starts with valid defaults and must not contain `[TODO: ...]` placeholders.\n\n3. Generate or update the personal marketplace entry when the plugin should appear in Codex UI ordering:\n\n```bash\n# Personal marketplace entries default to `~\u002F.agents\u002Fplugins\u002Fmarketplace.json`.\npython3 scripts\u002Fcreate_basic_plugin.py my-plugin --with-marketplace\n```\n\nOnly specify `--marketplace-name \u003Cname>` when the default `personal` marketplace name is already\ntaken or installed and you need to seed a different new marketplace file:\n\n```bash\npython3 scripts\u002Fcreate_basic_plugin.py my-plugin \\\n  --with-marketplace \\\n  --marketplace-name team-local\n```\n\nOnly use a repo\u002Fteam marketplace when the user specifically asks for that destination:\n\n```bash\npython3 scripts\u002Fcreate_basic_plugin.py my-plugin \\\n  --path \u003Crepo-root>\u002Fplugins \\\n  --marketplace-path \u003Crepo-root>\u002F.agents\u002Fplugins\u002Fmarketplace.json \\\n  --with-marketplace\n```\n\nWhen the user specifies a marketplace path, make sure that marketplace is actually installed before\ntelling the user to reinstall from it. The default personal marketplace file at\n`~\u002F.agents\u002Fplugins\u002Fmarketplace.json` is discovered implicitly, but other marketplace paths are not.\nOn Windows, use the equivalent path under the user profile.\n\n4. Generate\u002Fadjust optional companion folders as needed:\n\n```bash\npython3 scripts\u002Fcreate_basic_plugin.py my-plugin \\\n  --path \u003Cparent-plugin-directory> \\\n  --marketplace-path \u003Cmarketplace-json-path> \\\n  --with-skills --with-hooks --with-scripts --with-assets --with-mcp --with-apps --with-marketplace\n```\n\n`\u003Cparent-plugin-directory>` is the directory where the plugin folder `\u003Cplugin-name>` will be\ncreated (for example `~\u002Fplugins`).\n\n5. Before handing back a generated plugin, run:\n\n```bash\npython3 scripts\u002Fvalidate_plugin.py \u003Cplugin-path>\n```\n\nFor updates to an existing local plugin during development, keep the scaffold flow as-is and use the\nreference instead of hand-editing marketplace files:\n\n```bash\npython3 scripts\u002Fupdate_plugin_cachebuster.py \u003Cplugin-path>\n```\n\nPrefer the helper default cachebuster unless the user explicitly asks for a specific override.\nSee `references\u002Finstalling-and-updating.md` for the expected cachebuster and reinstall flow while iterating on an existing local plugin.\n\n## What this skill creates\n\n- Default marketplace-backed scaffolds use the personal marketplace file at\n  `~\u002F.agents\u002Fplugins\u002Fmarketplace.json`, with plugins generally being stored in\n  `~\u002Fplugins\u002F\u003Cplugin-name>\u002F`.\n- Creates plugin root at `\u002F\u003Cparent-plugin-directory>\u002F\u003Cplugin-name>\u002F`.\n- Always creates `\u002F\u003Cparent-plugin-directory>\u002F\u003Cplugin-name>\u002F.codex-plugin\u002Fplugin.json`.\n- Fills the manifest with the validated schema shape that the ingestion path accepts.\n- Creates or updates `~\u002F.agents\u002Fplugins\u002Fmarketplace.json` when `--with-marketplace` is set.\n  - If the marketplace file does not exist yet, seed a personal marketplace root before adding the first plugin entry.\n- `\u003Cplugin-name>` is normalized using skill-creator naming rules:\n  - `My Plugin` → `my-plugin`\n  - `My--Plugin` → `my-plugin`\n  - underscores, spaces, and punctuation are converted to `-`\n  - result is lower-case hyphen-delimited with consecutive hyphens collapsed\n- Supports optional creation of:\n  - `skills\u002F`\n  - `hooks\u002F`\n  - `scripts\u002F`\n  - `assets\u002F`\n  - `.mcp.json`\n  - `.app.json`\n\n## Marketplace workflow\n\n- Personal-marketplace creation defaults to `~\u002F.agents\u002Fplugins\u002Fmarketplace.json`. Here,\n  \"personal marketplace\" means the marketplace whose file is at that path.\n- Repo\u002Fteam marketplace creation is opt-in through both `--path` and `--marketplace-path`, only\n  when the user specifically requests it.\n- `--marketplace-name` is an exception path. Use it only when the default `personal` marketplace\n  name is already taken and you need to seed a different new marketplace file.\n- Do not use `--marketplace-name` to rename an existing marketplace file in place. If the file\n  already exists, its top-level `name` must already match.\n- If the user specifies a different marketplace path, treat that marketplace as needing explicit installation via `codex plugin marketplace add`.\n- Prefer `scripts\u002Fread_marketplace_name.py` when you need the marketplace name from any\n  `marketplace.json` file. With no argument it reads the default personal marketplace; with an\n  explicit path it works for repo\u002Fteam marketplaces too.\n- In either location, the generated source path remains `.\u002Fplugins\u002F\u003Cplugin-name>`.\n- Marketplace root metadata supports top-level `name` plus optional `interface.displayName`.\n- Treat plugin order in `plugins[]` as render order in Codex. Append new entries unless a user explicitly asks to reorder the list.\n- `displayName` belongs inside the marketplace `interface` object, not individual `plugins[]` entries.\n- Each generated marketplace entry must include all of:\n  - `policy.installation`\n  - `policy.authentication`\n  - `category`\n- Default new entries to:\n  - `policy.installation: \"AVAILABLE\"`\n  - `policy.authentication: \"ON_INSTALL\"`\n- Override defaults only when the user explicitly specifies another allowed value.\n- Allowed `policy.installation` values:\n  - `NOT_AVAILABLE`\n  - `AVAILABLE`\n  - `INSTALLED_BY_DEFAULT`\n- Allowed `policy.authentication` values:\n  - `ON_INSTALL`\n  - `ON_USE`\n- Treat `policy.products` as an override. Omit it unless the user explicitly requests product gating.\n- The generated plugin entry shape is:\n\n```json\n{\n  \"name\": \"plugin-name\",\n  \"source\": {\n    \"source\": \"local\",\n    \"path\": \".\u002Fplugins\u002Fplugin-name\"\n  },\n  \"policy\": {\n    \"installation\": \"AVAILABLE\",\n    \"authentication\": \"ON_INSTALL\"\n  },\n  \"category\": \"Productivity\"\n}\n```\n\n- Use `--force` only when intentionally replacing an existing marketplace entry for the same plugin name.\n- If the target marketplace file does not exist yet, create it with top-level `\"name\"`, an `\"interface\"` object containing `\"displayName\"`, and a `plugins` array, then add the new entry.\n\n- For a brand-new marketplace file, the root object should look like:\n\n```json\n{\n  \"name\": \"personal\",\n  \"interface\": {\n    \"displayName\": \"Personal\"\n  },\n  \"plugins\": [\n    {\n      \"name\": \"plugin-name\",\n      \"source\": {\n        \"source\": \"local\",\n        \"path\": \".\u002Fplugins\u002Fplugin-name\"\n      },\n      \"policy\": {\n        \"installation\": \"AVAILABLE\",\n        \"authentication\": \"ON_INSTALL\"\n      },\n      \"category\": \"Productivity\"\n    }\n  ]\n}\n```\n\n## Required behavior\n\n- Outer folder name and `plugin.json` `\"name\"` are always the same normalized plugin name.\n- Do not remove required structure; keep `.codex-plugin\u002Fplugin.json` present.\n- Do not leave `[TODO: ...]` placeholders in plugin manifests.\n- Keep `apps` and `mcpServers` out of `plugin.json` unless their companion files are actually created.\n- Omit unsupported plugin manifest fields that validation rejects, including `hooks`.\n- If creating files inside an existing plugin path, use `--force` only when overwrite is intentional.\n- Preserve any existing marketplace `interface.displayName`.\n- When generating marketplace entries, always write `policy.installation`, `policy.authentication`, and `category` even if their values are defaults.\n- Add `policy.products` only when the user explicitly asks for that override.\n- Keep marketplace `source.path` relative to the selected marketplace root as `.\u002Fplugins\u002F\u003Cplugin-name>`.\n- Only use `--marketplace-name` when creating a new marketplace file whose name should not be\n  `personal` because that name is already taken or installed elsewhere.\n- If Codex would need approval to write the marketplace file, ask for that approval before\n  proceeding. If the user prefers to run the write themselves, provide the exact scaffold command\n  and then continue from validation or subsequent plugin edits instead of leaving the workflow\n  vague.\n- For updates to an existing local plugin during development, do not hand-edit marketplace config\n  or `marketplace.json`. Use the update flow documented in\n  `references\u002Finstalling-and-updating.md` and `scripts\u002Fupdate_plugin_cachebuster.py`.\n- Do not tell the user to run `codex plugin marketplace add` for the default personal-marketplace\n  flow. That command is for explicit non-default marketplace configuration, not for the standard\n  `~\u002F.agents\u002Fplugins\u002Fmarketplace.json` path.\n- If the user provided a non-default `--marketplace-path`, make sure that marketplace is installed\n  before giving reinstall instructions. Use `codex plugin marketplace add \u003Cpath-to-marketplace-root>`\n  when that explicit marketplace has not been configured yet.\n- When the workflow created or updated a marketplace-backed plugin, end the final user-facing\n  response with a short Codex app handoff. Say `To view this in the Codex app:` and write\n  `View \u003Cnormalized plugin name>` and `Share \u003Cnormalized plugin name>` as Markdown links, not raw\n  URLs or code spans.\n- The View deeplink uses `codex:\u002F\u002Fplugins\u002F\u003Cnormalized plugin name>?marketplacePath=\u003Cabsolute marketplace.json path>`.\n  The Share deeplink uses the same URL with `&mode=share`.\n- Replace the placeholders with the real normalized plugin name and absolute `marketplace.json`\n  path from the scaffolded plugin. URL-encode the path segment and query value when needed.\n- Do not add `pluginName` or `hostId` query parameters to these deeplinks. Codex derives both after\n  the user clicks the link.\n- Do not emit the `View \u003Cnormalized plugin name>` or `Share \u003Cnormalized plugin name>` links when no marketplace entry was\n  created or updated.\n\n## Reference to exact spec sample\n\nFor the exact canonical sample JSON for both plugin manifests and marketplace entries, use:\n\n- `references\u002Fplugin-json-spec.md`\n- `references\u002Finstalling-and-updating.md` for update\u002Freinstall guidance while\n  iterating on an existing local plugin, plus the new-thread pickup behavior after reinstall\n\n## Validation\n\nAfter editing `SKILL.md`, run:\n\n```bash\npython3 ..\u002Fskill-creator\u002Fscripts\u002Fquick_validate.py .\n```\n\nBefore handing back a generated plugin, run:\n\n```bash\npython3 scripts\u002Fvalidate_plugin.py \u003Cplugin-path>\n```\n",{"name":5,"description":7},"main","4c6d8d65f3d6096e2fc25b0845e481dda73c2794",".codex\u002Fskills\u002F.system\u002Fplugin-creator",0,"https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions","Building deterministic AI governance and continuity systems. Workflow architect + visual storyteller","2026-11-11 16:42:59",{"source":8,"skillName":5,"commands":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add nexuslinkproductions\u002Fyuri-os --skill plugin-creator",{"tool":58,"command":59},"bunx","bunx skills add nexuslinkproductions\u002Fyuri-os --skill plugin-creator",{"tool":61,"command":62},"pnpm","pnpm dlx skills add nexuslinkproductions\u002Fyuri-os --skill plugin-creator","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002F.system\u002Fplugin-creator\u002FSKILL.md",true,[66,72,78,82,86,92],{"path":67,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":71},"agents\u002Fopenai.yaml","REFERENCE","参考文档",339,"https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002F.system\u002Fplugin-creator\u002Fagents\u002Fopenai.yaml",{"path":73,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":76,"sourceHtmlUrl":77},"assets\u002Fplugin-creator-small.svg","ASSET","资产文件",1319,"https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002F.system\u002Fplugin-creator\u002Fassets\u002Fplugin-creator-small.svg",{"path":79,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":80,"sourceHtmlUrl":81},"assets\u002Fplugin-creator.png",1563,"https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002F.system\u002Fplugin-creator\u002Fassets\u002Fplugin-creator.png",{"path":83,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":84,"sourceHtmlUrl":85},"references\u002Fplugin-json-spec.md",8581,"https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002F.system\u002Fplugin-creator\u002Freferences\u002Fplugin-json-spec.md",{"path":87,"resourceType":88,"resourceTypeDesc":89,"sizeBytes":90,"sourceHtmlUrl":91},"scripts\u002Fcreate_basic_plugin.py","SCRIPT","脚本",11185,"https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002F.system\u002Fplugin-creator\u002Fscripts\u002Fcreate_basic_plugin.py",{"path":93,"resourceType":88,"resourceTypeDesc":89,"sizeBytes":94,"sourceHtmlUrl":95},"scripts\u002Fvalidate_plugin.py",20011,"https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002F.system\u002Fplugin-creator\u002Fscripts\u002Fvalidate_plugin.py",[97,117,140,170,199,218],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":39},"01M71CG1AME5WC0A79AE65WT0X","zoom-out","Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-out\u002FSKILL.md",[],[104,105,23,106,107,108,109,110,111,28,112,26,113,114,115,116],"zoom out","zoom","harness","how","section","re","true","understand","perspective","you","code","it","context",{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":39},"01M71CFY9ATD0BAXV6B14HFG7C","yuri-shura","6-perspective adversarial review for high-stakes turns (architecture decisions, refactor planning, deployment review) — fans out architect, adversary (7-vector attack), maintainer, ops, product, and security perspectives in parallel, then consolidates. Use when user says 'review this decision', '\u002Fshura', 'adversarial review', 'what could go wrong', 'architecture review', or 'deployment review'.","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002Fskills\u002Fyuri-shura\u002FSKILL.md",[],[124,125,106,126,127,35,128,129,130,131,132,28,133,26,134,135,136,137,138,139],"yuri shura","parallel","architecture review","planning","deployment","vector","strategic review","decision","strategic","ops","workflow","decisions","architecture","review","perspectives","adversarial",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":151,"publishedAt":39},"01M71CFTTYW1HA2MNX38EV1GJ5","yuri-sales-intelligence","Unified sales and outreach skill generating cold outreach openers, social selling sequences, objection rebuttals, and ad creative for any paid platform — multi-persona aware, adapting tone and offer frame to buyer type. Use when user says 'write a cold email', 'outreach sequence', 'objection handling', 'ad copy', or 'sales pitch'.","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002Fskills\u002Fyuri-sales-intelligence\u002FSKILL.md",[146],{"categoryNo":147,"categoryName":148,"taxonomyType":149,"taxonomyTypeDesc":150},"01JBSEEDCAT000000000000005","邮件与沟通","SCENARIO","使用场景",[152,153,154,155,156,157,158,159,160,26,161,162,163,164,165,166,167,35,168,169],"intelligence","sales intelligence","yuri sales intelligence","sales","cold","paid","social","persona","pitch","cold email","ad creative","write","sequences","sequence","platform","email","cold outreach","frame",{"skillNo":171,"name":172,"nameZh":6,"description":173,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":174,"categories":175,"keywords":184,"publishedAt":39},"01M71CFQMBFTFADJNGP0Z2WCYK","yuri-code-intelligence","Unified code quality intelligence layer that diagnoses code smells (Long Method, Feature Envy, design pattern issues), prescribes targeted Fowler refactoring techniques, and reviews code for security, performance, and clarity. Use when user says 'review this code', 'refactor this', 'what's wrong with this method', 'code smells', or 'clean this up'.","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002Fskills\u002Fyuri-code-intelligence\u002FSKILL.md",[176,179],{"categoryNo":177,"categoryName":178,"taxonomyType":149,"taxonomyTypeDesc":150},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":180,"categoryName":181,"taxonomyType":182,"taxonomyTypeDesc":183},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[185,114,186,152,106,187,188,189,35,190,191,192,193,194,195,196,197,198,28,26],"yuri code intelligence","code intelligence","reviews","code quality","feature","performance","code review","long","up","issues","clean","techniques","improve","design",{"skillNo":200,"name":201,"nameZh":6,"description":202,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":203,"categories":204,"keywords":205,"publishedAt":39},"01M71CFP32RT6GD3GKNHCJP8VP","yuri-adw","Invoke when user asks to run the ADW loop \u002F agentic engineering loop \u002F software factory workflow.","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002Fskills\u002Fyuri-adw\u002FSKILL.md",[],[206,207,208,209,210,211,212,213,214,26,215,134,216,217],"yuri adw","run","engineering loop","software factory","software","agentic engineering","factory","loop","invoke","engineering","agentic","user",{"skillNo":219,"name":220,"nameZh":6,"description":221,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":222,"categories":223,"keywords":236,"publishedAt":39},"01M71CFK4VPEKY6A73237P7RSN","writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-skills\u002FSKILL.md",[224,227,230,233],{"categoryNo":225,"categoryName":226,"taxonomyType":149,"taxonomyTypeDesc":150},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":228,"categoryName":229,"taxonomyType":149,"taxonomyTypeDesc":150},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":231,"categoryName":232,"taxonomyType":149,"taxonomyTypeDesc":150},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":234,"categoryName":235,"taxonomyType":182,"taxonomyTypeDesc":183},"01JBSEEDCAT000000000000036","内容创作者",[237,238,30,26,134,239,106,240,128,28,27],"writing","writing skills","work","editing"]