[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F2DMJMCGDZEAKZG919F4EF":3,"skill-same:01M7F2DMJMCGDZEAKZG919F4EF":47},{"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":28,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7F2DMJMCGDZEAKZG919F4EF","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.","OJamals\u002Ffi","OJamals","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F190230429?v=4","01M7F28NRDVKV848GX2433PSBH","A. Omar Aljamal, MD","01M7F28NS029WSHBC32Z79PD0F",3,"MIT","https:\u002F\u002Fgithub.com\u002FOJamals\u002Ffi\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","da5a0c7ce142dc4c02297a9c40f7f9483d70c0cd",".agents\u002Fskills\u002Fdsh-create-upgrade-guide",1,"https:\u002F\u002Fgithub.com\u002FOJamals\u002Ffi","https:\u002F\u002Fgithub.com\u002FOJamals","https:\u002F\u002Faljamal.work","Internist & hospitalist. Clinical AI that has to earn its answers: evaluation, safety and clinical NLP.","2026-11-15 06:18:36",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add OJamals\u002Ffi --skill dsh-create-upgrade-guide",{"tool":39,"command":40},"bunx","bunx skills add OJamals\u002Ffi --skill dsh-create-upgrade-guide",{"tool":42,"command":43},"pnpm","pnpm dlx skills add OJamals\u002Ffi --skill dsh-create-upgrade-guide","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FOJamals\u002Ffi\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fdsh-create-upgrade-guide\u002FSKILL.md",true,[],[48,55,62,69,76,83],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7F2H65DRC9H6YBX2X9AY3W7","user-only-skill","Prove model-disabled skills stay outside the model catalog.","https:\u002F\u002Fgithub.com\u002FOJamals\u002Ffi\u002Fblob\u002Fmain\u002Fsnapshots\u002Fsession\u002Fskill-load\u002Fworkspace\u002F.dsh\u002Fskills\u002Fuser-only-skill\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7F2GSX6RCFK12GS7GSY3B6Q","snapshot-skill","Exercise project skill discovery and loading in snapshot tests.","https:\u002F\u002Fgithub.com\u002FOJamals\u002Ffi\u002Fblob\u002Fmain\u002Fsnapshots\u002Fsession\u002Fskill-load\u002Fworkspace\u002F.dsh\u002Fskills\u002Fsnapshot-skill\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"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},"01M7F2G84RNW56KS4VCGPV7NGX","model-only-skill","Prove user-disabled skills remain available to the model.","https:\u002F\u002Fgithub.com\u002FOJamals\u002Ffi\u002Fblob\u002Fmain\u002Fsnapshots\u002Fsession\u002Fskill-load\u002Fworkspace\u002F.dsh\u002Fskills\u002Fmodel-only-skill\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},"01M7F2G3QBJB748G8C6M3BWA1P","office-xlsx","Read, create, and modify Excel workbooks (.xlsx), including data, formulas, formatting, and pandas analysis. Use for Excel inputs or deliverables. Load before running Office commands. Data and formula tasks skip visual inspection; inspect only for formatting or layout needs. Use only bundled LibreOffice unless the user explicitly opts out; without that opt-out, do not search for another LibreOffice executable.","https:\u002F\u002Fgithub.com\u002FOJamals\u002Ffi\u002Fblob\u002Fmain\u002Fpackages\u002Fskill\u002Fskill-office\u002Fassets\u002Foffice-xlsx\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},"01M7F2FZTBV428N1FJDJSSEHTA","office-pptx","Create, read, edit, and check PowerPoint presentations (.pptx), including slide text, tables, images, and charts. Use when a PPTX file is an input or requested deliverable. Load this skill before running Office commands. Use only bundled LibreOffice unless the user explicitly opts out; without that opt-out, do not search for another LibreOffice executable.","https:\u002F\u002Fgithub.com\u002FOJamals\u002Ffi\u002Fblob\u002Fmain\u002Fpackages\u002Fskill\u002Fskill-office\u002Fassets\u002Foffice-pptx\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},"01M7F2FW8DGQ1RF3QASTXGZSNK","office-docx","Create, read, edit, and check Word documents (.docx), including reports, letters, and formatted tables. Use when a DOCX file is an input or requested deliverable. Load this skill before running Office commands. Use only bundled LibreOffice unless the user explicitly opts out; without that opt-out, do not search for another LibreOffice executable.","https:\u002F\u002Fgithub.com\u002FOJamals\u002Ffi\u002Fblob\u002Fmain\u002Fpackages\u002Fskill\u002Fskill-office\u002Fassets\u002Foffice-docx\u002FSKILL.md",[],[]]