[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CFGQQF38MH1ATXVMVT107Z":3,"skill-same:01M7CFGQQF38MH1ATXVMVT107Z":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":15,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":5,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7CFGQQF38MH1ATXVMVT107Z","product-launch-video",null,"Turn a product URL, launch brief, or approved script into a production-ready launch video. Use for product reveals, feature announcements, SaaS launches, and narrated product films; not for generic explainers or editing existing footage.","getedgehq\u002Fskills","getedgehq","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F327350993?v=4","01M7CEH5YJQYF1PB3MDG9PA5HX","01M7CEH5ZAPY8TX4H3E04KM875",5,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fproduct-launch-video\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fproduct-launch-video\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: product-launch-video\ndescription: Turn a product URL, launch brief, or approved script into a production-ready launch video. Use for product reveals, feature announcements, SaaS launches, and narrated product films; not for generic explainers or editing existing footage.\n---\n\n# Product Launch Video\n\nCreate a launch film whose story, visual system, motion, and evidence all come\nfrom the product being launched. The deliverable is a rendered video plus the\neditable project that produced it.\n\nUse HyperFrames when it is installed. A Remotion project is also supported;\nprefer maintained remocn components over recreating common animation\nprimitives. Do not switch stacks after the storyboard is approved.\n\n## Inputs to lock\n\nBefore building, establish:\n\n- product URL or source brief;\n- audience and the one change in belief the film should create;\n- aspect ratio, target duration, language, and narration choice;\n- claims that may appear and the evidence behind each;\n- whether an existing script must remain verbatim or may be restructured.\n\nIf any of these would materially change the film, ask once before starting.\n\n## Required output\n\nKeep the project editable. At minimum, produce:\n\n```text\ncapture\u002F                 product copy, screenshots, logos, and design tokens\nSTORYBOARD.md            approved shot-by-shot plan\nSCRIPT.md                narration, when the film is narrated\ndesign.md                type, color, spacing, motion, and framing rules\ncompositions\u002F            source for every shot\nrenders\u002Flaunch.mp4       final delivery\n```\n\nDo not treat a preview, storyboard, contact sheet, or silent draft as the final\nvideo.\n\n## Workflow\n\n### 1. Capture the product\n\nInspect the supplied URL or assets. Preserve exact product copy, real UI,\nlogos, typography, colors, and interface states. Record every usable asset and\nits source. Do not invent features, customers, metrics, or integrations.\n\nIf no website exists, create a small source record from the brief and supplied\nassets so later shots still have a traceable basis.\n\n### 2. Choose the story\n\nWrite one sentence for each of these before storyboarding:\n\n- the audience's present frustration;\n- the product's distinctive mechanism;\n- the proof the viewer should believe;\n- the action the viewer should take.\n\nSelect only the beats the source material supports. A short film usually needs\na hook, mechanism, proof, and close; it does not need a feature inventory.\n\nRead [references\u002Fstory-and-shot-system.md](references\u002Fstory-and-shot-system.md)\nwhen planning the sequence.\n\n### 3. Establish the visual system\n\nDerive `design.md` from the captured product rather than from a generic video\ntemplate. Define the canvas, typography, color roles, grid, safe areas, visual\ndensity, motion character, caption treatment, and transition family.\n\nLimit the film to one visual grammar. Repetition creates identity; a new style\nfor every shot makes the film feel assembled from templates.\n\n### 4. Storyboard before animation\n\nFor every shot, record:\n\n- start and end time;\n- narrative job;\n- exact on-screen copy;\n- source asset or UI state;\n- composition and camera intent;\n- entrance, development, and exit;\n- transition to the next shot;\n- any claim and its evidence source.\n\nThe frame must continue developing for its useful duration. Avoid an entrance\nanimation followed by several seconds of static content.\n\nShow the storyboard for approval before building the full film.\n\n### 5. Build with maintained primitives\n\nHyperFrames is preferred for HTML shot sequences. For Remotion, read\n[references\u002Fremotion-and-remocn.md](references\u002Fremotion-and-remocn.md) and use\nremocn for common typography, terminal, chart, background, and transition\nbehaviors. Custom animation is appropriate only when the product requires a\nmotion idea that the library cannot express.\n\nEvery shot must be deterministic at an arbitrary frame. Do not rely on runtime\ntimers, non-seeded randomness, or interaction state that a renderer cannot\nreproduce.\n\n### 6. Review the assembled film\n\nBefore rendering, inspect:\n\n- first, middle, and final frames of every shot;\n- every transition seam;\n- text wrapping, clipping, contrast, and safe areas;\n- timing against narration and music;\n- product fidelity and claim accuracy;\n- the full film at normal speed with audio;\n- a silent pass, so the visual story still makes sense.\n\nRun `node scripts\u002Fcheck-project.mjs \u003Cproject-dir>` for the package-level project\ngate. Also run the native lint, validation, and render checks of the selected\nvideo stack.\n\nPause for approval on the assembled preview. Render the final MP4 only after\napproval.\n\n## Evidence boundary\n\nA polished example demonstrates intended craft; it does not prove the skill\nimproves model performance. Report separately:\n\n- package and project checks;\n- successful final render;\n- human visual review;\n- any comparative evaluation, only when recorded runs and scoring exist.\n\nNever call the skill evaluated because one attractive video was produced.\n\n## Failure conditions\n\nStop rather than ship when:\n\n- the primary product claim cannot be sourced;\n- captured UI is replaced by invented interface chrome;\n- a shot is illegible at delivery resolution;\n- narration and picture disagree;\n- the project cannot render deterministically;\n- the editable source or final MP4 is missing.\n\n","# Product Launch Video\n\nCreate a launch film whose story, visual system, motion, and evidence all come\nfrom the product being launched. The deliverable is a rendered video plus the\neditable project that produced it.\n\nUse HyperFrames when it is installed. A Remotion project is also supported;\nprefer maintained remocn components over recreating common animation\nprimitives. Do not switch stacks after the storyboard is approved.\n\n## Inputs to lock\n\nBefore building, establish:\n\n- product URL or source brief;\n- audience and the one change in belief the film should create;\n- aspect ratio, target duration, language, and narration choice;\n- claims that may appear and the evidence behind each;\n- whether an existing script must remain verbatim or may be restructured.\n\nIf any of these would materially change the film, ask once before starting.\n\n## Required output\n\nKeep the project editable. At minimum, produce:\n\n```text\ncapture\u002F                 product copy, screenshots, logos, and design tokens\nSTORYBOARD.md            approved shot-by-shot plan\nSCRIPT.md                narration, when the film is narrated\ndesign.md                type, color, spacing, motion, and framing rules\ncompositions\u002F            source for every shot\nrenders\u002Flaunch.mp4       final delivery\n```\n\nDo not treat a preview, storyboard, contact sheet, or silent draft as the final\nvideo.\n\n## Workflow\n\n### 1. Capture the product\n\nInspect the supplied URL or assets. Preserve exact product copy, real UI,\nlogos, typography, colors, and interface states. Record every usable asset and\nits source. Do not invent features, customers, metrics, or integrations.\n\nIf no website exists, create a small source record from the brief and supplied\nassets so later shots still have a traceable basis.\n\n### 2. Choose the story\n\nWrite one sentence for each of these before storyboarding:\n\n- the audience's present frustration;\n- the product's distinctive mechanism;\n- the proof the viewer should believe;\n- the action the viewer should take.\n\nSelect only the beats the source material supports. A short film usually needs\na hook, mechanism, proof, and close; it does not need a feature inventory.\n\nRead [references\u002Fstory-and-shot-system.md](references\u002Fstory-and-shot-system.md)\nwhen planning the sequence.\n\n### 3. Establish the visual system\n\nDerive `design.md` from the captured product rather than from a generic video\ntemplate. Define the canvas, typography, color roles, grid, safe areas, visual\ndensity, motion character, caption treatment, and transition family.\n\nLimit the film to one visual grammar. Repetition creates identity; a new style\nfor every shot makes the film feel assembled from templates.\n\n### 4. Storyboard before animation\n\nFor every shot, record:\n\n- start and end time;\n- narrative job;\n- exact on-screen copy;\n- source asset or UI state;\n- composition and camera intent;\n- entrance, development, and exit;\n- transition to the next shot;\n- any claim and its evidence source.\n\nThe frame must continue developing for its useful duration. Avoid an entrance\nanimation followed by several seconds of static content.\n\nShow the storyboard for approval before building the full film.\n\n### 5. Build with maintained primitives\n\nHyperFrames is preferred for HTML shot sequences. For Remotion, read\n[references\u002Fremotion-and-remocn.md](references\u002Fremotion-and-remocn.md) and use\nremocn for common typography, terminal, chart, background, and transition\nbehaviors. Custom animation is appropriate only when the product requires a\nmotion idea that the library cannot express.\n\nEvery shot must be deterministic at an arbitrary frame. Do not rely on runtime\ntimers, non-seeded randomness, or interaction state that a renderer cannot\nreproduce.\n\n### 6. Review the assembled film\n\nBefore rendering, inspect:\n\n- first, middle, and final frames of every shot;\n- every transition seam;\n- text wrapping, clipping, contrast, and safe areas;\n- timing against narration and music;\n- product fidelity and claim accuracy;\n- the full film at normal speed with audio;\n- a silent pass, so the visual story still makes sense.\n\nRun `node scripts\u002Fcheck-project.mjs \u003Cproject-dir>` for the package-level project\ngate. Also run the native lint, validation, and render checks of the selected\nvideo stack.\n\nPause for approval on the assembled preview. Render the final MP4 only after\napproval.\n\n## Evidence boundary\n\nA polished example demonstrates intended craft; it does not prove the skill\nimproves model performance. Report separately:\n\n- package and project checks;\n- successful final render;\n- human visual review;\n- any comparative evaluation, only when recorded runs and scoring exist.\n\nNever call the skill evaluated because one attractive video was produced.\n\n## Failure conditions\n\nStop rather than ship when:\n\n- the primary product claim cannot be sourced;\n- captured UI is replaced by invented interface chrome;\n- a shot is illegible at delivery resolution;\n- narration and picture disagree;\n- the project cannot render deterministically;\n- the editable source or final MP4 is missing.\n\n",{"name":5,"description":7},"main","01960aeb08909dbd0c1a2d4f219cdb300099b8b9",0,"https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills","https:\u002F\u002Fgetedge.cc","https:\u002F\u002Fgithub.com\u002Fgetedgehq","2026-11-12 10:05:02",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add getedgehq\u002Fskills --skill product-launch-video",{"tool":37,"command":38},"bunx","bunx skills add getedgehq\u002Fskills --skill product-launch-video",{"tool":40,"command":41},"pnpm","pnpm dlx skills add getedgehq\u002Fskills --skill product-launch-video","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fproduct-launch-video\u002FSKILL.md",true,[45,51,55,59,63,69],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"DERIVATION.json","REFERENCE","参考文档",3026,"https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fproduct-launch-video\u002FDERIVATION.json",{"path":52,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":15},"LICENSE","许可证",10756,{"path":56,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Fremotion-and-remocn.md",2196,"https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fproduct-launch-video\u002Freferences\u002Fremotion-and-remocn.md",{"path":60,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":61,"sourceHtmlUrl":62},"references\u002Fstory-and-shot-system.md",2427,"https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fproduct-launch-video\u002Freferences\u002Fstory-and-shot-system.md",{"path":64,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":67,"sourceHtmlUrl":68},"scripts\u002Fcheck-project.mjs","SCRIPT","脚本",1257,"https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fproduct-launch-video\u002Fscripts\u002Fcheck-project.mjs",{"path":70,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":71,"sourceHtmlUrl":72},"tests\u002Fcheck-project.test.mjs",1127,"https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fproduct-launch-video\u002Ftests\u002Fcheck-project.test.mjs",[74,82,90,97,104,112],{"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":81,"publishedAt":19},"01M7CFVPC1P7JN60J5AN9AZZ5G","zero-downtime-cloud-move","Runbook for moving a live app from one cloud to another (Google Cloud to AWS, AWS to Google Cloud, a PaaS to your own account, or one storage provider to another) without downtime. The agent inventories what is really running, builds the new stack next to the old one, keeps a one-line rollback for every phase, proves the new stack with real workloads before any traffic moves, cuts over with a checklist, watches a fixed window after the switch, copies data with an idempotent job whose second pass must report 0 left, and deletes the old cloud last. Use when someone asks to migrate, move or replatform a production app, switch cloud providers, move a backend, database files or object storage, plan a DNS cutover, or decommission an old cloud account.","https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fzero-downtime-cloud-move\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fzero-downtime-cloud-move\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":86,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7CFVH8VN6G2KE8PBFD1CRMN","zayats-ceo-branding","Build an evidence-based CEO positioning paper, Personal Branding Roadmap, and editorial workflow using Marina Zayats's public method. Use for executive branding, LinkedIn ghostwriting briefs, profile strategy, and recurring CEO-approved content planning.","https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fzayats-ceo-branding\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fzayats-ceo-branding\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M7CFV9BB7G8K8CX9RKZ3GECX","yc-app-roast","YC App Roast: roast a YC or a16z Speedrun application. Use when a founder wants their YC or Speedrun answers scored, asks \"what would a YC partner think\", wants the weak answers found or rewritten, or wants their draft checked before they submit. Scores every answer 0-10 against public advice from YC and Speedrun partners, names the top issue with the exact words that cost points, and writes a rewrite from the founder's own facts. Works for YC and a16z Speedrun. Not affiliated with Y Combinator or a16z.","https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fyc-app-roast\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":19},"01M7CFV11Z1HB9EEWFQ6PCJ98X","yc-app-review","YC App Review: get a YC or a16z Speedrun application reviewed by people you trust. Use when a founder wants friends, mentors or alumni to review their YC or Speedrun application, or asks to share their draft for feedback. Builds a shareable review page (one HTML file, application-portal look) where reviewers leave notes per question and press \"Send my notes\" to send them back as text, then parses the notes into proposed rewrites. Optional tracked private links per reviewer. Works for YC and a16z Speedrun. Not affiliated with Y Combinator or a16z.","https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fyc-app-review\u002FSKILL.md",[],[],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":108,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":19},"01M7CFTSVJV7XCSW62W39MX8CZ","x-growth-playbook","X Growth Playbook. Analyse a person's own X (Twitter) posts and tell them what to post next, with the numbers behind every claim. Compares quote posts vs originals, links vs no links, short vs long, time of day in their timezone, media vs text and the topics they name, reports medians with n, then writes a 10-step plan and the next 7 posts in their voice. Use when the user says \"analyse my X posts\", \"what works on my Twitter\", \"how do I grow on X\", \"what should I post next on X\", \"audit my X account\", or shares an X data archive, X API export or a list of their posts. Runs on the user's computer.","https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fx-growth-playbook\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fx-growth-playbook\u002FSKILL.md",[],[],{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":116,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":19},"01M7CFTK101S3P00MQ129G5YNH","workplan","Create, update, or close work plans for multi-step tasks. Use when starting refactors, bug lists, feature work, migrations, or any task with 2+ steps. Also use after auto-compaction to re-orient. Triggers: \"workplan\", \"work plan\", \"create a plan\", \"what's the plan\", \"where was I\", or when Claude detects a multi-step task that needs tracking.","https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fworkplan\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fworkplan\u002FSKILL.md",[],[]]