[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AV34VS072A8KTMERTXM1MB":3,"skill-same:01M7AV34VS072A8KTMERTXM1MB":51},{"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":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7AV34VS072A8KTMERTXM1MB","dsh-doc-site-sync",null,"Use when publishing, updating, moving, or removing DeepSeek Harness documentation website pages; editing website\u002Fdocs.ts mappings or navigation; diagnosing a page missing from the VitePress site; fixing projected documentation links; or running the docs:dev, docs:check, and doc-sync workflow after website-content changes.","vignesh050694\u002Fdeepseek_harness","vignesh050694","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F28592443?v=4","01M7AV2QCAEBS9GXAGZZ4JRTV3","Vignesh V","01M7AV2QDMQ7J8CVBHKHWQPC9R",0,"MIT","https:\u002F\u002Fgithub.com\u002Fvignesh050694\u002Fdeepseek_harness\u002Fblob\u002Fchore\u002Fremove-chinese-i18n\u002F.agents\u002Fskills\u002Fdsh-doc-site-sync\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: dsh-doc-site-sync\ndescription: Use when publishing, updating, moving, or removing DeepSeek Harness documentation website pages; editing website\u002Fdocs.ts mappings or navigation; diagnosing a page missing from the VitePress site; fixing projected documentation links; or running the docs:dev, docs:check, and doc-sync workflow after website-content changes.\n---\n\n# Synchronizing the DeepSeek Harness Documentation Site\n\nKeep repository Markdown as the only editable content source. Treat the website as a tested projection: [website\u002Fdocs.ts](..\u002F..\u002F..\u002Fwebsite\u002Fdocs.ts) selects public pages, [scripts\u002Fproject-doc-site.ts](..\u002F..\u002F..\u002Fscripts\u002Fproject-doc-site.ts) rewrites them into the disposable `website\u002F.generated\u002F` tree, and VitePress builds that tree.\n\nRepository translations follow the sibling pairing contract: English `foo.md`, Chinese `foo.zh.md`, and `foo.i18n.yaml` live together. Never create `zh-CN\u002F` or other locale directories for website content. The site route trees are independent of that source layout: `foo.zh.md` projects to the root route and `foo.md` projects to the matching `\u002Fen\u002F` route.\n\n## Read the owning contracts\n\n- Read [docs\u002FAGENTS.md](..\u002F..\u002F..\u002Fdocs\u002FAGENTS.md) and use [dsh-doc-standards](..\u002Fdsh-doc-standards\u002FSKILL.md) when deciding where content belongs or changing product documentation prose.\n- Read the current `DocsPage` type and entries in [website\u002Fdocs.ts](..\u002F..\u002F..\u002Fwebsite\u002Fdocs.ts) before changing the manifest; do not rely on a remembered field set.\n- Read [website\u002F.vitepress\u002Fconfig.ts](..\u002F..\u002F..\u002Fwebsite\u002F.vitepress\u002Fconfig.ts) before adding a new section, sidebar collection, locale, or top-level navigation item.\n\n## Classify the change\n\n- **Edit an already published page:** change only its canonical Markdown source. Do not touch the manifest unless its route or navigation metadata changes.\n- **Publish a new page:** create it in its owning `docs\u002F` tier, then add one manifest entry.\n- **Rename, move, or remove a page:** update the canonical file, manifest entry, and inbound repository links atomically. Remove stale manifest entries; `docs:check` rejects missing sources.\n- **Publish a generated catalog:** map the generated `docs\u002F` file, but change its generator or source metadata rather than editing the catalog by hand.\n- **Change site structure:** update the manifest for ordinary pages; update VitePress configuration only when the existing sidebar, section, or locale model cannot express the change.\n\nNever edit or commit `website\u002F.generated\u002F`, `website\u002F.cache\u002F`, or `website\u002F.dist\u002F`. Except for `website\u002FAGENTS.md`, never add Markdown under `website\u002F`; locale and route directories such as `website\u002Fzh-CN\u002F`, `website\u002Fen\u002F`, and `website\u002Fapi\u002F` are invalid source layouts. Keep generated catalogs under `docs\u002F`, freshness-gate them there, and publish them through the manifest.\n\n## Add or update a manifest entry\n\nSet every `DocsPage` field deliberately:\n\n- `source`: repository-relative canonical Markdown path. For a complete bilingual pair, add the English `.md` path through `pairedPages()`; it derives the sibling `.zh.md`, the content locales, and counterpart aliases.\n- `route`: public VitePress path including the `.md` suffix.\n- `label`: sidebar label, not necessarily the document H1.\n- `sidebar`: reuse `zh-guide`, `zh-develop`, or `en-docs` unless the information architecture genuinely needs another collection.\n- `section`: reuse an existing section when possible. If adding one, also place it in `sectionOrder` in the VitePress config.\n- `order`: stable order within the section.\n- `sourceAliases`: optional additional repository paths that should resolve to this page when links are projected. It does not create another public route.\n\nUse `mirroredPages()` only for a source that intentionally falls back to the same available language in both route trees. Convert that entry to `pairedPages()` when its counterpart is added. Keep the manifest an explicit public allowlist. Do not publish RFCs, postmortems, testing guides, `AGENTS.md`, or maintainer workflows merely because they exist under `docs\u002F`; add internal material only when the user explicitly expands what the site publishes.\n\n## Preserve link behavior\n\nWrite normal repository-relative Markdown links in canonical docs. The projector applies these rules:\n\n- A target present in the manifest becomes a site-relative route.\n- An existing target outside the manifest becomes a GitHub source link, including supported line suffixes.\n- An image is the exception: its file is copied into the generated tree and referenced from there, so the site serves it regardless of repository visibility. It must be a regular file inside the repository.\n- External URLs, site-absolute URLs, email links, and fragment-only links remain unchanged.\n- A missing repository-relative target fails projection instead of silently producing a broken link.\n- Cross-page fragments use the English GitHub heading id as their canonical id. If an authored heading emits a different VitePress id, place an explicit `\u003Ca id=\"...\">\u003C\u002Fa>` immediately before it; add generated aliases in the owning generator.\n\nDo not write website-specific routes into canonical Markdown just to satisfy VitePress. Use `sourceAliases` for directory-style repository links that should resolve to a mapped index page.\n\n## Preview and validate\n\nRun local preview while editing:\n\n```sh\npnpm docs:dev\n```\n\nThe dev server watches mapped source files and reprojects them. Restart it after changing the manifest if the new source is not picked up automatically.\n\nRun the focused website gate before treating the mapping as valid:\n\n```sh\npnpm docs:check\n```\n\nIf Markdown link checks pass but the site build reports a missing fragment, follow the `verify-doc-site-fragments` source and target paths. Preserve the English GitHub id with an explicit alias in authored Markdown or in the owning generator.\n\nBefore committing a documentation-site change, run:\n\n```sh\npnpm run doc-sync\npnpm run lint\ngit diff --check\n```\n\nUse [dsh-pre-push-checks](..\u002Fdsh-pre-push-checks\u002FSKILL.md) before pushing. Report the canonical files changed, manifest entries added or removed, public routes affected, and the exact checks run.\n\n## Keep deployment separate\n\nSynchronizing content into the VitePress build does not publish it to the internet. Do not add GitHub Pages permissions, deployment workflows, custom domains, or public hosting unless the user explicitly requests deployment and confirms the hosting policy.\n","# Synchronizing the DeepSeek Harness Documentation Site\n\nKeep repository Markdown as the only editable content source. Treat the website as a tested projection: [website\u002Fdocs.ts](..\u002F..\u002F..\u002Fwebsite\u002Fdocs.ts) selects public pages, [scripts\u002Fproject-doc-site.ts](..\u002F..\u002F..\u002Fscripts\u002Fproject-doc-site.ts) rewrites them into the disposable `website\u002F.generated\u002F` tree, and VitePress builds that tree.\n\nRepository translations follow the sibling pairing contract: English `foo.md`, Chinese `foo.zh.md`, and `foo.i18n.yaml` live together. Never create `zh-CN\u002F` or other locale directories for website content. The site route trees are independent of that source layout: `foo.zh.md` projects to the root route and `foo.md` projects to the matching `\u002Fen\u002F` route.\n\n## Read the owning contracts\n\n- Read [docs\u002FAGENTS.md](..\u002F..\u002F..\u002Fdocs\u002FAGENTS.md) and use [dsh-doc-standards](..\u002Fdsh-doc-standards\u002FSKILL.md) when deciding where content belongs or changing product documentation prose.\n- Read the current `DocsPage` type and entries in [website\u002Fdocs.ts](..\u002F..\u002F..\u002Fwebsite\u002Fdocs.ts) before changing the manifest; do not rely on a remembered field set.\n- Read [website\u002F.vitepress\u002Fconfig.ts](..\u002F..\u002F..\u002Fwebsite\u002F.vitepress\u002Fconfig.ts) before adding a new section, sidebar collection, locale, or top-level navigation item.\n\n## Classify the change\n\n- **Edit an already published page:** change only its canonical Markdown source. Do not touch the manifest unless its route or navigation metadata changes.\n- **Publish a new page:** create it in its owning `docs\u002F` tier, then add one manifest entry.\n- **Rename, move, or remove a page:** update the canonical file, manifest entry, and inbound repository links atomically. Remove stale manifest entries; `docs:check` rejects missing sources.\n- **Publish a generated catalog:** map the generated `docs\u002F` file, but change its generator or source metadata rather than editing the catalog by hand.\n- **Change site structure:** update the manifest for ordinary pages; update VitePress configuration only when the existing sidebar, section, or locale model cannot express the change.\n\nNever edit or commit `website\u002F.generated\u002F`, `website\u002F.cache\u002F`, or `website\u002F.dist\u002F`. Except for `website\u002FAGENTS.md`, never add Markdown under `website\u002F`; locale and route directories such as `website\u002Fzh-CN\u002F`, `website\u002Fen\u002F`, and `website\u002Fapi\u002F` are invalid source layouts. Keep generated catalogs under `docs\u002F`, freshness-gate them there, and publish them through the manifest.\n\n## Add or update a manifest entry\n\nSet every `DocsPage` field deliberately:\n\n- `source`: repository-relative canonical Markdown path. For a complete bilingual pair, add the English `.md` path through `pairedPages()`; it derives the sibling `.zh.md`, the content locales, and counterpart aliases.\n- `route`: public VitePress path including the `.md` suffix.\n- `label`: sidebar label, not necessarily the document H1.\n- `sidebar`: reuse `zh-guide`, `zh-develop`, or `en-docs` unless the information architecture genuinely needs another collection.\n- `section`: reuse an existing section when possible. If adding one, also place it in `sectionOrder` in the VitePress config.\n- `order`: stable order within the section.\n- `sourceAliases`: optional additional repository paths that should resolve to this page when links are projected. It does not create another public route.\n\nUse `mirroredPages()` only for a source that intentionally falls back to the same available language in both route trees. Convert that entry to `pairedPages()` when its counterpart is added. Keep the manifest an explicit public allowlist. Do not publish RFCs, postmortems, testing guides, `AGENTS.md`, or maintainer workflows merely because they exist under `docs\u002F`; add internal material only when the user explicitly expands what the site publishes.\n\n## Preserve link behavior\n\nWrite normal repository-relative Markdown links in canonical docs. The projector applies these rules:\n\n- A target present in the manifest becomes a site-relative route.\n- An existing target outside the manifest becomes a GitHub source link, including supported line suffixes.\n- An image is the exception: its file is copied into the generated tree and referenced from there, so the site serves it regardless of repository visibility. It must be a regular file inside the repository.\n- External URLs, site-absolute URLs, email links, and fragment-only links remain unchanged.\n- A missing repository-relative target fails projection instead of silently producing a broken link.\n- Cross-page fragments use the English GitHub heading id as their canonical id. If an authored heading emits a different VitePress id, place an explicit `\u003Ca id=\"...\">\u003C\u002Fa>` immediately before it; add generated aliases in the owning generator.\n\nDo not write website-specific routes into canonical Markdown just to satisfy VitePress. Use `sourceAliases` for directory-style repository links that should resolve to a mapped index page.\n\n## Preview and validate\n\nRun local preview while editing:\n\n```sh\npnpm docs:dev\n```\n\nThe dev server watches mapped source files and reprojects them. Restart it after changing the manifest if the new source is not picked up automatically.\n\nRun the focused website gate before treating the mapping as valid:\n\n```sh\npnpm docs:check\n```\n\nIf Markdown link checks pass but the site build reports a missing fragment, follow the `verify-doc-site-fragments` source and target paths. Preserve the English GitHub id with an explicit alias in authored Markdown or in the owning generator.\n\nBefore committing a documentation-site change, run:\n\n```sh\npnpm run doc-sync\npnpm run lint\ngit diff --check\n```\n\nUse [dsh-pre-push-checks](..\u002Fdsh-pre-push-checks\u002FSKILL.md) before pushing. Report the canonical files changed, manifest entries added or removed, public routes affected, and the exact checks run.\n\n## Keep deployment separate\n\nSynchronizing content into the VitePress build does not publish it to the internet. Do not add GitHub Pages permissions, deployment workflows, custom domains, or public hosting unless the user explicitly requests deployment and confirms the hosting policy.\n",{"name":5,"description":7},"chore\u002Fremove-chinese-i18n","06fa4a35d98953badf69a1df45b1d70e250282ca",".agents\u002Fskills\u002Fdsh-doc-site-sync","https:\u002F\u002Fgithub.com\u002Fvignesh050694\u002Fdeepseek_harness","https:\u002F\u002Fgithub.com\u002Fvignesh050694","calpyte.com","2026-09-21 12:05:15",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add vignesh050694\u002Fdeepseek_harness --skill dsh-doc-site-sync",{"tool":37,"command":38},"bunx","bunx skills add vignesh050694\u002Fdeepseek_harness --skill dsh-doc-site-sync",{"tool":40,"command":41},"pnpm","pnpm dlx skills add vignesh050694\u002Fdeepseek_harness --skill dsh-doc-site-sync","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvignesh050694\u002Fdeepseek_harness\u002Fblob\u002Fchore\u002Fremove-chinese-i18n\u002F.agents\u002Fskills\u002Fdsh-doc-site-sync\u002FSKILL.md",true,[45],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"agents\u002Fopenai.yaml","REFERENCE","参考文档",255,"https:\u002F\u002Fgithub.com\u002Fvignesh050694\u002Fdeepseek_harness\u002Fblob\u002Fchore\u002Fremove-chinese-i18n\u002F.agents\u002Fskills\u002Fdsh-doc-site-sync\u002Fagents\u002Fopenai.yaml",[52,59,66,73,80,87],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M7AV4XEMT19VE71MGJA7Z70R","user-only-skill","Prove model-disabled skills stay outside the model catalog.","https:\u002F\u002Fgithub.com\u002Fvignesh050694\u002Fdeepseek_harness\u002Fblob\u002Fchore\u002Fremove-chinese-i18n\u002Fexamples\u002Facp-agent\u002Ftests\u002Fsnapshots\u002Fskill-load\u002Fworkspace\u002F.dsh\u002Fskills\u002Fuser-only-skill\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M7AV4W4MFDZH6X15H1PN2QA8","snapshot-skill","Exercise project skill discovery and loading in snapshot tests.","https:\u002F\u002Fgithub.com\u002Fvignesh050694\u002Fdeepseek_harness\u002Fblob\u002Fchore\u002Fremove-chinese-i18n\u002Fexamples\u002Facp-agent\u002Ftests\u002Fsnapshots\u002Fskill-load\u002Fworkspace\u002F.dsh\u002Fskills\u002Fsnapshot-skill\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M7AV4TPBT8H7JH9QEKSJB00R","model-only-skill","Prove user-disabled skills remain available to the model.","https:\u002F\u002Fgithub.com\u002Fvignesh050694\u002Fdeepseek_harness\u002Fblob\u002Fchore\u002Fremove-chinese-i18n\u002Fexamples\u002Facp-agent\u002Ftests\u002Fsnapshots\u002Fskill-load\u002Fworkspace\u002F.dsh\u002Fskills\u002Fmodel-only-skill\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7AV4PKKWSTASVS6X2DSG4X9","editing-cordis-compositions","Use when creating, changing, or validating a Cordis composition for this harness — writing or editing an agent preset, adding or removing a plugin row, deciding whether something belongs to the host composition or to one session, checking whether a preset you authored actually mounts, or diagnosing a row that mounted but contributed nothing.","https:\u002F\u002Fgithub.com\u002Fvignesh050694\u002Fdeepseek_harness\u002Fblob\u002Fchore\u002Fremove-chinese-i18n\u002Fapps\u002Fcli\u002Fconfig\u002Fagent-presets\u002Fcordis\u002Fskills\u002Fediting-cordis-compositions\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7AV4G69RJK29FFHRADKVNYW","cordis-plugin-development","Create, modify, debug, or extend dynamic Cordis Plugins, including Host Services and Events, Client Slot and theme UI, Package-private Client-to-Host calls, dynamic Tools, version updates, approval failures, and runtime diagnostics. Use this Skill to route a user request to the correct platform and Inspect Provider, then define, run, repair, or roll back the Plugin.","https:\u002F\u002Fgithub.com\u002Fvignesh050694\u002Fdeepseek_harness\u002Fblob\u002Fchore\u002Fremove-chinese-i18n\u002Fapps\u002Fcli\u002Fconfig\u002Fagent-presets\u002Fcordis\u002Fskills\u002Fcordis-plugin-development\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M7AV4AHM7FRMHKHQJCBKKE1R","record-browser-gif","Record browser or Web UI interaction demos as optimized GIFs using the available built-in browser, state-based frame capture, and deterministic encoding, then publish to a dedicated assets branch when the task includes attaching the GIF to a pull request. Use when asked to make, record, or generate a GIF that demonstrates a browser workflow, and for every pull request that changes product-user-visible GUI behavior, which MUST include a GIF recorded from the pull request's real server and model flow.","https:\u002F\u002Fgithub.com\u002Fvignesh050694\u002Fdeepseek_harness\u002Fblob\u002Fchore\u002Fremove-chinese-i18n\u002F.agents\u002Fskills\u002Frecord-browser-gif\u002FSKILL.md",[],[]]