[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AS4SCRCA93XZVATPB0KKG4":3,"skill-same:01M7AS4SCRCA93XZVATPB0KKG4":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":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7AS4SCRCA93XZVATPB0KKG4","dsh-prose-standard",null,"Use when writing, reviewing, restoring, trimming, or auditing prose in the deepseek-harness repo, including deciding where documentation or comments are required across Markdown, JSDoc, code and test comments, prompts, descriptions, diagnostics, and CLI or UI strings.","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-prose-standard\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: dsh-prose-standard\ndescription: Use when writing, reviewing, restoring, trimming, or auditing prose in the deepseek-harness repo, including deciding where documentation or comments are required across Markdown, JSDoc, code and test comments, prompts, descriptions, diagnostics, and CLI or UI strings.\n---\n\n# DeepSeek Harness Prose Standard\n\nWrite enough to preserve the contract, then remove reasoning transcripts, repetition, and decoration. A contract is an obligation, invariant, precondition, postcondition, or compatibility promise that a caller, callee, implementer, producer, or consumer relies on. This skill owns editorial judgment and required prose coverage; use [dsh-doc-standards](..\u002Fdsh-doc-standards\u002FSKILL.md) for placement, budgets, bilingual pairs, and documentation gates, and [dsh-trim-cot-leakage](..\u002Fdsh-trim-cot-leakage\u002FSKILL.md) for hunting and fixing reasoning-transcript leakage. It is guidance, not a script.\n\nTreat `contract`, `boundary`, `shape`, `surface`, `seam`, `gate`, and `vocabulary` as terms to check before use, not banned words. First ask whether the exact rule, API, field set, type, validation, timing point, component split, or failure states the fact better. Keep a term when it names the exact technical subject, including caller\u002Fcallee contracts and security\u002Fprocess boundaries.\n\nComments describe non-obvious contracts or rationale that code cannot express; they do not restate what code already implies.\n\n## Inputs and exclusions\n\nRequire an explicit `scope`. If it is missing, report the required input and stop; do not infer a repository-wide scope or begin an interview.\n\nAccept `mode: automatic | interactive`; default to `automatic`. Enter interactive mode only when the user explicitly requests questions or calibration.\n\n`mode` controls questions, not write authority. Review and audit tasks report findings without editing; explicitly requested write, fix, or trim tasks apply clear changes.\n\nAlways exclude `vendor\u002F` from discovery, review, and edits, even when the requested scope is the whole repository. Do not follow a symlink into it. Put exclusions after inclusion globs so a later include cannot re-admit it: for example, end ripgrep commands with `--glob '!vendor\u002F**'`, and give Git commands an explicit `:(exclude)vendor\u002F**` pathspec. If the requested scope contains only `vendor\u002F`, report that no eligible files remain.\n\nAlso exclude `.agents\u002Fnotes\u002Farchived\u002F` from prose review and edits. Archived Agent Notes are frozen snapshots; inspect an exact target only to understand a historical inbound citation, never to modernize its prose or outbound links.\n\nTreat generated catalogs, snapshots, and fixtures as derivative. Edit the owning source or scenario first, then regenerate the artifact. When a generator extracts a summary from owner prose, make the extracted sentence complete for that surface. Bilingual pairs have no permanent owner: either language may be the authored side for an update. Follow the [lightweight routine path](..\u002F..\u002F..\u002Fdocs\u002FAGENTS.md#writing-rules), update the counterpart minimally, and re-record the pair.\n\n## Preserve the complete proposition\n\nBefore editing, identify every proposition in the passage. Preserve each relevant:\n\n- actor and action;\n- condition, timing, and ordering;\n- modality such as must, may, or never;\n- negative guarantee and exception;\n- ownership, side effect, failure mode, and consequence.\n\nRemove adjectives, repetition, and narration only when every factual clause survives and the result is clearer. A smaller word count alone is not an improvement.\n\nKeep a complete local contract at the point of use: behavior, failure, ownership, and consequence that a caller or maintainer needs there. Aggressively link to the owning document for architecture, rationale, algorithms, history, or extended examples. One explanation has one home; essential contract facts may repeat locally.\n\nKeep non-obvious rationale when omitting it could plausibly cause misuse or an incorrect simplification. Otherwise state the consequence and link the rationale home.\n\n## Required coverage by prose location\n\nThis is not a one-way shortening pass. Add or restore prose when code, types, and structure do not communicate a required contract below. Do not add a comment when those facts are already obvious locally.\n\n- **Public JSDoc:** document caller-visible return distinctions, throws or rejections, side effects, ownership, timing, cancellation, and durability.\n- **Internal comments:** orient non-local structure and obviously complicated local structure, including invariants, race ordering, ownership, security boundaries, and surprising failure behavior. Delete control-flow narration and code restatement.\n- **Module comments:** state the module's role, dependencies, responsibilities, and non-obvious architecture choices; link architecture choices to their owning explanation.\n- **Tests:** explain only non-obvious test design—why a fixture, assertion, platform accommodation, real entry path, or indirect observation is necessary. Delete walkthroughs and inventories.\n- **Cookbooks:** include prerequisites, required actions, the real entry path, observable verification, and concise warnings.\n- **READMEs:** include the consumer contract: configuration, semantics, failures, limitations, extension points, and model-visible effects. Quote stable model-visible text owned by the package; link generated catalogs and cross-package owners. Keep durable gaps and maintainer traps, not ordinary cleanup inventories. Follow the [package README requirements](..\u002F..\u002F..\u002Fdocs\u002Fcookbook\u002Fadding-a-package.md#4-write-the-package-readme).\n- **Agent Notes:** retain unique rationale, mechanisms, alternatives, consequences, shipped verification evidence, and named coverage gaps. Implemented Agent Notes state shipped reality in the present tense; remove planning checklists, not evidence of what pins the decision.\n- **Postmortems:** retain the incident sequence, evidence, causal chain, impact, and prevention. Remove repeated persuasion or implementation detail that does not establish causality.\n- **Skills and agent instructions:** state behavioral guardrails and explicit scope limitations such as “guidance, not a script\u002Fchecklist.” Keep the workflow concise and link its source of truth.\n- **Examples and configuration comments:** explain access limits, non-obvious wiring or load order, security stance, replay behavior, exceptions, and likely misuse. Do not narrate entries that the configuration already shows.\n- **Prompts and visible strings:** treat wording as behavior. Inspect generated output and run behavior validation or state why no snapshot applies.\n- **Diagnostics:** name the failing subject or path, violated rule, and correction when it is non-obvious. Remove internal execution narration.\n\nPreserve searchable mechanism names and meaningful modal, temporal, or negative emphasis. Normalize decorative emphasis only.\n\n## Workflow\n\n1. Confirm the scope, mode, current branch or PR base, and applicable `AGENTS.md` files. Do not inspect unrelated branches.\n2. Read [the documentation standard](..\u002F..\u002F..\u002Fdocs\u002FAGENTS.md) and the owning code or document before judging a passage. For calibration or unfamiliar cases, read [the distilled examples](references\u002Fexamples.md).\n3. Inspect the requested scope, not only the largest files. Use searches and word counts to find candidates, then judge passages semantically.\n4. Classify each candidate as keep, add, trim, restore, restructure, or defer. Apply clear changes only when the task authorizes edits; do not manufacture edits to satisfy a deletion target.\n5. Update the owner before derivative artifacts. Re-check analogous passages after learning a new rule.\n6. Run the narrow relevant checks, documentation gates, `git diff --check`, and behavior tests for visible strings. Verify the final diff contains no `vendor\u002F` path and report any accidental vendor match rather than claiming a clean exclusion history.\n7. Report the inspected scope, clear changes, deliberate keeps, deferred cases, and checks actually run.\n\n## Borderline decisions\n\nA case is borderline only when at least two versions satisfy the complete-proposition rule but trade accepted principles, and this skill does not already resolve the tradeoff. A rewrite with one proposition-preserving answer is not borderline.\n\nIn automatic mode, apply clear edits when authorized and report genuine borderline cases without asking questions. Do not weaken a proposition to make progress.\n\nIn interactive mode, group analogous passages under the governing principle. Present two or three viable versions, recommend one, and state the factual or structural difference. Do not offer inferior distractors. Use the user's requested channel; when calibrating a PR through inline comments, place the recommended provisional version in the diff and attach the alternatives to that exact line.\n\nAfter the user decides, distill the principle and versions into [the examples](references\u002Fexamples.md), without PR history or reviewer narration, and apply the learned rule to every analogous passage in scope.\n","# DeepSeek Harness Prose Standard\n\nWrite enough to preserve the contract, then remove reasoning transcripts, repetition, and decoration. A contract is an obligation, invariant, precondition, postcondition, or compatibility promise that a caller, callee, implementer, producer, or consumer relies on. This skill owns editorial judgment and required prose coverage; use [dsh-doc-standards](..\u002Fdsh-doc-standards\u002FSKILL.md) for placement, budgets, bilingual pairs, and documentation gates, and [dsh-trim-cot-leakage](..\u002Fdsh-trim-cot-leakage\u002FSKILL.md) for hunting and fixing reasoning-transcript leakage. It is guidance, not a script.\n\nTreat `contract`, `boundary`, `shape`, `surface`, `seam`, `gate`, and `vocabulary` as terms to check before use, not banned words. First ask whether the exact rule, API, field set, type, validation, timing point, component split, or failure states the fact better. Keep a term when it names the exact technical subject, including caller\u002Fcallee contracts and security\u002Fprocess boundaries.\n\nComments describe non-obvious contracts or rationale that code cannot express; they do not restate what code already implies.\n\n## Inputs and exclusions\n\nRequire an explicit `scope`. If it is missing, report the required input and stop; do not infer a repository-wide scope or begin an interview.\n\nAccept `mode: automatic | interactive`; default to `automatic`. Enter interactive mode only when the user explicitly requests questions or calibration.\n\n`mode` controls questions, not write authority. Review and audit tasks report findings without editing; explicitly requested write, fix, or trim tasks apply clear changes.\n\nAlways exclude `vendor\u002F` from discovery, review, and edits, even when the requested scope is the whole repository. Do not follow a symlink into it. Put exclusions after inclusion globs so a later include cannot re-admit it: for example, end ripgrep commands with `--glob '!vendor\u002F**'`, and give Git commands an explicit `:(exclude)vendor\u002F**` pathspec. If the requested scope contains only `vendor\u002F`, report that no eligible files remain.\n\nAlso exclude `.agents\u002Fnotes\u002Farchived\u002F` from prose review and edits. Archived Agent Notes are frozen snapshots; inspect an exact target only to understand a historical inbound citation, never to modernize its prose or outbound links.\n\nTreat generated catalogs, snapshots, and fixtures as derivative. Edit the owning source or scenario first, then regenerate the artifact. When a generator extracts a summary from owner prose, make the extracted sentence complete for that surface. Bilingual pairs have no permanent owner: either language may be the authored side for an update. Follow the [lightweight routine path](..\u002F..\u002F..\u002Fdocs\u002FAGENTS.md#writing-rules), update the counterpart minimally, and re-record the pair.\n\n## Preserve the complete proposition\n\nBefore editing, identify every proposition in the passage. Preserve each relevant:\n\n- actor and action;\n- condition, timing, and ordering;\n- modality such as must, may, or never;\n- negative guarantee and exception;\n- ownership, side effect, failure mode, and consequence.\n\nRemove adjectives, repetition, and narration only when every factual clause survives and the result is clearer. A smaller word count alone is not an improvement.\n\nKeep a complete local contract at the point of use: behavior, failure, ownership, and consequence that a caller or maintainer needs there. Aggressively link to the owning document for architecture, rationale, algorithms, history, or extended examples. One explanation has one home; essential contract facts may repeat locally.\n\nKeep non-obvious rationale when omitting it could plausibly cause misuse or an incorrect simplification. Otherwise state the consequence and link the rationale home.\n\n## Required coverage by prose location\n\nThis is not a one-way shortening pass. Add or restore prose when code, types, and structure do not communicate a required contract below. Do not add a comment when those facts are already obvious locally.\n\n- **Public JSDoc:** document caller-visible return distinctions, throws or rejections, side effects, ownership, timing, cancellation, and durability.\n- **Internal comments:** orient non-local structure and obviously complicated local structure, including invariants, race ordering, ownership, security boundaries, and surprising failure behavior. Delete control-flow narration and code restatement.\n- **Module comments:** state the module's role, dependencies, responsibilities, and non-obvious architecture choices; link architecture choices to their owning explanation.\n- **Tests:** explain only non-obvious test design—why a fixture, assertion, platform accommodation, real entry path, or indirect observation is necessary. Delete walkthroughs and inventories.\n- **Cookbooks:** include prerequisites, required actions, the real entry path, observable verification, and concise warnings.\n- **READMEs:** include the consumer contract: configuration, semantics, failures, limitations, extension points, and model-visible effects. Quote stable model-visible text owned by the package; link generated catalogs and cross-package owners. Keep durable gaps and maintainer traps, not ordinary cleanup inventories. Follow the [package README requirements](..\u002F..\u002F..\u002Fdocs\u002Fcookbook\u002Fadding-a-package.md#4-write-the-package-readme).\n- **Agent Notes:** retain unique rationale, mechanisms, alternatives, consequences, shipped verification evidence, and named coverage gaps. Implemented Agent Notes state shipped reality in the present tense; remove planning checklists, not evidence of what pins the decision.\n- **Postmortems:** retain the incident sequence, evidence, causal chain, impact, and prevention. Remove repeated persuasion or implementation detail that does not establish causality.\n- **Skills and agent instructions:** state behavioral guardrails and explicit scope limitations such as “guidance, not a script\u002Fchecklist.” Keep the workflow concise and link its source of truth.\n- **Examples and configuration comments:** explain access limits, non-obvious wiring or load order, security stance, replay behavior, exceptions, and likely misuse. Do not narrate entries that the configuration already shows.\n- **Prompts and visible strings:** treat wording as behavior. Inspect generated output and run behavior validation or state why no snapshot applies.\n- **Diagnostics:** name the failing subject or path, violated rule, and correction when it is non-obvious. Remove internal execution narration.\n\nPreserve searchable mechanism names and meaningful modal, temporal, or negative emphasis. Normalize decorative emphasis only.\n\n## Workflow\n\n1. Confirm the scope, mode, current branch or PR base, and applicable `AGENTS.md` files. Do not inspect unrelated branches.\n2. Read [the documentation standard](..\u002F..\u002F..\u002Fdocs\u002FAGENTS.md) and the owning code or document before judging a passage. For calibration or unfamiliar cases, read [the distilled examples](references\u002Fexamples.md).\n3. Inspect the requested scope, not only the largest files. Use searches and word counts to find candidates, then judge passages semantically.\n4. Classify each candidate as keep, add, trim, restore, restructure, or defer. Apply clear changes only when the task authorizes edits; do not manufacture edits to satisfy a deletion target.\n5. Update the owner before derivative artifacts. Re-check analogous passages after learning a new rule.\n6. Run the narrow relevant checks, documentation gates, `git diff --check`, and behavior tests for visible strings. Verify the final diff contains no `vendor\u002F` path and report any accidental vendor match rather than claiming a clean exclusion history.\n7. Report the inspected scope, clear changes, deliberate keeps, deferred cases, and checks actually run.\n\n## Borderline decisions\n\nA case is borderline only when at least two versions satisfy the complete-proposition rule but trade accepted principles, and this skill does not already resolve the tradeoff. A rewrite with one proposition-preserving answer is not borderline.\n\nIn automatic mode, apply clear edits when authorized and report genuine borderline cases without asking questions. Do not weaken a proposition to make progress.\n\nIn interactive mode, group analogous passages under the governing principle. Present two or three viable versions, recommend one, and state the factual or structural difference. Do not offer inferior distractors. Use the user's requested channel; when calibrating a PR through inline comments, place the recommended provisional version in the diff and attach the alternatives to that exact line.\n\nAfter the user decides, distill the principle and versions into [the examples](references\u002Fexamples.md), without PR history or reviewer narration, and apply the learned rule to every analogous passage in scope.\n",{"name":5,"description":7},"master","62087459d3d7f4149ee9a33bff63ed9ca4b6c1d8","deepseek-harness\u002F.agents\u002Fskills\u002Fdsh-prose-standard","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":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add Qiuzixiao\u002Fdeepseek-harness-desktop --skill dsh-prose-standard",{"tool":37,"command":38},"bunx","bunx skills add Qiuzixiao\u002Fdeepseek-harness-desktop --skill dsh-prose-standard",{"tool":40,"command":41},"pnpm","pnpm dlx skills add Qiuzixiao\u002Fdeepseek-harness-desktop --skill dsh-prose-standard","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FQiuzixiao\u002Fdeepseek-harness-desktop\u002Fblob\u002Fmaster\u002Fdeepseek-harness\u002F.agents\u002Fskills\u002Fdsh-prose-standard\u002FSKILL.md",true,[45,51],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"agents\u002Fopenai.yaml","REFERENCE","参考文档",241,"https:\u002F\u002Fgithub.com\u002FQiuzixiao\u002Fdeepseek-harness-desktop\u002Fblob\u002Fmaster\u002Fdeepseek-harness\u002F.agents\u002Fskills\u002Fdsh-prose-standard\u002Fagents\u002Fopenai.yaml",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002Fexamples.md",9202,"https:\u002F\u002Fgithub.com\u002FQiuzixiao\u002Fdeepseek-harness-desktop\u002Fblob\u002Fmaster\u002Fdeepseek-harness\u002F.agents\u002Fskills\u002Fdsh-prose-standard\u002Freferences\u002Fexamples.md",[56,63,70,77,84,91],{"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},"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":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},"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":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},"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":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},"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":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"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":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"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",[],[]]