[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6M2JMPNDCB1YF1Z2MPEFNNG":3,"skill-same:01M6M2JMPNDCB1YF1Z2MPEFNNG":73},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":40,"linkOnly":41,"markdownContent":42,"markdownBody":43,"frontMatter":44,"refName":54,"commitSha":55,"skillDirectory":56,"forksCount":13,"repositoryHtmlUrl":57,"repositoryHomepageUrl":6,"ownerHtmlUrl":58,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":59,"install":60,"resources":72},"01M6M2JMPNDCB1YF1Z2MPEFNNG","seedance-continuation",null,"This skill should be used when a Seedance 2.0 user asks to continue, extend, make the next part, repair the tail, bridge between known frames, re-anchor drift, or create a successor prompt from accepted footage.","endman100\u002Fskill-router-nexus","endman100","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F31997019?v=4","01M6KPDX17BYDWW4RRB0TNGGMX","01M6KPDX64Y2QBEWVFG5W5PWPF",0,"MIT","https:\u002F\u002Fgithub.com\u002Fendman100\u002Fskill-router-nexus\u002Fblob\u002Fmain\u002FVideo-Generation\u002Fseedance-20\u002Fskills\u002Fseedance-continuation\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39],"seedance continuation","seedance","anchor","2026","when","extend","continuation","seedance-20","true","tail","re","github","repair","continuity","next","drift","bridge","user","prompt","continue","https","create","2026-11-10 10:12:30",false,"---\nname: seedance-continuation\ndescription: \"This skill should be used when a Seedance 2.0 user asks to continue, extend, make the next part, repair the tail, bridge between known frames, re-anchor drift, or create a successor prompt from accepted footage.\"\nlicense: MIT\nuser-invocable: true\ntags:\n  - continuation\n  - extend\n  - continuity\n  - seedance-20\nmetadata:\n  version: \"6.6.0\"\n  updated: \"2026-07-04\"\n  parent: \"seedance-20\"\n  author: \"Iamemily2050 (@iamemily2050)\"\n  repository: \"https:\u002F\u002Fgithub.com\u002FEmily2040\u002Fseedance-2.0\"\n  openclaw:\n    emoji: \"?\"\n    homepage: \"https:\u002F\u002Fgithub.com\u002FEmily2040\u002Fseedance-2.0\"\n---\n\n# seedance-continuation\n\nUse this for seamless continuation, intentional next shots, bridge clips, tail repair, and re-anchoring after drift. A continuation prompt must be grounded in accepted footage, not only in the old plan.\n\nLoad `[ref:continuation-handoff]`, `[ref:sequence-project-state]`, `[ref:prompt-compiler]`, `[ref:reference-transfer-contract]`, and `[ref:continuity-qc]`. Load `[ref:failure-atlas]` when the continuation failed or drift is visible. Load `[ref:directing-engine]` so the next clip inherits the project's directorial voice and its position on the long-form spine; the look never re-rolls between clips.\n\n## Intent\n\nThe user already made something they accepted, and now they are trusting the story to continue from exactly where it really landed - not where the plan hoped it would. The soul of this skill is fidelity to what actually happened: honor the accepted footage as the only truth, refuse to invent the bridge, and ask for the real ending rather than guess it. Continuity is a promise that the film the user already has will not be quietly contradicted.\n\n## Required Input Gate\n\nBefore writing any continuation prompt, require:\n\n- `project_id`;\n- current `clip_id`;\n- valid `parent_clip_id`;\n- `scene_id`, and whether the next clip stays inside the scene or crosses a scene boundary;\n- full-story objective;\n- final story outcome;\n- next planned narrative job;\n- next clip `felt_intent` - what the viewer should feel or notice;\n- accepted previous clip or accepted final frame;\n- `observed_end_state`;\n- continuity locks;\n- inherited directorial voice and arc position;\n- exact reference registry;\n- active surface or conservative surface profile.\n\nIf the source is unavailable, say: \"I have the story plan, but I do not have the actual ending of the previous generation. Upload the clip or its final frame - `python scripts\u002Fextract_last_frame.py \u003Ctake>` pulls the final frame locally - or describe exactly what is visible at the end. I should not invent the continuation state.\"\n\nOnce a frame or clip is attached, run the Observation Fast Path from `[ref:continuation-handoff]`: the agent fills the observation record from what is visible and asks only about what the attachment cannot show (for a still: open motion, camera movement phase, audio phase). Never hand the sensing work back to the user when the pixels are already in hand.\n\nDo not hide this uncertainty by writing a speculative prompt.\n\n## Continuation Types\n\n`seamless_continuation`: same shot, same geography, same open motion, same or motivated camera continuation, and accepted previous footage as the source.\n\n`intentional_next_shot`: an editorial cut is appropriate. Story continuity matters, but exact frame continuity is not promised. Do not call it seamless.\n\n`bridge_between_known_states`: a defined start state and end state must be connected, often with first\u002Flast-frame generation when the active surface supports it.\n\n`repair_tail`: the previous final seconds failed. Repair, edit, or regenerate the tail before continuing because continuing from a failed tail amplifies the error.\n\n`reanchor_after_drift`: identity, detail, geography, motion, audio, or world continuity degraded. Return to canonical identity, the strongest accepted final frame, a stable source clip, or a new intentional shot using canonical references.\n\n## Scene Boundary Rule\n\nCrossing a scene boundary defaults to `intentional_next_shot` opening from canonical references. Do not promise `seamless_continuation` across a scene boundary; if the user explicitly asks for one, record the reason and treat the result as high drift risk.\n\n## Canon Rule\n\nAccepted observed footage overrides planned state. If the plan says the subject reached the car door but the accepted clip ends two steps away, the next prompt begins two steps away. It does not replay the terminal exit, and it does not assume the subject is inside the car.\n\nRejected footage never updates canon and never becomes a parent source.\n\nTrack `extension_depth` as consecutive output-sourced generations since the last canonical re-anchor; it resets to 0 when a clip opens from canonical references. At the scene's `max_chain_depth` (default 2, hard ceiling 3), re-anchor by schedule instead of extending again. Visible drift before the cap is an immediate `reanchor_after_drift`.\n\n## Output Contract\n\nReturn:\n\n1. Continuation type.\n2. Source evidence used.\n3. Observed end state.\n4. Next clip contract.\n5. Intent echo: one line - \"this clip exists so the viewer feels X\" - confirmed before generation spends money.\n6. Continuity locks and allowed changes.\n7. Completed beats to exclude.\n8. Reserved future beats to exclude.\n9. Final natural-language Seedance prompt for the current clip only.\n10. Updated Project State Capsule or a request for missing source evidence.\n","# seedance-continuation\n\nUse this for seamless continuation, intentional next shots, bridge clips, tail repair, and re-anchoring after drift. A continuation prompt must be grounded in accepted footage, not only in the old plan.\n\nLoad `[ref:continuation-handoff]`, `[ref:sequence-project-state]`, `[ref:prompt-compiler]`, `[ref:reference-transfer-contract]`, and `[ref:continuity-qc]`. Load `[ref:failure-atlas]` when the continuation failed or drift is visible. Load `[ref:directing-engine]` so the next clip inherits the project's directorial voice and its position on the long-form spine; the look never re-rolls between clips.\n\n## Intent\n\nThe user already made something they accepted, and now they are trusting the story to continue from exactly where it really landed - not where the plan hoped it would. The soul of this skill is fidelity to what actually happened: honor the accepted footage as the only truth, refuse to invent the bridge, and ask for the real ending rather than guess it. Continuity is a promise that the film the user already has will not be quietly contradicted.\n\n## Required Input Gate\n\nBefore writing any continuation prompt, require:\n\n- `project_id`;\n- current `clip_id`;\n- valid `parent_clip_id`;\n- `scene_id`, and whether the next clip stays inside the scene or crosses a scene boundary;\n- full-story objective;\n- final story outcome;\n- next planned narrative job;\n- next clip `felt_intent` - what the viewer should feel or notice;\n- accepted previous clip or accepted final frame;\n- `observed_end_state`;\n- continuity locks;\n- inherited directorial voice and arc position;\n- exact reference registry;\n- active surface or conservative surface profile.\n\nIf the source is unavailable, say: \"I have the story plan, but I do not have the actual ending of the previous generation. Upload the clip or its final frame - `python scripts\u002Fextract_last_frame.py \u003Ctake>` pulls the final frame locally - or describe exactly what is visible at the end. I should not invent the continuation state.\"\n\nOnce a frame or clip is attached, run the Observation Fast Path from `[ref:continuation-handoff]`: the agent fills the observation record from what is visible and asks only about what the attachment cannot show (for a still: open motion, camera movement phase, audio phase). Never hand the sensing work back to the user when the pixels are already in hand.\n\nDo not hide this uncertainty by writing a speculative prompt.\n\n## Continuation Types\n\n`seamless_continuation`: same shot, same geography, same open motion, same or motivated camera continuation, and accepted previous footage as the source.\n\n`intentional_next_shot`: an editorial cut is appropriate. Story continuity matters, but exact frame continuity is not promised. Do not call it seamless.\n\n`bridge_between_known_states`: a defined start state and end state must be connected, often with first\u002Flast-frame generation when the active surface supports it.\n\n`repair_tail`: the previous final seconds failed. Repair, edit, or regenerate the tail before continuing because continuing from a failed tail amplifies the error.\n\n`reanchor_after_drift`: identity, detail, geography, motion, audio, or world continuity degraded. Return to canonical identity, the strongest accepted final frame, a stable source clip, or a new intentional shot using canonical references.\n\n## Scene Boundary Rule\n\nCrossing a scene boundary defaults to `intentional_next_shot` opening from canonical references. Do not promise `seamless_continuation` across a scene boundary; if the user explicitly asks for one, record the reason and treat the result as high drift risk.\n\n## Canon Rule\n\nAccepted observed footage overrides planned state. If the plan says the subject reached the car door but the accepted clip ends two steps away, the next prompt begins two steps away. It does not replay the terminal exit, and it does not assume the subject is inside the car.\n\nRejected footage never updates canon and never becomes a parent source.\n\nTrack `extension_depth` as consecutive output-sourced generations since the last canonical re-anchor; it resets to 0 when a clip opens from canonical references. At the scene's `max_chain_depth` (default 2, hard ceiling 3), re-anchor by schedule instead of extending again. Visible drift before the cap is an immediate `reanchor_after_drift`.\n\n## Output Contract\n\nReturn:\n\n1. Continuation type.\n2. Source evidence used.\n3. Observed end state.\n4. Next clip contract.\n5. Intent echo: one line - \"this clip exists so the viewer feels X\" - confirmed before generation spends money.\n6. Continuity locks and allowed changes.\n7. Completed beats to exclude.\n8. Reserved future beats to exclude.\n9. Final natural-language Seedance prompt for the current clip only.\n10. Updated Project State Capsule or a request for missing source evidence.\n",{"name":5,"tags":45,"license":14,"metadata":46,"description":7,"user-invocable":53},[24,23,31,25],{"author":47,"parent":25,"updated":48,"version":49,"openclaw":50,"repository":52},"Iamemily2050 (@iamemily2050)","2026-07-04","6.6.0",{"emoji":51,"homepage":52},"?","https:\u002F\u002Fgithub.com\u002FEmily2040\u002Fseedance-2.0",true,"main","f19b254e8975d0bfddb394686706106930d7964d","Video-Generation\u002Fseedance-20\u002Fskills\u002Fseedance-continuation","https:\u002F\u002Fgithub.com\u002Fendman100\u002Fskill-router-nexus","https:\u002F\u002Fgithub.com\u002Fendman100","2026-11-11 18:19:10",{"source":8,"skillName":5,"commands":61,"prompt":71,"zipAvailable":53},[62,65,68],{"tool":63,"command":64},"npx","npx skills add endman100\u002Fskill-router-nexus --skill seedance-continuation",{"tool":66,"command":67},"bunx","bunx skills add endman100\u002Fskill-router-nexus --skill seedance-continuation",{"tool":69,"command":70},"pnpm","pnpm dlx skills add endman100\u002Fskill-router-nexus --skill seedance-continuation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fendman100\u002Fskill-router-nexus\u002Fblob\u002Fmain\u002FVideo-Generation\u002Fseedance-20\u002Fskills\u002Fseedance-continuation\u002FSKILL.md",[],[74,96,134,155,164,188],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":78,"sourceHtmlUrl":79,"categories":80,"keywords":86,"publishedAt":40},"01M6MPCT5BXVER8HQZTW3QE9AS","create-master","基于佛教经典文献，生成特定高僧大德的 AI 教学角色","https:\u002F\u002Fgithub.com\u002Fendman100\u002Fskill-router-nexus\u002Fblob\u002Fmain\u002FMetaphysics-and-Spirituality\u002FMaster-skill\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fendman100\u002Fskill-router-nexus\u002Fblob\u002Fmain\u002FMetaphysics-and-Spirituality\u002FMaster-skill\u002FSKILL.md",[81],{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},"01JBSEEDCAT000000000000039","教师与教育","PROFESSION","适用职业",[87,88,39,89,26,90,91,92,93,94,95],"create master","master","生成","webfetch","edit","write","read","grep","Bash",{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":100,"sourceHtmlUrl":101,"categories":102,"keywords":114,"publishedAt":40},"01M6M43AKE95Y64E1JRXEF5QQ3","writing-dna-skill","从至少 20 篇完整文章中蒸馏可复用的写作 DNA，分析语言、文章结构、选题逻辑、素材策略、认知框架和视觉风格，并生成 Writing-DNA.md；按该 DNA 写作时会读取全部蒸馏产物和 5 篇相关原文。用于中英文作者、账号、品牌或出版物的风格分析与一致性写作。 Distill reusable Writing DNA from at least 20 complete articles for Chinese or English authors, publications, brands, and accounts; use for language, structure, topic logic, source strategy, cognitive-frame, and visual-style analysis.","https:\u002F\u002Fgithub.com\u002Fendman100\u002Fskill-router-nexus\u002Fblob\u002Fmain\u002FWriting-and-Content\u002Fwriting-dna-skill\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fendman100\u002Fskill-router-nexus\u002Fblob\u002Fmain\u002FWriting-and-Content\u002Fwriting-dna-skill\u002FSKILL.md",[103,108,111],{"categoryNo":104,"categoryName":105,"taxonomyType":106,"taxonomyTypeDesc":107},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":109,"categoryName":110,"taxonomyType":106,"taxonomyTypeDesc":107},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":112,"categoryName":113,"taxonomyType":84,"taxonomyTypeDesc":85},"01JBSEEDCAT000000000000036","内容创作者",[115,116,117,118,119,120,121,122,123,124,125,126,127,89,128,129,130,131,132,133],"writing dna skill","DNA","writing","strategy","english","logic","visual","structure","chinese","reusable","use","style","distill","analysis","frame","source","for","at","complete",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":138,"sourceHtmlUrl":139,"categories":140,"keywords":143,"publishedAt":40},"01M6M428TTCGQ4ME3KY99VN037","stop-slop","Remove AI writing patterns from prose. Use when drafting, editing, or reviewing text to eliminate predictable AI tells.","https:\u002F\u002Fgithub.com\u002Fendman100\u002Fskill-router-nexus\u002Fblob\u002Fmain\u002FWriting-and-Content\u002Fstop-slop\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fendman100\u002Fskill-router-nexus\u002Fblob\u002Fmain\u002FWriting-and-Content\u002Fstop-slop\u002FSKILL.md",[141,142],{"categoryNo":104,"categoryName":105,"taxonomyType":106,"taxonomyTypeDesc":107},{"categoryNo":112,"categoryName":113,"taxonomyType":84,"taxonomyTypeDesc":85},[144,145,146,147,22,148,38,149,150,125,151,152,153,131,154,117],"slop","stop slop","stop","drafting","drafts","patterns","prose","remove","editing","text","content",{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":159,"sourceHtmlUrl":160,"categories":161,"keywords":162,"publishedAt":40},"01M6M41X0B7EBX42TK435DMGGR","shuorenhua","检查和清理中英文文本里的 AI 套路，适用于“去 AI 味”“说人话”“自然一点”“别像模板”“先标问题”这类改写和审稿需求；按场景控制力度，同时保留事实、术语、语域和责任主体。","https:\u002F\u002Fgithub.com\u002Fendman100\u002Fskill-router-nexus\u002Fblob\u002Fmain\u002FWriting-and-Content\u002Fshuorenhua\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fendman100\u002Fskill-router-nexus\u002Fblob\u002Fmain\u002FWriting-and-Content\u002Fshuorenhua\u002FSKILL.md",[],[157,163],"文本",{"skillNo":165,"name":166,"nameZh":6,"description":167,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":168,"sourceHtmlUrl":169,"categories":170,"keywords":171,"publishedAt":40},"01M6M3ZD12WBEW5KXKDM4N6DFG","naming","Name products, SaaS, brands, open source projects, bots, and apps. Use when the user needs to name something, find a brand name, or pick a product name. Metaphor-driven process that produces memorable, meaningful names and avoids AI slop.","https:\u002F\u002Fgithub.com\u002Fendman100\u002Fskill-router-nexus\u002Fblob\u002Fmain\u002FWriting-and-Content\u002Fnaming-main\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fendman100\u002Fskill-router-nexus\u002Fblob\u002Fmain\u002FWriting-and-Content\u002Fnaming-main\u002FSKILL.md",[],[166,172,173,174,175,176,125,177,93,130,178,179,180,181,95,182,183,184,185,22,186,187,144],"repo","websearch","product name","apps","bots","view","brand","pick","gh","projects","open","saas","open source","product","describe","ai slop",{"skillNo":189,"name":190,"nameZh":6,"description":191,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":192,"sourceHtmlUrl":193,"categories":194,"keywords":196,"publishedAt":40},"01M6M3YVXAFAAWJ7F6JMPFREYE","humanizer-zh","去除文本中的 AI 生成痕迹。适用于编辑或审阅文本，使其听起来更自然、更像人类书写。\n基于维基百科的\"AI 写作特征\"综合指南。检测并修复以下模式：夸大的象征意义、\n宣传性语言、以 -ing 结尾的肤浅分析、模糊的归因、破折号过度使用、三段式法则、\nAI 词汇、否定式排比、过多的连接性短语。","https:\u002F\u002Fgithub.com\u002Fendman100\u002Fskill-router-nexus\u002Fblob\u002Fmain\u002FWriting-and-Content\u002Fhumanizer-zh\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fendman100\u002Fskill-router-nexus\u002Fblob\u002Fmain\u002FWriting-and-Content\u002Fhumanizer-zh\u002FSKILL.md",[195],{"categoryNo":104,"categoryName":105,"taxonomyType":106,"taxonomyTypeDesc":107},[197,198,199,93,92,91,117,89,163,200,144,146],"humanizer","zh","humanizer zh","翻译"]