[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AS4X0RQTQ3W5PRS0W54SH2":3,"skill-same:01M7AS4X0RQTQ3W5PRS0W54SH2":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":25,"commitSha":26,"skillDirectory":27,"forksCount":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":31,"install":32,"resources":44},"01M7AS4X0RQTQ3W5PRS0W54SH2","dsh-translate-docs",null,"Manually run the extended DeepSeek Harness bilingual-document workflow, including generated briefings, delegated prose translation, whole-document translation, and scoped pairing verification.","Qiuzixiao\u002Fdeepseek-harness-desktop","Qiuzixiao","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F120417469?v=4","01M7AS3GVP6K6CY963D6YR3613","Jar maker","01M7AS3GWP71XA2MZRRBM42Y41",0,"MIT","https:\u002F\u002Fgithub.com\u002FQiuzixiao\u002Fdeepseek-harness-desktop\u002Fblob\u002Fmaster\u002Fdeepseek-harness\u002F.agents\u002Fskills\u002Fdsh-translate-docs\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: dsh-translate-docs\ndescription: Manually run the extended DeepSeek Harness bilingual-document workflow, including generated briefings, delegated prose translation, whole-document translation, and scoped pairing verification.\ndisable-model-invocation: true\nuser-invocable: true\n---\n\n# Translating DeepSeek-Harness docs\n\n## Invocation boundary\n\nRun this extended workflow only when the user explicitly invokes `dsh-translate-docs` by name. Never select or load it for ordinary documentation work, from another skill, or from an inferred translation need; routine translation follows the one-shot, one-pass rule in [docs\u002FAGENTS.md](..\u002F..\u002F..\u002Fdocs\u002FAGENTS.md).\n\n## What this skill is\n\n**This skill is guidance, not a translation memory.** It is the workflow map for keeping `foo.md ↔ foo.zh.md` pairs consistent and natural in both languages. Both languages carry equal authority — a change is authored in either one, and that side is the source for that update. You are the translator: the rules below say what must hold, not how to phrase any particular sentence — phrasing judgment is yours, terminology is not.\n\n## Triage by change type — this decides everything else\n\n- **Update** (pair exists, one side edited): follow [the update path](#the-update-path-briefing-driven). It is briefing-driven and deliberately cheap: no guidance-corpus reading, no git archaeology, smallest counterpart edit. Never re-translate a whole document to apply an update — a minimal update preserves the reviewed phrasing of everything that didn't change; a re-translation throws that review away.\n- **New pair** (no counterpart yet): follow [the whole-document path](#the-whole-document-path-new-pairs).\n- **Deleted or renamed doc**: delete or rename the counterpart and the `.i18n.yaml` alongside it — the gate reports an incomplete pair otherwise.\n\nFrozen Agent Notes under `.agents\u002Fnotes\u002Farchived\u002F` are not translation work. Their complete triplets are sealed by the archive verifier; never update, re-record, or repair either side after archival.\n\n## The update path (briefing-driven)\n\nThe briefing-driven path matches guidance-corpus quality at a fraction of the cost; the [briefed-updates Agent Note](..\u002F..\u002Fnotes\u002Fimplemented\u002Fprocess\u002F2026-07-26-briefed-minimal-translation-updates.md) owns the benchmark evidence.\n\n1. **Generate the briefing**: `pnpm run gen-translation-brief \u003Cany file of the pair>` (no arguments briefs every out-of-sync pair). The briefing maps the change at the narrowest safely aligned granularity — changed Markdown units (paragraph, table row, list item, heading), then whole heading sections, then whole document — and contains the authored side's diff since the last confirmed-consistent state, each changed unit's last-confirmed source, current source, and current counterpart text (with line numbers), the terminology rows the change touches, first-occurrence movement notes, and a digest of the binding update rules.\n2. **Mechanical-only diff? `--apply` it.** When every change lies inside code fences that the pair shares byte-identically, the briefing says so; `pnpm run gen-translation-brief --apply \u003Cpair>` splices the edited fences into the counterpart and structure-validates the result before writing — no subagent, no hand-editing.\n3. **Prose diff? Delegate to a subagent, passing the briefing** (or the command to generate it). The briefing is the translator's whole working set — the subagent does not re-read the guidance corpus (the rules digest, terminology rows, and each changed unit's three-way context are inline) and does not re-derive the diff. It escalates to the whole-document path's sources of truth only when the briefing leaves a specific decision genuinely unanswerable — an unlisted term with no precedent in the surrounding text, or a whole-document briefing (`BOTH sides changed`, or neither units nor sections align), which always means reconciling by hand under [translation-rules.md](..\u002F..\u002F..\u002Fdocs\u002Fi18n\u002Ftranslation-rules.md).\n4. **Smallest edit that covers the diff.** Preserve the reviewed phrasing of everything the diff does not touch, then verify the changed hunks clause by clause against the source: nothing added, nothing dropped, terminology per the inline rows, code spans verbatim.\n5. **Record and verify, scoped**: `pnpm run verify-translation-pairing --write \u003Cpair>` then `pnpm run verify-translation-pairing \u003Cpair>`. `--write` names exactly the pairs you confirmed — it refuses to run bare so a bulk re-record is always an explicit `--all`. The corpus-wide check still runs in `doc-sync`\u002FCI; do not run it per-update.\n\n## The whole-document path (new pairs)\n\nWhen translations need to be written from scratch, the orchestrating agent does not translate: spawn a subagent to do the translation work. The translator reads the sources of truth below first, then translates the whole file into the other language — section by section for long documents, keeping each section's structure locked to the source as you go rather than fixing structure at the end.\n\n### Sources of truth (read, don't re-summarize)\n\n- **[docs\u002Fi18n\u002FREADME.md](..\u002F..\u002F..\u002Fdocs\u002Fi18n\u002FREADME.md)** — the pairing contract: the three-file pair (`foo.md`, `foo.zh.md`, `foo.i18n.yaml`), the consistency record's both-side blob hashes, the language-switcher lines, scope, and exclusions.\n- **[docs\u002Fi18n\u002Ftranslation-rules.md](..\u002F..\u002F..\u002Fdocs\u002Fi18n\u002Ftranslation-rules.md)** — how to translate: faithfulness, structure preservation, terminology discipline, typography (MUST\u002FSHOULD levels).\n- **[docs\u002Fi18n\u002Fterminology.md](..\u002F..\u002F..\u002Fdocs\u002Fi18n\u002Fterminology.md)** — the terminology table, binding in both directions. Load it BEFORE translating, not when a term feels uncertain; the terms you don't notice are the ones that drift.\n- **[docs\u002Fi18n\u002Ftranslation-prompt.md](..\u002F..\u002F..\u002Fdocs\u002Fi18n\u002Ftranslation-prompt.md)** — the automated pipeline's calibrated machine-consumed template. Agents using this skill do not render it; the terminology table is the only repository file the automated renderer injects, while this skill and `translation-rules.md` remain binding for agent-authored translations.\n- **[dsh-prose-standard](..\u002Fdsh-prose-standard\u002FSKILL.md)** — required prose coverage and editorial judgment. Apply it to both sides without adding or dropping source propositions.\n\n### Translate\n\n- **Pass 1 — write, don't transpose.** Read a semantic unit, then restate it as a native technical author in the nearest [style sample's](..\u002F..\u002F..\u002Fdocs\u002Fi18n\u002Fstyle-samples.md) register. Preserve the required frame without forcing sentence-by-sentence correspondence.\n- **Pass 2 — verify against the source, clause by clause.** Fidelity is checked here, not written in: confirm nothing was added or dropped, every term follows the table, and each code span survived verbatim. Fix by rewriting the sentence natively, not by patching words into it.\n- **Read the completed counterpart alone.** After the source comparison, read the translated file without the source beside it and rewrite phrasing whose awkwardness only becomes visible in isolation.\n- Write only the final text to the file, never drafts or notes.\n- Every term in [terminology.md](..\u002F..\u002F..\u002Fdocs\u002Fi18n\u002Fterminology.md) renders exactly as specified. For a Chinese target, use the Chinese and first-occurrence columns; an unlisted term needs a citable Chinese OSS\u002Fvendor precedent or stays English under 「待定术语」. For an English target, use the English column and an established English technical term; preserve an ambiguous source term with a short gloss and list it as pending. Never invent a rendering inline.\n- Code blocks are byte-identical across the pair, comments included. Relative links keep their `.md` targets; only the switcher line links `.zh.md`.\n- The pairing gate checks heading depths, fenced blocks, table row and column counts, list kinds, ordered-list starts, list item counts, and link targets. In Pass 2, manually verify list and table order, noncanonical list numbering, inline code, emphasis, meaning, terminology, and tone.\n\n## Find the work\n\n- `pnpm run verify-translation-pairing --list` prints every in-scope document as missing \u002F out-of-sync \u002F ok. Missing and out-of-sync rows are contract violations; the normal check rejects them.\n- `pnpm run gen-translation-brief` with no arguments prints the briefing for every out-of-sync pair.\n- In a PR that edits paired docs, the work list is the diff itself: every changed side of a pair needs its counterpart updated and the pair re-recorded in the same PR, and the gate goes red if you forget.\n\n## Finish the pair\n\n1. Switcher: `[English](foo.md) | 中文` immediately after the Chinese file's H1, `English | [中文](foo.zh.md)` after the English file's H1 — add both if this is a new pair, except that a generator-owned English source stays byte-identical to generator output and omits its switcher while the Chinese counterpart still links back.\n2. Record consistency: `pnpm run verify-translation-pairing --write \u003Cpair>` recomputes and records both sides' full blob hashes in `foo.i18n.yaml`. The yaml diff in your PR is the reviewable statement \"I confirmed these two say the same thing\" — only run it after you actually have.\n3. No manifest entry is needed for an ordinary document: every in-scope source requires a pair. Change [scripts\u002Ftranslation-pairing.manifest.json](..\u002F..\u002F..\u002Fscripts\u002Ftranslation-pairing.manifest.json) only when the owning policy documents a genuine generated, instructional, or bilingual-by-construction exclusion.\n4. Before the PR: the touched pairs are green under the scoped check; `pnpm run doc-sync` (which includes the corpus-wide pairing check plus `verify-md-wrap`\u002F`verify-md-links`) runs once at PR level per [dsh-pre-push-checks](..\u002Fdsh-pre-push-checks\u002FSKILL.md), not inside each translation task.\n5. Keep the PR reviewable: state which pairs are new versus minimally updated and list 「待定术语」 prominently.\n\n## How to respond to translation review\n\nFollow the [code-review reporting guidance](..\u002Fdsh-code-review\u002FSKILL.md#reporting-findings): evaluate each comment on its merits, and for terminology comments, remember the terminology table is the contract — apply a reviewer's rendering decision to [terminology.md](..\u002F..\u002F..\u002Fdocs\u002Fi18n\u002Fterminology.md), not only to one file.\n","# Translating DeepSeek-Harness docs\n\n## Invocation boundary\n\nRun this extended workflow only when the user explicitly invokes `dsh-translate-docs` by name. Never select or load it for ordinary documentation work, from another skill, or from an inferred translation need; routine translation follows the one-shot, one-pass rule in [docs\u002FAGENTS.md](..\u002F..\u002F..\u002Fdocs\u002FAGENTS.md).\n\n## What this skill is\n\n**This skill is guidance, not a translation memory.** It is the workflow map for keeping `foo.md ↔ foo.zh.md` pairs consistent and natural in both languages. Both languages carry equal authority — a change is authored in either one, and that side is the source for that update. You are the translator: the rules below say what must hold, not how to phrase any particular sentence — phrasing judgment is yours, terminology is not.\n\n## Triage by change type — this decides everything else\n\n- **Update** (pair exists, one side edited): follow [the update path](#the-update-path-briefing-driven). It is briefing-driven and deliberately cheap: no guidance-corpus reading, no git archaeology, smallest counterpart edit. Never re-translate a whole document to apply an update — a minimal update preserves the reviewed phrasing of everything that didn't change; a re-translation throws that review away.\n- **New pair** (no counterpart yet): follow [the whole-document path](#the-whole-document-path-new-pairs).\n- **Deleted or renamed doc**: delete or rename the counterpart and the `.i18n.yaml` alongside it — the gate reports an incomplete pair otherwise.\n\nFrozen Agent Notes under `.agents\u002Fnotes\u002Farchived\u002F` are not translation work. Their complete triplets are sealed by the archive verifier; never update, re-record, or repair either side after archival.\n\n## The update path (briefing-driven)\n\nThe briefing-driven path matches guidance-corpus quality at a fraction of the cost; the [briefed-updates Agent Note](..\u002F..\u002Fnotes\u002Fimplemented\u002Fprocess\u002F2026-07-26-briefed-minimal-translation-updates.md) owns the benchmark evidence.\n\n1. **Generate the briefing**: `pnpm run gen-translation-brief \u003Cany file of the pair>` (no arguments briefs every out-of-sync pair). The briefing maps the change at the narrowest safely aligned granularity — changed Markdown units (paragraph, table row, list item, heading), then whole heading sections, then whole document — and contains the authored side's diff since the last confirmed-consistent state, each changed unit's last-confirmed source, current source, and current counterpart text (with line numbers), the terminology rows the change touches, first-occurrence movement notes, and a digest of the binding update rules.\n2. **Mechanical-only diff? `--apply` it.** When every change lies inside code fences that the pair shares byte-identically, the briefing says so; `pnpm run gen-translation-brief --apply \u003Cpair>` splices the edited fences into the counterpart and structure-validates the result before writing — no subagent, no hand-editing.\n3. **Prose diff? Delegate to a subagent, passing the briefing** (or the command to generate it). The briefing is the translator's whole working set — the subagent does not re-read the guidance corpus (the rules digest, terminology rows, and each changed unit's three-way context are inline) and does not re-derive the diff. It escalates to the whole-document path's sources of truth only when the briefing leaves a specific decision genuinely unanswerable — an unlisted term with no precedent in the surrounding text, or a whole-document briefing (`BOTH sides changed`, or neither units nor sections align), which always means reconciling by hand under [translation-rules.md](..\u002F..\u002F..\u002Fdocs\u002Fi18n\u002Ftranslation-rules.md).\n4. **Smallest edit that covers the diff.** Preserve the reviewed phrasing of everything the diff does not touch, then verify the changed hunks clause by clause against the source: nothing added, nothing dropped, terminology per the inline rows, code spans verbatim.\n5. **Record and verify, scoped**: `pnpm run verify-translation-pairing --write \u003Cpair>` then `pnpm run verify-translation-pairing \u003Cpair>`. `--write` names exactly the pairs you confirmed — it refuses to run bare so a bulk re-record is always an explicit `--all`. The corpus-wide check still runs in `doc-sync`\u002FCI; do not run it per-update.\n\n## The whole-document path (new pairs)\n\nWhen translations need to be written from scratch, the orchestrating agent does not translate: spawn a subagent to do the translation work. The translator reads the sources of truth below first, then translates the whole file into the other language — section by section for long documents, keeping each section's structure locked to the source as you go rather than fixing structure at the end.\n\n### Sources of truth (read, don't re-summarize)\n\n- **[docs\u002Fi18n\u002FREADME.md](..\u002F..\u002F..\u002Fdocs\u002Fi18n\u002FREADME.md)** — the pairing contract: the three-file pair (`foo.md`, `foo.zh.md`, `foo.i18n.yaml`), the consistency record's both-side blob hashes, the language-switcher lines, scope, and exclusions.\n- **[docs\u002Fi18n\u002Ftranslation-rules.md](..\u002F..\u002F..\u002Fdocs\u002Fi18n\u002Ftranslation-rules.md)** — how to translate: faithfulness, structure preservation, terminology discipline, typography (MUST\u002FSHOULD levels).\n- **[docs\u002Fi18n\u002Fterminology.md](..\u002F..\u002F..\u002Fdocs\u002Fi18n\u002Fterminology.md)** — the terminology table, binding in both directions. Load it BEFORE translating, not when a term feels uncertain; the terms you don't notice are the ones that drift.\n- **[docs\u002Fi18n\u002Ftranslation-prompt.md](..\u002F..\u002F..\u002Fdocs\u002Fi18n\u002Ftranslation-prompt.md)** — the automated pipeline's calibrated machine-consumed template. Agents using this skill do not render it; the terminology table is the only repository file the automated renderer injects, while this skill and `translation-rules.md` remain binding for agent-authored translations.\n- **[dsh-prose-standard](..\u002Fdsh-prose-standard\u002FSKILL.md)** — required prose coverage and editorial judgment. Apply it to both sides without adding or dropping source propositions.\n\n### Translate\n\n- **Pass 1 — write, don't transpose.** Read a semantic unit, then restate it as a native technical author in the nearest [style sample's](..\u002F..\u002F..\u002Fdocs\u002Fi18n\u002Fstyle-samples.md) register. Preserve the required frame without forcing sentence-by-sentence correspondence.\n- **Pass 2 — verify against the source, clause by clause.** Fidelity is checked here, not written in: confirm nothing was added or dropped, every term follows the table, and each code span survived verbatim. Fix by rewriting the sentence natively, not by patching words into it.\n- **Read the completed counterpart alone.** After the source comparison, read the translated file without the source beside it and rewrite phrasing whose awkwardness only becomes visible in isolation.\n- Write only the final text to the file, never drafts or notes.\n- Every term in [terminology.md](..\u002F..\u002F..\u002Fdocs\u002Fi18n\u002Fterminology.md) renders exactly as specified. For a Chinese target, use the Chinese and first-occurrence columns; an unlisted term needs a citable Chinese OSS\u002Fvendor precedent or stays English under 「待定术语」. For an English target, use the English column and an established English technical term; preserve an ambiguous source term with a short gloss and list it as pending. Never invent a rendering inline.\n- Code blocks are byte-identical across the pair, comments included. Relative links keep their `.md` targets; only the switcher line links `.zh.md`.\n- The pairing gate checks heading depths, fenced blocks, table row and column counts, list kinds, ordered-list starts, list item counts, and link targets. In Pass 2, manually verify list and table order, noncanonical list numbering, inline code, emphasis, meaning, terminology, and tone.\n\n## Find the work\n\n- `pnpm run verify-translation-pairing --list` prints every in-scope document as missing \u002F out-of-sync \u002F ok. Missing and out-of-sync rows are contract violations; the normal check rejects them.\n- `pnpm run gen-translation-brief` with no arguments prints the briefing for every out-of-sync pair.\n- In a PR that edits paired docs, the work list is the diff itself: every changed side of a pair needs its counterpart updated and the pair re-recorded in the same PR, and the gate goes red if you forget.\n\n## Finish the pair\n\n1. Switcher: `[English](foo.md) | 中文` immediately after the Chinese file's H1, `English | [中文](foo.zh.md)` after the English file's H1 — add both if this is a new pair, except that a generator-owned English source stays byte-identical to generator output and omits its switcher while the Chinese counterpart still links back.\n2. Record consistency: `pnpm run verify-translation-pairing --write \u003Cpair>` recomputes and records both sides' full blob hashes in `foo.i18n.yaml`. The yaml diff in your PR is the reviewable statement \"I confirmed these two say the same thing\" — only run it after you actually have.\n3. No manifest entry is needed for an ordinary document: every in-scope source requires a pair. Change [scripts\u002Ftranslation-pairing.manifest.json](..\u002F..\u002F..\u002Fscripts\u002Ftranslation-pairing.manifest.json) only when the owning policy documents a genuine generated, instructional, or bilingual-by-construction exclusion.\n4. Before the PR: the touched pairs are green under the scoped check; `pnpm run doc-sync` (which includes the corpus-wide pairing check plus `verify-md-wrap`\u002F`verify-md-links`) runs once at PR level per [dsh-pre-push-checks](..\u002Fdsh-pre-push-checks\u002FSKILL.md), not inside each translation task.\n5. Keep the PR reviewable: state which pairs are new versus minimally updated and list 「待定术语」 prominently.\n\n## How to respond to translation review\n\nFollow the [code-review reporting guidance](..\u002Fdsh-code-review\u002FSKILL.md#reporting-findings): evaluate each comment on its merits, and for terminology comments, remember the terminology table is the contract — apply a reviewer's rendering decision to [terminology.md](..\u002F..\u002F..\u002Fdocs\u002Fi18n\u002Fterminology.md), not only to one file.\n",{"name":5,"description":7,"user-invocable":24,"disable-model-invocation":24},true,"master","62087459d3d7f4149ee9a33bff63ed9ca4b6c1d8","deepseek-harness\u002F.agents\u002Fskills\u002Fdsh-translate-docs","https:\u002F\u002Fgithub.com\u002FQiuzixiao\u002Fdeepseek-harness-desktop","https:\u002F\u002Fdshdesktop.cn","https:\u002F\u002Fgithub.com\u002FQiuzixiao","2026-09-10 18:31:27",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":24},[34,37,40],{"tool":35,"command":36},"npx","npx skills add Qiuzixiao\u002Fdeepseek-harness-desktop --skill dsh-translate-docs",{"tool":38,"command":39},"bunx","bunx skills add Qiuzixiao\u002Fdeepseek-harness-desktop --skill dsh-translate-docs",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Qiuzixiao\u002Fdeepseek-harness-desktop --skill dsh-translate-docs","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FQiuzixiao\u002Fdeepseek-harness-desktop\u002Fblob\u002Fmaster\u002Fdeepseek-harness\u002F.agents\u002Fskills\u002Fdsh-translate-docs\u002FSKILL.md",[45],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"agents\u002Fopenai.yaml","REFERENCE","参考文档",296,"https:\u002F\u002Fgithub.com\u002FQiuzixiao\u002Fdeepseek-harness-desktop\u002Fblob\u002Fmaster\u002Fdeepseek-harness\u002F.agents\u002Fskills\u002Fdsh-translate-docs\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},"01M7AS86XE0PJQ0MCDH5DPZCFC","short-drama-domain","Short-drama project object map and task routing. Use when the user works with screenplay artifacts, episode scenes, continuity, diagnosis, revision, or delivery. This skill provides operational vocabulary and questions, not a mandatory writing style.","https:\u002F\u002Fgithub.com\u002FQiuzixiao\u002Fdeepseek-harness-desktop\u002Fblob\u002Fmaster\u002Fdsh-short-drama\u002Fmanaged-presets\u002Fscreenplay-v1\u002Fskills\u002Fshort-drama-domain\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},"01M7AS837QRW3BDY2W6PHXB2AB","creative-project-organization","从梗概开始创作、生成设定\u002F人物\u002F大纲\u002F正文等文件时，在首批落盘前规划内容分组和保存位置；新增独立交付物时复核布局。自动适配项目语言和命名习惯，也用于用户要求的项目整理。无需用户提出归档要求。","https:\u002F\u002Fgithub.com\u002FQiuzixiao\u002Fdeepseek-harness-desktop\u002Fblob\u002Fmaster\u002Fdsh-short-drama\u002Fmanaged-presets\u002Fscreenplay-v1\u002Fskills\u002Fcreative-project-organization\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},"01M7AS7YHQTH0H79BZGANZF6V5","skill-sink","技能沉淀机制：把创作中验证有效的经验、方法论与个人文风，提炼成可复用的 DSH skill。当创作中发现可复用经验、用户要沉淀个人文风、或要把反复出现的规则固化成技能时使用。","https:\u002F\u002Fgithub.com\u002FQiuzixiao\u002Fdeepseek-harness-desktop\u002Fblob\u002Fmaster\u002Fdsh-plugin-desktop\u002Fresources\u002Fagent-presets\u002Fshort-drama\u002Fskills\u002Fskill-sink\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},"01M7AS7S0NS2PQVSNFQFRES3PW","short-drama-zonggang","短剧创作总纲与情绪账务引擎方法论。以「恨账—存债\u002F付息\u002F兑付」债务系统为内核，覆盖选题、故事骨架、压爽循环与卡点、付费闸门、台词正文格式、验收自检与失效模式库。当用户要创作短剧剧本、立项选题、写分集大纲、写正文台词、设计付费卡点，或评审\u002F修改\u002F验收短剧时，先加载本 Skill。","https:\u002F\u002Fgithub.com\u002FQiuzixiao\u002Fdeepseek-harness-desktop\u002Fblob\u002Fmaster\u002Fdsh-plugin-desktop\u002Fresources\u002Fagent-presets\u002Fshort-drama\u002Fskills\u002Fshort-drama-zonggang\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},"01M7AS7KHM1F0V7HM33VDGAEQG","short-drama-structure","把已确认的故事前提排成短剧四幕二十拍、分集节奏和场次骨架（4×5 节拍表、卡点与高潮兑现）。当用户已有故事梗概，要求拆成四幕\u002F20 拍\u002F分集\u002F场次表、中段松散需要重排转折，或想设置悬念、反转、付费卡点及高潮兑现路径时使用。不适用于从零提炼创意、单场对白润色或平台投稿咨询。","https:\u002F\u002Fgithub.com\u002FQiuzixiao\u002Fdeepseek-harness-desktop\u002Fblob\u002Fmaster\u002Fdsh-plugin-desktop\u002Fresources\u002Fagent-presets\u002Fshort-drama\u002Fskills\u002Fshort-drama-structure\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},"01M7AS7EEA9D20P4R5BBSPNBCN","short-drama-scene","当用户提供剧本片段、分场或对白，要求更可拍\u002F更有戏\u002F减少解释\u002F改得口语化时调用；重点处理单场冲突、动作进出、状态变化、信息差、潜台词和对白瘦身。不适用于从零搭故事结构、设计整部剧的悬念卡点或行业投稿咨询。","https:\u002F\u002Fgithub.com\u002FQiuzixiao\u002Fdeepseek-harness-desktop\u002Fblob\u002Fmaster\u002Fdsh-plugin-desktop\u002Fresources\u002Fagent-presets\u002Fshort-drama\u002Fskills\u002Fshort-drama-scene\u002FSKILL.md",[],[]]