[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77VRFFAZPFSY07G96FJXP9A":3,"skill-same:01M77VRFFAZPFSY07G96FJXP9A":55},{"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":27,"commitSha":28,"skillDirectory":29,"forksCount":14,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M77VRFFAZPFSY07G96FJXP9A","od-share-to-community",null,"Package the user's just-finished work as an OpenDesign plugin without asking for fields the project files already answer, then surface the existing Add-to-My-plugins \u002F Open-Design-PR buttons.","hiktan44\u002Fopen-design-app","hiktan44","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F140920746?v=4","01M77SNV7J2RH7G3TQVS2FXMW9","hikmet tanriverdi","01M77SNV87GR8D3BJ9WJHFMZ9Y",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhiktan44\u002Fopen-design-app\u002Fblob\u002Fmain\u002Fplugins\u002F_official\u002Fscenarios\u002Fod-share-to-community\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: od-share-to-community\ndescription: Package the user's just-finished work as an OpenDesign plugin without asking for fields the project files already answer, then surface the existing Add-to-My-plugins \u002F Open-Design-PR buttons.\nod:\n  scenario: plugin-sharing\n  mode: scenario\n---\n\n# od-share-to-community (scenario)\n\nTriggered by the post-completion \"Share to OpenDesign\" submission action. The user just finished a piece of work in this project and wants to ship it as a plugin. They have not been asked any questions yet.\n\n## Required outcome\n\nProduce a folder named `generated-plugin\u002F` in the active project workspace. At minimum:\n\n- `SKILL.md` with frontmatter and clear agent instructions.\n- `open-design.json` with valid plugin metadata: `specVersion`, `name`, `version`, `description`, mode, task kind, inputs, plus any pipeline \u002F context references the workflow needs.\n- `plugin.repo` is optional during scaffolding, but do not silently omit it: check `gh --version` and `gh auth status`, then prefer the local account login printed by auth status. Only use `gh api user --jq .login` as a fallback when auth status does not expose a login. If `gh` is missing, not logged in, rate-limited, or cannot resolve a real owner, omit `plugin.repo` instead of inventing an owner and explicitly report the auth problem with `gh auth refresh -h github.com -s repo,workflow`, `gh auth login -h github.com -s repo,workflow`, or `od plugin publish-repo generated-plugin --owner \u003Cgithub-login-or-org>` as recovery commands. Never write placeholder owners such as `open-design-user`, `\u003Cvendor>`, `example-user`, `your-org`, or `your-username` into the final manifest.\n- Optional `examples\u002F` and `assets\u002F` only when they help review or reuse.\n\n## Auto-derive from the project — do not ask the user fields the files already answer\n\nThe agent's CWD is the user's OD project root. Before generating anything, **read what's already there** and infer the plugin from it. Treat the project files as the source of truth; the user does not need to retype things you can see.\n\nWhat to read, in this order, and what to take from each:\n\n1. `*.artifact.json` (or `artifact.json`) at the project root — task kind, mode, the prompt the user actually ran, the file the agent produced. This drives `od.taskKind`, `od.mode`, the default `useCase.query`, and the example output path.\n2. `brand-spec.md` \u002F `DESIGN.md` if present — voice, brand name, audience. Folds into the plugin description and tags.\n3. The list of generated artifacts in the project workspace (the `*.html`, `*.tsx`, `*.svg`, etc. the agent wrote during this session) — pick the most recent \u002F largest one as `useCase.exampleOutputs[0].path` after copying it under `generated-plugin\u002Fexamples\u002F`.\n4. The user's first prompt in this conversation, if surfaced via the runtime — the natural-language description of what they wanted. Folds into `description` and the default `useCase.query`.\n\nPick a stable plugin id from what you derived: lowercase letters, numbers, dashes, underscores, dots. Prefer something the brand-spec or artifact metadata suggests over inventing one.\n\nIf a field truly cannot be derived (e.g. no artifact.json exists, no brand-spec, the project is too sparse), only then ask the user — and emit **one** consolidated `\u003Cquestion-form>` block, not field-by-field prose questions. Default the answers from whatever you did manage to derive so the user can accept the proposed values directly in the rendered form. `\u003Cquestion-form>` is assistant-text markup rendered by OpenDesign, not a native tool call.\n\n## Validate the plugin locally before reporting\n\nRun `od plugin validate` on the folder, then `od plugin pack` for a tarball, then `od plugin install --source \u003Cabsolute-folder-path>` to confirm the install path works.\n\n## When the work above is done\n\nWrite a single summary turn covering: files created, `od plugin validate` status, local install \u002F run status, and `od plugin pack` output. Then STOP.\n\n## Do NOT chain the publish-repo \u002F Open-Design-PR flows yourself\n\nDo NOT suggest follow-up CLI commands such as `od plugin publish`, `od plugin publish --to open-design`, `gh repo create`, `git init` \u002F `git remote add` \u002F `git push`, or any other publish \u002F repo wiring. The plugin-folder card under Design Files already exposes three buttons whose prompts drive those flows end-to-end with the right auth gates, fallbacks, and retry rules baked in:\n\n- **Add to My plugins** — already satisfied by this turn's `od plugin install --source` step.\n- **Publish repo** — creates \u002F updates the author's `plugin.repo` GitHub repo through a gh + git sequence the agent is told exactly how to run.\n- **OpenDesign PR** — opens a draft PR against `nexu-io\u002Fopen-design` for the community catalog.\n\nPoint the user at whichever button they want next; do NOT recreate those flows as freeform shell suggestions in this summary. Recreating them drifts from the button prompts' guarantees and is the source of the bug that closed #2332.\n\n## Do NOT assume `jq` is on PATH\n\nDo NOT assume the standalone `jq` binary is installed (it is not part of the OD agent runtime baseline and is missing from default macOS \u002F Windows shells). When you need to read the manifest, prefer your built-in file-reading tool, then `cat generated-plugin\u002Fopen-design.json` followed by manual JSON parsing, then `node -e 'console.log(JSON.parse(require(\"fs\").readFileSync(\"generated-plugin\u002Fopen-design.json\",\"utf8\")))'`. The `gh ... --jq` flag is fine because gh ships its own embedded library; the brew-installed standalone `jq` is NOT.\n\n## Language\n\nMirror the user's chat language in any `\u003Cquestion-form>` titles, labels, descriptions, options, and helper text, as well as status updates and error explanations. Generated artifacts (manifest fields, SKILL.md body, PR \u002F commit messages, branch names) MUST stay English regardless of the chat language — that's the OD plugins-spec convention and matches the existing scenarios under `plugins\u002F_official\u002Fscenarios\u002F`.\n\n## Suggested folder shape\n\n```text\ngenerated-plugin\u002F\n  SKILL.md\n  open-design.json\n  examples\u002F\n    \u003Ccopied-from-the-project>\n  assets\u002F\n    \u003Cif-needed>\n```\n\n## Spec references\n\n- `docs\u002Fplugins-spec.md`\n- `docs\u002Fschemas\u002Fopen-design.plugin.v1.json`\n- The sibling `plugins\u002F_official\u002Fscenarios\u002Fod-plugin-authoring\u002FSKILL.md` for the from-scratch authoring counterpart.\n","# od-share-to-community (scenario)\n\nTriggered by the post-completion \"Share to OpenDesign\" submission action. The user just finished a piece of work in this project and wants to ship it as a plugin. They have not been asked any questions yet.\n\n## Required outcome\n\nProduce a folder named `generated-plugin\u002F` in the active project workspace. At minimum:\n\n- `SKILL.md` with frontmatter and clear agent instructions.\n- `open-design.json` with valid plugin metadata: `specVersion`, `name`, `version`, `description`, mode, task kind, inputs, plus any pipeline \u002F context references the workflow needs.\n- `plugin.repo` is optional during scaffolding, but do not silently omit it: check `gh --version` and `gh auth status`, then prefer the local account login printed by auth status. Only use `gh api user --jq .login` as a fallback when auth status does not expose a login. If `gh` is missing, not logged in, rate-limited, or cannot resolve a real owner, omit `plugin.repo` instead of inventing an owner and explicitly report the auth problem with `gh auth refresh -h github.com -s repo,workflow`, `gh auth login -h github.com -s repo,workflow`, or `od plugin publish-repo generated-plugin --owner \u003Cgithub-login-or-org>` as recovery commands. Never write placeholder owners such as `open-design-user`, `\u003Cvendor>`, `example-user`, `your-org`, or `your-username` into the final manifest.\n- Optional `examples\u002F` and `assets\u002F` only when they help review or reuse.\n\n## Auto-derive from the project — do not ask the user fields the files already answer\n\nThe agent's CWD is the user's OD project root. Before generating anything, **read what's already there** and infer the plugin from it. Treat the project files as the source of truth; the user does not need to retype things you can see.\n\nWhat to read, in this order, and what to take from each:\n\n1. `*.artifact.json` (or `artifact.json`) at the project root — task kind, mode, the prompt the user actually ran, the file the agent produced. This drives `od.taskKind`, `od.mode`, the default `useCase.query`, and the example output path.\n2. `brand-spec.md` \u002F `DESIGN.md` if present — voice, brand name, audience. Folds into the plugin description and tags.\n3. The list of generated artifacts in the project workspace (the `*.html`, `*.tsx`, `*.svg`, etc. the agent wrote during this session) — pick the most recent \u002F largest one as `useCase.exampleOutputs[0].path` after copying it under `generated-plugin\u002Fexamples\u002F`.\n4. The user's first prompt in this conversation, if surfaced via the runtime — the natural-language description of what they wanted. Folds into `description` and the default `useCase.query`.\n\nPick a stable plugin id from what you derived: lowercase letters, numbers, dashes, underscores, dots. Prefer something the brand-spec or artifact metadata suggests over inventing one.\n\nIf a field truly cannot be derived (e.g. no artifact.json exists, no brand-spec, the project is too sparse), only then ask the user — and emit **one** consolidated `\u003Cquestion-form>` block, not field-by-field prose questions. Default the answers from whatever you did manage to derive so the user can accept the proposed values directly in the rendered form. `\u003Cquestion-form>` is assistant-text markup rendered by OpenDesign, not a native tool call.\n\n## Validate the plugin locally before reporting\n\nRun `od plugin validate` on the folder, then `od plugin pack` for a tarball, then `od plugin install --source \u003Cabsolute-folder-path>` to confirm the install path works.\n\n## When the work above is done\n\nWrite a single summary turn covering: files created, `od plugin validate` status, local install \u002F run status, and `od plugin pack` output. Then STOP.\n\n## Do NOT chain the publish-repo \u002F Open-Design-PR flows yourself\n\nDo NOT suggest follow-up CLI commands such as `od plugin publish`, `od plugin publish --to open-design`, `gh repo create`, `git init` \u002F `git remote add` \u002F `git push`, or any other publish \u002F repo wiring. The plugin-folder card under Design Files already exposes three buttons whose prompts drive those flows end-to-end with the right auth gates, fallbacks, and retry rules baked in:\n\n- **Add to My plugins** — already satisfied by this turn's `od plugin install --source` step.\n- **Publish repo** — creates \u002F updates the author's `plugin.repo` GitHub repo through a gh + git sequence the agent is told exactly how to run.\n- **OpenDesign PR** — opens a draft PR against `nexu-io\u002Fopen-design` for the community catalog.\n\nPoint the user at whichever button they want next; do NOT recreate those flows as freeform shell suggestions in this summary. Recreating them drifts from the button prompts' guarantees and is the source of the bug that closed #2332.\n\n## Do NOT assume `jq` is on PATH\n\nDo NOT assume the standalone `jq` binary is installed (it is not part of the OD agent runtime baseline and is missing from default macOS \u002F Windows shells). When you need to read the manifest, prefer your built-in file-reading tool, then `cat generated-plugin\u002Fopen-design.json` followed by manual JSON parsing, then `node -e 'console.log(JSON.parse(require(\"fs\").readFileSync(\"generated-plugin\u002Fopen-design.json\",\"utf8\")))'`. The `gh ... --jq` flag is fine because gh ships its own embedded library; the brew-installed standalone `jq` is NOT.\n\n## Language\n\nMirror the user's chat language in any `\u003Cquestion-form>` titles, labels, descriptions, options, and helper text, as well as status updates and error explanations. Generated artifacts (manifest fields, SKILL.md body, PR \u002F commit messages, branch names) MUST stay English regardless of the chat language — that's the OD plugins-spec convention and matches the existing scenarios under `plugins\u002F_official\u002Fscenarios\u002F`.\n\n## Suggested folder shape\n\n```text\ngenerated-plugin\u002F\n  SKILL.md\n  open-design.json\n  examples\u002F\n    \u003Ccopied-from-the-project>\n  assets\u002F\n    \u003Cif-needed>\n```\n\n## Spec references\n\n- `docs\u002Fplugins-spec.md`\n- `docs\u002Fschemas\u002Fopen-design.plugin.v1.json`\n- The sibling `plugins\u002F_official\u002Fscenarios\u002Fod-plugin-authoring\u002FSKILL.md` for the from-scratch authoring counterpart.\n",{"od":24,"name":5,"description":7},{"mode":25,"scenario":26},"scenario","plugin-sharing","main","f403d5b733fab92eab16d13e9baf3ac951afed55","plugins\u002F_official\u002Fscenarios\u002Fod-share-to-community","https:\u002F\u002Fgithub.com\u002Fhiktan44\u002Fopen-design-app","https:\u002F\u002Fgithub.com\u002Fhiktan44","fasheone.com","Hikmet Tanrıverdi\r\nSTRATEJI DANIŞMANLIK, 2008-2018 İHKİB İSTANBUL HAZIR GİYİM BŞK, İTO MECLİS ÜYESİ, TEXMART DIŞ TİCARET YK STRATEGY CONSULTING, 2008-2018 PRESI","2026-10-11 23:59:08",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add hiktan44\u002Fopen-design-app --skill od-share-to-community",{"tool":41,"command":42},"bunx","bunx skills add hiktan44\u002Fopen-design-app --skill od-share-to-community",{"tool":44,"command":45},"pnpm","pnpm dlx skills add hiktan44\u002Fopen-design-app --skill od-share-to-community","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhiktan44\u002Fopen-design-app\u002Fblob\u002Fmain\u002Fplugins\u002F_official\u002Fscenarios\u002Fod-share-to-community\u002FSKILL.md",true,[49],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"open-design.json","REFERENCE","参考文档",3158,"https:\u002F\u002Fgithub.com\u002Fhiktan44\u002Fopen-design-app\u002Fblob\u002Fmain\u002Fplugins\u002F_official\u002Fscenarios\u002Fod-share-to-community\u002Fopen-design.json",[56,63,70,77,84,93],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M77WGV99HNV3Q6JN3H8Z70JE","Beta Skill","Instruction-only fixture skill.","https:\u002F\u002Fgithub.com\u002Fhiktan44\u002Fopen-design-app\u002Fblob\u002Fmain\u002Ftools\u002Frelease\u002Ftests\u002Ffixtures\u002Fcatalog\u002Fskills\u002Fbeta\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M77WGRXNRGHT9J1K929BPV5H","Alpha Skill","First fixture skill with a runnable demo.","https:\u002F\u002Fgithub.com\u002Fhiktan44\u002Fopen-design-app\u002Fblob\u002Fmain\u002Ftools\u002Frelease\u002Ftests\u002Ffixtures\u002Fcatalog\u002Fskills\u002Falpha\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M77WGQK7F7R1W6RBFZFEZ53M","Deck One","A small deck template fixture.","https:\u002F\u002Fgithub.com\u002Fhiktan44\u002Fopen-design-app\u002Fblob\u002Fmain\u002Ftools\u002Frelease\u002Ftests\u002Ffixtures\u002Fcatalog\u002Fdesign-templates\u002Fdeck-one\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M77WGNPEGTDWMKDX659FS5DT","youtube-clipper","YouTube clip generation and editing with automated workflows — pull source video, slice highlights, add captions, and export.","https:\u002F\u002Fgithub.com\u002Fhiktan44\u002Fopen-design-app\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube-clipper\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":88,"licenseFileUrl":89,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M77WGJ9KKT6Q4P10GAV3KC48","writing-guidelines","Review docs\u002Fprose for Writing Guidelines compliance. Use when asked to \"review my docs\", \"check writing style\", \"audit prose\", \"review docs voice and tone\", or \"check this page against the writing handbook\".","MIT","https:\u002F\u002Fgithub.com\u002Fhiktan44\u002Fopen-design-app\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-guidelines\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhiktan44\u002Fopen-design-app\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-guidelines\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},"01M77WGF9P0WT4XBXMM0B9WRGR","wpds","WordPress Design System. Apply WordPress's official design tokens, typography, and component patterns to themes and sites.","https:\u002F\u002Fgithub.com\u002Fhiktan44\u002Fopen-design-app\u002Fblob\u002Fmain\u002Fskills\u002Fwpds\u002FSKILL.md",[],[]]