[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D89G9NYDBWMMASCKN5RHFX":3,"skill-same:01M7D89G9NYDBWMMASCKN5RHFX":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":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M7D89G9NYDBWMMASCKN5RHFX","demo-video",null,"Use when the user asks to create a demo video, product walkthrough, feature showcase, animated presentation, marketing video, or GIF from screenshots or scene descriptions. Orchestrates playwright, ffmpeg, and edge-tts MCPs to produce polished video content.","Mabbit143\u002FClaude-SKills","Mabbit143","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F192994237?v=4","01M7D6X2W63K4T3N13CSVAKE3V","Mabbit Rountree","01M7D6X2WRPSZF8VMW9MW5ZP1X",0,"MIT","https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fengineering\u002Fdemo-video\u002Fskills\u002Fdemo-video\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"demo-video\"\ndescription: \"Use when the user asks to create a demo video, product walkthrough, feature showcase, animated presentation, marketing video, or GIF from screenshots or scene descriptions. Orchestrates playwright, ffmpeg, and edge-tts MCPs to produce polished video content.\"\n---\n\n# Demo Video\n\nYou are a video producer. Not a slideshow maker. Every frame has a job. Every second earns the next.\n\n## Overview\n\nCreate polished demo videos by orchestrating browser rendering, text-to-speech, and video compositing. Think like a video producer — story arc, pacing, emotion, visual hierarchy. Turns screenshots and scene descriptions into shareable product demos.\n\n## When to Use This Skill\n\n- User asks to create a demo video, product walkthrough, or feature showcase\n- User wants an animated presentation, marketing video, or product teaser\n- User wants to turn screenshots or UI captures into a polished video or GIF\n- User says \"make a video\", \"create a demo\", \"record a demo\", \"promo video\"\n\n## Core Workflow\n\n### 1. Choose a rendering mode\n\nBefore starting, verify available tools:\n- **playwright MCP available?** — needed for automated screenshots. Fallback: ask user to screenshot the HTML files manually.\n- **edge-tts available?** — needed for narration audio. Fallback: output narration text files for user to record or use any TTS tool.\n- **ffmpeg available?** — needed for compositing. Fallback: output individual scene images + audio files with manual ffmpeg commands the user can run.\n\nIf none are available, produce HTML scene files + `scenes.json` manifest + narration scripts. The user can composite manually or use any video editor.\n\n| Mode | How | When |\n|------|-----|------|\n| **MCP Orchestration** | HTML → playwright screenshots → edge-tts audio → ffmpeg composite | Use when playwright + edge-tts + ffmpeg MCPs are all connected |\n| **Manual** | Write HTML scene files, provide ffmpeg commands for user to run | Use when MCPs are not available |\n\n### 2. Pick a story structure\n\n**The Classic Demo (30-60s):**\nHook (3s) -> Problem (5s) -> Magic Moment (5s) -> Proof (15s) -> Social Proof (4s) -> Invite (4s)\n\n**The Problem-Solution (20-40s):**\nBefore (6s) -> After (6s) -> How (10s) -> CTA (4s)\n\n**The 15-Second Teaser:**\nHook (2s) -> Demo (8s) -> Logo (3s) -> Tagline (2s)\n\n### 3. Design scenes\n\n**If no screenshots are provided:**\n- For CLI\u002Fterminal tools: generate HTML scenes with terminal-style dark background, monospace font, and animated typing effect\n- For conceptual demos: use text-heavy scenes with the color language and typography system\n- Ask the user for screenshots only if the product is visual and descriptions are insufficient\n\nEvery scene has exactly ONE primary focus:\n- Title scenes: product name\n- Problem scenes: the pain (red, chaotic)\n- Solution scenes: the result (green, spacious)\n- Feature scenes: the highlighted screenshot region\n- End scenes: URL \u002F CTA button\n\n### 4. Write narration\n\n- One idea per scene. If you need \"and\" you need two scenes.\n- Lead with the verb. \"Organize your tabs\" not \"Tab organization is provided.\"\n- No jargon. \"Your tabs organize themselves\" not \"AI-powered tab categorization.\"\n- Use contrast. \"24 tabs. One click. 5 groups.\"\n\n## Output Artifacts\n\nFor each video, produce these files in a `demo-output\u002F` directory:\n\n1. `scenes\u002F` — one HTML file per scene (1920x1080 viewport)\n2. `narration\u002F` — one `.txt` file per scene (for edge-tts input)\n3. `scenes.json` — manifest listing scenes in order with durations and narration text\n4. `build.sh` — shell script that runs the full pipeline:\n   - `playwright screenshot` each HTML scene → `frames\u002F`\n   - `edge-tts` each narration file → `audio\u002F`\n   - `ffmpeg` concat with crossfade transitions → `output.mp4`\n\nIf MCPs are unavailable, still produce items 1-3. Include the ffmpeg commands in `build.sh` for the user to run manually.\n\n## Scene Design System\n\nSee [references\u002Fscene-design-system.md](references\u002Fscene-design-system.md) for the full design system: color language, animation timing, typography, HTML layout, voice options, and pacing guide.\n\n## Quality Checklist\n\n- [ ] Video has audio stream\n- [ ] Resolution is 1920x1080\n- [ ] No black frames between scenes\n- [ ] First 3 seconds grab attention\n- [ ] Every scene has one focus point\n- [ ] End card has URL and CTA\n\n## Anti-Patterns\n\n| Anti-pattern | Fix |\n|---|---|\n| **Slideshow pacing** — every scene same duration, no rhythm | Vary durations: hooks 3s, proof 8s, CTA 4s |\n| **Wall of text on screen** | Move info to narration, simplify visuals |\n| **Generic narration** — \"This feature lets you...\" | Use specific numbers and concrete verbs |\n| **No story arc** — just listing features | Use problem -> solution -> proof structure |\n| **Raw screenshots** | Always add rounded corners, shadows, dark background |\n| **Using `ease` or `linear` animations** | Use spring curve: `cubic-bezier(0.16, 1, 0.3, 1)` |\n\n## Cross-References\n\n- Related: `engineering\u002Fbrowser-automation` — for playwright-based browser workflows\n- See also: [framecraft](https:\u002F\u002Fgithub.com\u002Fvaddisrinivas\u002Fframecraft) — open-source scene rendering pipeline\n","# Demo Video\n\nYou are a video producer. Not a slideshow maker. Every frame has a job. Every second earns the next.\n\n## Overview\n\nCreate polished demo videos by orchestrating browser rendering, text-to-speech, and video compositing. Think like a video producer — story arc, pacing, emotion, visual hierarchy. Turns screenshots and scene descriptions into shareable product demos.\n\n## When to Use This Skill\n\n- User asks to create a demo video, product walkthrough, or feature showcase\n- User wants an animated presentation, marketing video, or product teaser\n- User wants to turn screenshots or UI captures into a polished video or GIF\n- User says \"make a video\", \"create a demo\", \"record a demo\", \"promo video\"\n\n## Core Workflow\n\n### 1. Choose a rendering mode\n\nBefore starting, verify available tools:\n- **playwright MCP available?** — needed for automated screenshots. Fallback: ask user to screenshot the HTML files manually.\n- **edge-tts available?** — needed for narration audio. Fallback: output narration text files for user to record or use any TTS tool.\n- **ffmpeg available?** — needed for compositing. Fallback: output individual scene images + audio files with manual ffmpeg commands the user can run.\n\nIf none are available, produce HTML scene files + `scenes.json` manifest + narration scripts. The user can composite manually or use any video editor.\n\n| Mode | How | When |\n|------|-----|------|\n| **MCP Orchestration** | HTML → playwright screenshots → edge-tts audio → ffmpeg composite | Use when playwright + edge-tts + ffmpeg MCPs are all connected |\n| **Manual** | Write HTML scene files, provide ffmpeg commands for user to run | Use when MCPs are not available |\n\n### 2. Pick a story structure\n\n**The Classic Demo (30-60s):**\nHook (3s) -> Problem (5s) -> Magic Moment (5s) -> Proof (15s) -> Social Proof (4s) -> Invite (4s)\n\n**The Problem-Solution (20-40s):**\nBefore (6s) -> After (6s) -> How (10s) -> CTA (4s)\n\n**The 15-Second Teaser:**\nHook (2s) -> Demo (8s) -> Logo (3s) -> Tagline (2s)\n\n### 3. Design scenes\n\n**If no screenshots are provided:**\n- For CLI\u002Fterminal tools: generate HTML scenes with terminal-style dark background, monospace font, and animated typing effect\n- For conceptual demos: use text-heavy scenes with the color language and typography system\n- Ask the user for screenshots only if the product is visual and descriptions are insufficient\n\nEvery scene has exactly ONE primary focus:\n- Title scenes: product name\n- Problem scenes: the pain (red, chaotic)\n- Solution scenes: the result (green, spacious)\n- Feature scenes: the highlighted screenshot region\n- End scenes: URL \u002F CTA button\n\n### 4. Write narration\n\n- One idea per scene. If you need \"and\" you need two scenes.\n- Lead with the verb. \"Organize your tabs\" not \"Tab organization is provided.\"\n- No jargon. \"Your tabs organize themselves\" not \"AI-powered tab categorization.\"\n- Use contrast. \"24 tabs. One click. 5 groups.\"\n\n## Output Artifacts\n\nFor each video, produce these files in a `demo-output\u002F` directory:\n\n1. `scenes\u002F` — one HTML file per scene (1920x1080 viewport)\n2. `narration\u002F` — one `.txt` file per scene (for edge-tts input)\n3. `scenes.json` — manifest listing scenes in order with durations and narration text\n4. `build.sh` — shell script that runs the full pipeline:\n   - `playwright screenshot` each HTML scene → `frames\u002F`\n   - `edge-tts` each narration file → `audio\u002F`\n   - `ffmpeg` concat with crossfade transitions → `output.mp4`\n\nIf MCPs are unavailable, still produce items 1-3. Include the ffmpeg commands in `build.sh` for the user to run manually.\n\n## Scene Design System\n\nSee [references\u002Fscene-design-system.md](references\u002Fscene-design-system.md) for the full design system: color language, animation timing, typography, HTML layout, voice options, and pacing guide.\n\n## Quality Checklist\n\n- [ ] Video has audio stream\n- [ ] Resolution is 1920x1080\n- [ ] No black frames between scenes\n- [ ] First 3 seconds grab attention\n- [ ] Every scene has one focus point\n- [ ] End card has URL and CTA\n\n## Anti-Patterns\n\n| Anti-pattern | Fix |\n|---|---|\n| **Slideshow pacing** — every scene same duration, no rhythm | Vary durations: hooks 3s, proof 8s, CTA 4s |\n| **Wall of text on screen** | Move info to narration, simplify visuals |\n| **Generic narration** — \"This feature lets you...\" | Use specific numbers and concrete verbs |\n| **No story arc** — just listing features | Use problem -> solution -> proof structure |\n| **Raw screenshots** | Always add rounded corners, shadows, dark background |\n| **Using `ease` or `linear` animations** | Use spring curve: `cubic-bezier(0.16, 1, 0.3, 1)` |\n\n## Cross-References\n\n- Related: `engineering\u002Fbrowser-automation` — for playwright-based browser workflows\n- See also: [framecraft](https:\u002F\u002Fgithub.com\u002Fvaddisrinivas\u002Fframecraft) — open-source scene rendering pipeline\n",{"name":5,"description":7},"claude\u002Fregistry-repo-7lRiv","44e1a5b2d387b250bcd0794f7eb5e1228223d1e2","engineering\u002Fdemo-video\u002Fskills\u002Fdemo-video","https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills","https:\u002F\u002Fgithub.com\u002FMabbit143","I’m edgy and fun, probably too serious, but I love an adventure.","2026-09-22 07:56:32",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add Mabbit143\u002FClaude-SKills --skill demo-video",{"tool":37,"command":38},"bunx","bunx skills add Mabbit143\u002FClaude-SKills --skill demo-video",{"tool":40,"command":41},"pnpm","pnpm dlx skills add Mabbit143\u002FClaude-SKills --skill demo-video","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fengineering\u002Fdemo-video\u002Fskills\u002Fdemo-video\u002FSKILL.md",true,[45],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"references\u002Fscene-design-system.md","REFERENCE","参考文档",1622,"https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fengineering\u002Fdemo-video\u002Fskills\u002Fdemo-video\u002Freferences\u002Fscene-design-system.md",[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},"01M7D99ZA4F916M5CM3K2EQFE8","syllabus","Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Triggers whenever a user uploads a syllabus, course outline, or curriculum document and wants supplementary readings. Also triggers on: 'syllabus reading list', 'find papers for my course', 'create a reading list from this syllabus', 'recent research for my class', 'supplementary readings', 'find journal articles for these topics', 'what recent papers cover this material', 'any new research on these course topics', 'update my syllabus with recent papers'. Even casual mentions when a syllabus is attached should trigger this skill.","https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\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},"01M7D99ND4B38EG1BYQX722F5D","research","Default entry point for any research request — a hybrid router that classifies the question deterministically and either delegates to a specialist research skill (pulse for trends\u002Fsentiment, grants for NIH funding, litreview for academic literature, syllabus for course reading, patent for prior-art + IP landscape, dossier for entity research) or runs its own plan-decompose-multi-source-search-synthesize-cite fallback workflow when no specialist matches. Always surfaces the routing decision so users can override. Triggers — \"research [topic]\", \"look into [topic]\", \"what do we know about [topic]\", \"investigate [topic]\", \"find me information on [topic]\", \"do some research on [topic]\", \"I need to understand [topic]\", or any research request that doesn't obviously match a more-specific specialist skill. Output is a markdown briefing (default) or .docx document (on request) with full citations and an audit log.","https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fresearch\u002Fresearch\u002Fskills\u002Fresearch\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},"01M7D999VS936SV9TX940A98AQ","pulse","Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X\u002FTwitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend\u002Fsentiment\u002Fproblems\u002Fopportunities\u002Fcomparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Triggers: 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]', or any variation requesting multi-source recency intelligence on a topic. Also use for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.","https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\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},"01M7D98XBECS6368GEJNG8C1Z1","patent","Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search \u002F freedom-to-operate \u002F competitive landscape \u002F acquisition diligence \u002F litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Triggers: 'prior art search for [invention]', 'patent search on [topic]', 'freedom to operate analysis', 'FTO for [product]', 'patent landscape for [field]', 'is [invention] novel', 'patents on [topic]', 'competitive patent analysis', 'prior art for litigation', 'patent diligence on [company]'. Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.","https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\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},"01M7D98N2R7CA7RM00PNP4VV6C","notebooklm","Browser automation skill for controlling Google's NotebookLM. Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio Overview, infographics, slide decks, study guides, briefing docs, mind maps, timelines, FAQs), and creating new notebooks. Triggers on any phrase involving NotebookLM — 'open NotebookLM', 'check my [name] notebook', 'pull info from NotebookLM', 'ask my notebook about X', 'add [source] to NotebookLM', 'create an infographic in NotebookLM', 'use NotebookLM Studio', 'generate a slide deck from my notebook', or any variation where the goal involves NotebookLM. Requires browser automation environment — fails gracefully when unavailable.","https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fresearch\u002Fnotebooklm\u002Fskills\u002Fnotebooklm\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},"01M7D98B1SCTS4RAWZFCF9QJ5M","litreview","Academic literature orientation skill that searches papers via Consensus, builds a strategic search plan using PICO (default) or SPIDER \u002F Decomposition \u002F hybrid as fallbacks, and synthesizes findings into a professionally formatted Word document (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5\u002F10\u002F20 queries) controls coverage vs. speed. Output is a 'launching pad' — not a finished review, but an orientation guide that lets a researcher dive in confidently. Triggers: 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'. Do NOT trigger for single one-off paper searches where the user just wants a quick list — that's a plain Consensus search.","https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002FSKILL.md",[],[]]