[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ESG6C24YDK7EBVR27G9SS7":3,"skill-same:01M7ESG6C24YDK7EBVR27G9SS7":58},{"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":37,"commitSha":38,"skillDirectory":39,"forksCount":40,"repositoryHtmlUrl":41,"repositoryHomepageUrl":6,"ownerHtmlUrl":42,"ownerBlogUrl":6,"ownerDescription":43,"updatedAt":44,"install":45,"resources":57},"01M7ESG6C24YDK7EBVR27G9SS7","seedance-interview-short",null,"This skill should be used when the user wants a fast Seedance 2.0 creative brief, a short interview, a compressed intake flow, or a quick director-style clarification before prompt writing.","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fseedance-interview-short\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: seedance-interview-short\ndescription: \"This skill should be used when the user wants a fast Seedance 2.0 creative brief, a short interview, a compressed intake flow, or a quick director-style clarification before prompt writing.\"\nlicense: MIT\nuser-invocable: true\ntags:\n  - creative-direction\n  - brief\n  - compression\n  - seedance-20\nmetadata:\n  version: \"6.7.0\"\n  updated: \"2026-08-01\"\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-interview-short\n\nBefore producing prompt text, a prompt-ready block, a rewrite, an example, or a compiled clip, load the [Director's Read](..\u002F..\u002Freferences\u002Fdirectors-read.md), classify the brief, and complete its canonical narrative or non-narrative record. Translate that record into visible or audible carriers and keep its internal labels out of final generation prose.\n\nUse this when speed matters more than exhaustive creative discovery. The goal is to turn a vague idea into a compact director brief with no more than three questions, then route to prompt writing.\n\nSpeed does not bypass story judgment. Load the [Director's Read](..\u002F..\u002Freferences\u002Fdirectors-read.md) before producing the compact brief. Use its canonical classification and the corresponding internal record; do not duplicate or broaden the lane rules here. Never reconstruct the read from remembered craft.\n\n## Intent\n\nThe user here knows what they want and is asking you to respect their momentum. The soul of this skill is restraint: find the one missing piece that would sink the generation, ask only that, and get out of the way. Speed is the form their trust takes.\n\n## Process\n\nAsk at most three questions, and only ask them if the answer materially changes the prompt. Assume no film background: ask in everyday words, give pickable options, and attach a default so \"I don't know\" never stalls the brief. Prioritize:\n\n1. What happens in the video, and what is different at the end? `(not sure? I'll pick one simple action with a visible ending)`\n2. Do you have photos, clips, or sound that should define this clip's appearance, movement, or sound? `(none is fine; I'll draft from your idea)`\n3. Only if the user asks for connected clips, a longer scene to divide, or continuation: how must the complete story end, and what accepted footage or final frame already exists? `(if continuing, I need the accepted clip or final frame)`\n\nUnknown duration alone does not make a sequence. For one clip, ask at most one blocking question; otherwise state a reversible assumption and draft. Do not ask whether this should become a series before the first draft. Preserve information the user already supplied. Explicit connected-clip or continuation intent still activates sequence planning and its accepted-footage gate.\n\nIf the user already supplied enough information, do not ask. Produce a brief immediately. If the user speaks production language fluently, drop the plain phrasing and ask in director terms.\n\nRun the interview and brief in the user's language; for localized starting-point menus and invites, load [interview-starters](..\u002F..\u002Freferences\u002Finterview-starters.md). If the user gives explicit shot, lens, camera, blocking, or performance direction, keep it verbatim and compile it into a shot-contract-grade brief - never simplify or override a professional's spec. When direction is unresolved, draft with a reversible assumption or offer up to three brief-specific choices from that reference; this counts toward the existing question limit. Options change staging, attention, timing, or performance and state a real tradeoff. A “choose for me” reply means choose and draft now. Preserve chosen and rejected options, and skip the menu for a specified brief.\n\nEven in fast mode, the brief states one motivated intention, not a generic \"cinematic\" look. For narrative work, derive it from the completed [Director's Read](..\u002F..\u002Freferences\u002Fdirectors-read.md) record and translate the turn, visible suppressed behavior, and non-transferable detail into filmable or audible carriers. For non-narrative work, serve the utility intent without inventing want, power, conflict, or subtext. Load [directing-engine](..\u002F..\u002Freferences\u002Fdirecting-engine.md) only when the right setup for the scene is genuinely unclear.\n\n## Compact Brief Pattern\n\nInternal lane record from the [Director's Read](..\u002F..\u002Freferences\u002Fdirectors-read.md), then: `Mode: [T2V\u002FI2V\u002FV2V\u002FR2V]. Subject: [anchor]. Beat: [before -> action -> final state]. Camera: [one move]. Light\u002Fstyle: [physical source and safe descriptor]. Sound: [dialogue\u002Fambience\u002FSFX\u002Fmusic\u002Fsilence]. Constraints: [identity, IP, safety, product, prompt budget].`\n\n## Routing Rule\n\nRoute to [seedance-sequence](..\u002Fseedance-sequence\u002FSKILL.md) when the user requests connected clips or a long story that needs multiple generations; [seedance-continuation](..\u002Fseedance-continuation\u002FSKILL.md) for accepted-footage continuation; [seedance-prompt](..\u002Fseedance-prompt\u002FSKILL.md) for a full standalone production prompt; [seedance-prompt-short](..\u002Fseedance-prompt-short\u002FSKILL.md) for a compact prompt, including one clip whose duration is undecided; [seedance-copyright](..\u002Fseedance-copyright\u002FSKILL.md) for IP\u002Flikeness risk; or [seedance-troubleshoot](..\u002Fseedance-troubleshoot\u002FSKILL.md) when the user starts from a bad result.\n\n## Output Contract\n\nReturn one compact brief under 150 words, any missing high-impact question, and a recommended skill route. When an optional choice is still pending, show the short options instead of a dossier; after selection, output only the chosen brief unless alternatives were requested. Choosing a direction does not authorize paid generation. Keep Director's Read labels out of final generation prose; show the internal record only when the user requests the planning rationale or when another agent needs the handoff. If the request is a sequence, include the complete story ending, likely clip count, current clip job, and the fact that future prompts stay provisional until accepted footage is reviewed.\n","# seedance-interview-short\n\nBefore producing prompt text, a prompt-ready block, a rewrite, an example, or a compiled clip, load the [Director's Read](..\u002F..\u002Freferences\u002Fdirectors-read.md), classify the brief, and complete its canonical narrative or non-narrative record. Translate that record into visible or audible carriers and keep its internal labels out of final generation prose.\n\nUse this when speed matters more than exhaustive creative discovery. The goal is to turn a vague idea into a compact director brief with no more than three questions, then route to prompt writing.\n\nSpeed does not bypass story judgment. Load the [Director's Read](..\u002F..\u002Freferences\u002Fdirectors-read.md) before producing the compact brief. Use its canonical classification and the corresponding internal record; do not duplicate or broaden the lane rules here. Never reconstruct the read from remembered craft.\n\n## Intent\n\nThe user here knows what they want and is asking you to respect their momentum. The soul of this skill is restraint: find the one missing piece that would sink the generation, ask only that, and get out of the way. Speed is the form their trust takes.\n\n## Process\n\nAsk at most three questions, and only ask them if the answer materially changes the prompt. Assume no film background: ask in everyday words, give pickable options, and attach a default so \"I don't know\" never stalls the brief. Prioritize:\n\n1. What happens in the video, and what is different at the end? `(not sure? I'll pick one simple action with a visible ending)`\n2. Do you have photos, clips, or sound that should define this clip's appearance, movement, or sound? `(none is fine; I'll draft from your idea)`\n3. Only if the user asks for connected clips, a longer scene to divide, or continuation: how must the complete story end, and what accepted footage or final frame already exists? `(if continuing, I need the accepted clip or final frame)`\n\nUnknown duration alone does not make a sequence. For one clip, ask at most one blocking question; otherwise state a reversible assumption and draft. Do not ask whether this should become a series before the first draft. Preserve information the user already supplied. Explicit connected-clip or continuation intent still activates sequence planning and its accepted-footage gate.\n\nIf the user already supplied enough information, do not ask. Produce a brief immediately. If the user speaks production language fluently, drop the plain phrasing and ask in director terms.\n\nRun the interview and brief in the user's language; for localized starting-point menus and invites, load [interview-starters](..\u002F..\u002Freferences\u002Finterview-starters.md). If the user gives explicit shot, lens, camera, blocking, or performance direction, keep it verbatim and compile it into a shot-contract-grade brief - never simplify or override a professional's spec. When direction is unresolved, draft with a reversible assumption or offer up to three brief-specific choices from that reference; this counts toward the existing question limit. Options change staging, attention, timing, or performance and state a real tradeoff. A “choose for me” reply means choose and draft now. Preserve chosen and rejected options, and skip the menu for a specified brief.\n\nEven in fast mode, the brief states one motivated intention, not a generic \"cinematic\" look. For narrative work, derive it from the completed [Director's Read](..\u002F..\u002Freferences\u002Fdirectors-read.md) record and translate the turn, visible suppressed behavior, and non-transferable detail into filmable or audible carriers. For non-narrative work, serve the utility intent without inventing want, power, conflict, or subtext. Load [directing-engine](..\u002F..\u002Freferences\u002Fdirecting-engine.md) only when the right setup for the scene is genuinely unclear.\n\n## Compact Brief Pattern\n\nInternal lane record from the [Director's Read](..\u002F..\u002Freferences\u002Fdirectors-read.md), then: `Mode: [T2V\u002FI2V\u002FV2V\u002FR2V]. Subject: [anchor]. Beat: [before -> action -> final state]. Camera: [one move]. Light\u002Fstyle: [physical source and safe descriptor]. Sound: [dialogue\u002Fambience\u002FSFX\u002Fmusic\u002Fsilence]. Constraints: [identity, IP, safety, product, prompt budget].`\n\n## Routing Rule\n\nRoute to [seedance-sequence](..\u002Fseedance-sequence\u002FSKILL.md) when the user requests connected clips or a long story that needs multiple generations; [seedance-continuation](..\u002Fseedance-continuation\u002FSKILL.md) for accepted-footage continuation; [seedance-prompt](..\u002Fseedance-prompt\u002FSKILL.md) for a full standalone production prompt; [seedance-prompt-short](..\u002Fseedance-prompt-short\u002FSKILL.md) for a compact prompt, including one clip whose duration is undecided; [seedance-copyright](..\u002Fseedance-copyright\u002FSKILL.md) for IP\u002Flikeness risk; or [seedance-troubleshoot](..\u002Fseedance-troubleshoot\u002FSKILL.md) when the user starts from a bad result.\n\n## Output Contract\n\nReturn one compact brief under 150 words, any missing high-impact question, and a recommended skill route. When an optional choice is still pending, show the short options instead of a dossier; after selection, output only the chosen brief unless alternatives were requested. Choosing a direction does not authorize paid generation. Keep Director's Read labels out of final generation prose; show the internal record only when the user requests the planning rationale or when another agent needs the handoff. If the request is a sequence, include the complete story ending, likely clip count, current clip job, and the fact that future prompts stay provisional until accepted footage is reviewed.\n",{"name":5,"tags":24,"license":15,"metadata":29,"description":7,"user-invocable":36},[25,26,27,28],"creative-direction","brief","compression","seedance-20",{"author":30,"parent":28,"updated":31,"version":32,"openclaw":33,"repository":35},"Iamemily2050 (@iamemily2050)","2026-08-01","6.7.0",{"emoji":34,"homepage":35},"🎬","https:\u002F\u002Fgithub.com\u002FEmily2040\u002Fseedance-2.0",true,"main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","04-安全渗透\u002Fseedance-interview-short",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":46,"prompt":56,"zipAvailable":36},[47,50,53],{"tool":48,"command":49},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill seedance-interview-short",{"tool":51,"command":52},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill seedance-interview-short",{"tool":54,"command":55},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill seedance-interview-short","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fseedance-interview-short\u002FSKILL.md",[],[59,67,72,79,86,93],{"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":66},"01M7FFG485KY83TD6HSC4YPCMC","obsidian-clipper-template-creator","Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator\u002FSKILL.md",[],[],"2026-11-16 10:05:34",{"skillNo":68,"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":69,"categories":70,"keywords":71,"publishedAt":66},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":66},"01M7FFFY0QEM14SKWPDYGMXM2P","python-api","Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP\u002FmAP semantics, and source-style import diagnostics.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Fpython-api\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":66},"01M7FFFVZQZ2GJ0C0TGP7JHD20","file-evaluation","Folder-based PASCAL VOC AP\u002FmAP evaluation from ground-truth and detection text files.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Ffile-evaluation\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":66},"01M7FFFSFNYSE77SJ6PE1CK2DA","object-detection-metrics","Guides legacy Object-Detection-Metrics PASCAL VOC AP\u002FmAP evaluation from detection text folders and direct Python API classes.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":66},"01M7FFFP0GCK1RVXBCPQ8APBMT","nx-workspace-patterns","Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fnx-workspace-patterns\u002FSKILL.md",[],[]]