[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FCNFE68HC4B8TEWWK7D2MP":3,"skill-same:01M7FCNFE68HC4B8TEWWK7D2MP":45},{"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":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M7FCNFE68HC4B8TEWWK7D2MP","dsh-create-upgrade-guide",null,"Use when a deepseek-harness change breaks an externally perceptible surface (CLI, profiles, cordis.yml or settings keys, persisted user data, SDK or wire APIs, published package entry points), or when changing a surface that an unreleased upgrade guide already covers, to write or update docs\u002Fupgrade-guide\u002Fv\u003Cversion>\u002F\u003Citem>\u002Fguide.md.","bhjia-phys\u002FAITP-agent","bhjia-phys","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F177605027?v=4","01M7FCMB9A3SGB3C2VY4K0RR2P","Bohan Jia","01M7FCMBA57SVVPTA0XRYWTEMK",1,"MIT","https:\u002F\u002Fgithub.com\u002Fbhjia-phys\u002FAITP-agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fdsh-create-upgrade-guide\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: dsh-create-upgrade-guide\ndescription: Use when a deepseek-harness change breaks an externally perceptible surface (CLI, profiles, cordis.yml or settings keys, persisted user data, SDK or wire APIs, published package entry points), or when changing a surface that an unreleased upgrade guide already covers, to write or update docs\u002Fupgrade-guide\u002Fv\u003Cversion>\u002F\u003Citem>\u002Fguide.md.\n---\n\n# DSH Create Upgrade Guide\n\nAn upgrade guide tells a reader who runs release vT what to change to run the next release. Write it in the change that introduces the break, as soon as the break is recognized; do not defer it to release preparation.\n\n## Scope\n\nWrite a guide only for breaks that someone outside the repository can observe after upgrading:\n\n- `dsh` commands, flags, and profile names;\n- `cordis.yml`, patch, overlay, and settings keys or their accepted values;\n- persisted user data: Session logs, SQLite stores, and user data directories;\n- TypeScript and Python SDK exports, JSON-RPC, HTTP, and ACP messages;\n- published package names and entry points.\n\nPre-stable internal APIs whose consumers are all updated in the same change need no guide. A Session-format change still follows [type acknowledgements](..\u002F..\u002F..\u002Fdocs\u002Fcookbook\u002Freviewing-persistence-type-changes.md); its guide states only the reader's actions and links that record.\n\n## Location\n\n`docs\u002Fupgrade-guide\u002Fv\u003Cversion>\u002F\u003Citem>\u002Fguide.md`\n\n- `\u003Cversion>` is the `version` field of the root `package.json` when you write the guide, for example `v0.1.7-rc.2`. The guide describes the upgrade from that release to the next one.\n- `\u003Citem>` is a kebab-case name of the changed surface, for example `profile-flag-rename`.\n- Each item directory holds exactly `guide.md`, its Chinese counterpart `guide.zh.md`, and the pairing record `guide.i18n.yaml`: no index, no attachments.\n\n## Maintenance\n\nWhile the root version is unchanged, the current version directory describes the delta from vT to current `master`. When a later change touches a surface a guide there covers, update that guide in the same change; delete the guide when the break is reverted. After the version bump, guides in older version directories are frozen; a new break goes into the new version directory. Never write a guide spanning more than one release.\n\n## Format\n\nStart from the [upgrade-guide template](..\u002Fdsh-doc\u002Ftemplates\u002Fupgrade-guide.md). `verify-upgrade-guides` enforces:\n\n- frontmatter with exactly `kind: upgrade-guide` and a one-sentence `description` naming what breaks; add a key only together with its gate check, then backfill every guide;\n- one `#` title, then exactly the `## Change` and `## Migration` sections in `guide.md`, and `## 变更` and `## 迁移` in `guide.zh.md`, in that order;\n- at most 500 words in `guide.md`, frontmatter included.\n\n`Change` states the old and new behavior of the surface and who is affected. `Migration` lists ordered steps that name exact files, keys, commands, or symbols, and states how to confirm the migration worked.\n\nWhen a guide needs more than 500 words, the extra text belongs elsewhere: link source files or symbols instead of restating code, move rationale into an [Agent Note](..\u002F..\u002Fnotes\u002FREADME.md), and turn repeated mechanical steps into a script or `dsh` command that the guide invokes.\n\nFollow [dsh-prose-standard](..\u002Fdsh-prose-standard\u002FSKILL.md). Write the Chinese counterpart in the same change under the [bilingual pairing rules](..\u002F..\u002F..\u002Fdocs\u002FAGENTS.md), then record the pair with `pnpm run verify-translation-pairing --write docs\u002Fupgrade-guide\u002Fv\u003Cversion>\u002F\u003Citem>\u002Fguide.md`.\n\n## Verify\n\n```sh\npnpm run verify-upgrade-guides\npnpm run verify-translation-pairing docs\u002Fupgrade-guide\u002Fv\u003Cversion>\u002F\u003Citem>\u002Fguide.md\npnpm run verify-md-links\n```\n","# DSH Create Upgrade Guide\n\nAn upgrade guide tells a reader who runs release vT what to change to run the next release. Write it in the change that introduces the break, as soon as the break is recognized; do not defer it to release preparation.\n\n## Scope\n\nWrite a guide only for breaks that someone outside the repository can observe after upgrading:\n\n- `dsh` commands, flags, and profile names;\n- `cordis.yml`, patch, overlay, and settings keys or their accepted values;\n- persisted user data: Session logs, SQLite stores, and user data directories;\n- TypeScript and Python SDK exports, JSON-RPC, HTTP, and ACP messages;\n- published package names and entry points.\n\nPre-stable internal APIs whose consumers are all updated in the same change need no guide. A Session-format change still follows [type acknowledgements](..\u002F..\u002F..\u002Fdocs\u002Fcookbook\u002Freviewing-persistence-type-changes.md); its guide states only the reader's actions and links that record.\n\n## Location\n\n`docs\u002Fupgrade-guide\u002Fv\u003Cversion>\u002F\u003Citem>\u002Fguide.md`\n\n- `\u003Cversion>` is the `version` field of the root `package.json` when you write the guide, for example `v0.1.7-rc.2`. The guide describes the upgrade from that release to the next one.\n- `\u003Citem>` is a kebab-case name of the changed surface, for example `profile-flag-rename`.\n- Each item directory holds exactly `guide.md`, its Chinese counterpart `guide.zh.md`, and the pairing record `guide.i18n.yaml`: no index, no attachments.\n\n## Maintenance\n\nWhile the root version is unchanged, the current version directory describes the delta from vT to current `master`. When a later change touches a surface a guide there covers, update that guide in the same change; delete the guide when the break is reverted. After the version bump, guides in older version directories are frozen; a new break goes into the new version directory. Never write a guide spanning more than one release.\n\n## Format\n\nStart from the [upgrade-guide template](..\u002Fdsh-doc\u002Ftemplates\u002Fupgrade-guide.md). `verify-upgrade-guides` enforces:\n\n- frontmatter with exactly `kind: upgrade-guide` and a one-sentence `description` naming what breaks; add a key only together with its gate check, then backfill every guide;\n- one `#` title, then exactly the `## Change` and `## Migration` sections in `guide.md`, and `## 变更` and `## 迁移` in `guide.zh.md`, in that order;\n- at most 500 words in `guide.md`, frontmatter included.\n\n`Change` states the old and new behavior of the surface and who is affected. `Migration` lists ordered steps that name exact files, keys, commands, or symbols, and states how to confirm the migration worked.\n\nWhen a guide needs more than 500 words, the extra text belongs elsewhere: link source files or symbols instead of restating code, move rationale into an [Agent Note](..\u002F..\u002Fnotes\u002FREADME.md), and turn repeated mechanical steps into a script or `dsh` command that the guide invokes.\n\nFollow [dsh-prose-standard](..\u002Fdsh-prose-standard\u002FSKILL.md). Write the Chinese counterpart in the same change under the [bilingual pairing rules](..\u002F..\u002F..\u002Fdocs\u002FAGENTS.md), then record the pair with `pnpm run verify-translation-pairing --write docs\u002Fupgrade-guide\u002Fv\u003Cversion>\u002F\u003Citem>\u002Fguide.md`.\n\n## Verify\n\n```sh\npnpm run verify-upgrade-guides\npnpm run verify-translation-pairing docs\u002Fupgrade-guide\u002Fv\u003Cversion>\u002F\u003Citem>\u002Fguide.md\npnpm run verify-md-links\n```\n",{"name":5,"description":7},"main","a9ff3d33354e68b485f4e60904cab6a2a2e1e0cd",".agents\u002Fskills\u002Fdsh-create-upgrade-guide","https:\u002F\u002Fgithub.com\u002Fbhjia-phys\u002FAITP-agent","https:\u002F\u002Fgithub.com\u002Fbhjia-phys","Theoretical Physics","2026-11-12 04:08:49",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add bhjia-phys\u002FAITP-agent --skill dsh-create-upgrade-guide",{"tool":37,"command":38},"bunx","bunx skills add bhjia-phys\u002FAITP-agent --skill dsh-create-upgrade-guide",{"tool":40,"command":41},"pnpm","pnpm dlx skills add bhjia-phys\u002FAITP-agent --skill dsh-create-upgrade-guide","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fbhjia-phys\u002FAITP-agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fdsh-create-upgrade-guide\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M7FCT9EVBCHBH5C37QGYJ8DT","user-only-skill","Prove model-disabled skills stay outside the model catalog.","https:\u002F\u002Fgithub.com\u002Fbhjia-phys\u002FAITP-agent\u002Fblob\u002Fmain\u002Fsnapshots\u002Fsession\u002Fskill-load\u002Fworkspace\u002F.dsh\u002Fskills\u002Fuser-only-skill\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M7FCT7VN5HQCMR2GFQV5VWKB","snapshot-skill","Exercise project skill discovery and loading in snapshot tests.","https:\u002F\u002Fgithub.com\u002Fbhjia-phys\u002FAITP-agent\u002Fblob\u002Fmain\u002Fsnapshots\u002Fsession\u002Fskill-load\u002Fworkspace\u002F.dsh\u002Fskills\u002Fsnapshot-skill\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7FCT4MKQD3SYF2XT5HCB9JH","model-only-skill","Prove user-disabled skills remain available to the model.","https:\u002F\u002Fgithub.com\u002Fbhjia-phys\u002FAITP-agent\u002Fblob\u002Fmain\u002Fsnapshots\u002Fsession\u002Fskill-load\u002Fworkspace\u002F.dsh\u002Fskills\u002Fmodel-only-skill\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7FCT2CSTVNFJ84EYW3QRE2X","office","Create, edit, inspect, or convert Office documents, spreadsheets, presentations, and PDFs. Load to choose the relevant workflow.","https:\u002F\u002Fgithub.com\u002Fbhjia-phys\u002FAITP-agent\u002Fblob\u002Fmain\u002Fpackages\u002Fskill\u002Fskill-office\u002Fassets\u002Foffice\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7FCT0G68CCDKH37R96FMT2T","office-xlsx","Read, create, edit, and validate Excel workbooks, data, and formulas (.xlsx).","https:\u002F\u002Fgithub.com\u002Fbhjia-phys\u002FAITP-agent\u002Fblob\u002Fmain\u002Fpackages\u002Fskill\u002Fskill-office\u002Fassets\u002Foffice-xlsx\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7FCSWM0FK0F4ZMFNWQF75QC","office-render","Render requested document images or inspect visual layout with LibreOffice Kit.","https:\u002F\u002Fgithub.com\u002Fbhjia-phys\u002FAITP-agent\u002Fblob\u002Fmain\u002Fpackages\u002Fskill\u002Fskill-office\u002Fassets\u002Foffice-render\u002FSKILL.md",[],[]]