[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M751JG0PH4ES5DHSJKMSJB9J":3,"skill-same:01M751JG0PH4ES5DHSJKMSJB9J":49},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":31,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M751JG0PH4ES5DHSJKMSJB9J","remotion-setup",null,"Scaffolds a new Remotion video project wired for Claude Code Agent Skills - Node check, create-video scaffold, skills install, folder conventions, Google Fonts, and a smoke-test render. Use whenever someone wants to start making videos with Remotion and Claude, even just \"make product videos with Claude.\"","SkillMedev\u002Fskills","SkillMedev","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F298078254?v=4","01M74ZSGTQ918CB0VXW4EG3RMX","SkillMe","01M74ZSGVBT497NA95CBT8JTY4",25,"MIT","https:\u002F\u002Fgithub.com\u002FSkillMedev\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fremotion-setup\u002FSKILL.md",[],[],"2026-11-11 18:21:06",false,"---\nname: remotion-setup\ndescription: Scaffolds a new Remotion video project wired for Claude Code Agent Skills - Node check, create-video scaffold, skills install, folder conventions, Google Fonts, and a smoke-test render. Use whenever someone wants to start making videos with Remotion and Claude, even just \"make product videos with Claude.\"\nmetadata:\n  title: \"Remotion Setup\"\n---\n# Remotion Setup\n\nYou scaffold a fresh **Remotion** project and wire it so the rest of the workflow\nis \"just prompt Claude.\" This is the one-time environment work. Do it once per\nproject; afterward `remotion-compose` and `remotion-render` skip straight to the\ncreative loop.\n\nTrigger eagerly. If the user says anything about *making videos with Claude* -\n\"set up Remotion,\" \"create a Remotion project,\" \"I want to make product videos\nwith Claude,\" \"start a video project\" - run this skill.\n\n## Step 1 - Verify the toolchain\n\nRemotion renders with headless Chromium, so check Node before scaffolding:\n\n```bash\nnode --version   # need >= 16; prefer an active LTS release\n```\n\nIf Node is older than 16, stop and tell the user to upgrade (nvm: `nvm install --lts && nvm use --lts`).\nAlso confirm `npx` is available (ships with npm 5.2+).\n\n## Step 2 - Scaffold the project\n\n```bash\nnpx create-video@latest\n```\n\nThis is interactive. Recommend the **Blank** (Hello World) template - it is the\ncleanest base for product videos. The CLI asks for a project directory and a\npackage manager; let the user pick, then `cd` into the new folder and install:\n\n```bash\ncd \u003Cproject-name>\nnpm install\n```\n\n## Step 3 - Install the Remotion Agent Skills\n\nSo Claude Code has Remotion's own skill context available in this repo:\n\n```bash\nnpx remotion skills add remotion\n```\n\nThis drops Remotion's agent-skill files into the project. If the command is\nunavailable in the installed Remotion version, point the user at a newer\n`@remotion\u002Fcli` and continue - it is a convenience, not a hard dependency.\n\n## Step 4 - Establish folder conventions\n\nStandardize the layout so later skills always know where things go:\n\n```\nsrc\u002F\n  Root.tsx              # registers every \u003CComposition> (the entry registry)\n  index.ts              # registerRoot(RemotionRoot)\n  compositions\u002F         # one .tsx file per video - remotion-compose writes here\npublic\u002F\n  assets\u002F               # images, logos, audio - referenced via staticFile()\n```\n\nCreate the folders if the template did not:\n\n```bash\nmkdir -p src\u002Fcompositions public\u002Fassets\n```\n\n`src\u002FRoot.tsx` is the registry. Every video is a `\u003CComposition>` registered here:\n\n```tsx\n\u002F\u002F src\u002FRoot.tsx\nimport { Composition } from \"remotion\";\nimport { HelloWorld } from \".\u002Fcompositions\u002FHelloWorld\";\n\nexport const RemotionRoot: React.FC = () => {\n  return (\n    \u003CComposition\n      id=\"HelloWorld\"\n      component={HelloWorld}\n      durationInFrames={90}\n      fps={30}\n      width={1920}\n      height={1080}\n    \u002F>\n  );\n};\n```\n\n```ts\n\u002F\u002F src\u002Findex.ts\nimport { registerRoot } from \"remotion\";\nimport { RemotionRoot } from \".\u002FRoot\";\nregisterRoot(RemotionRoot);\n```\n\nSensible defaults to register with: 30 fps and 1920x1080 for landscape product\nvideos (1080x1920 for vertical social), and short durations - 90 frames at\n30 fps is 3 seconds, and most product demo videos land between 15 and 60\nseconds (450-1800 frames).\n\n## Step 5 - Load a Google font\n\nRemotion has first-class Google Fonts so text renders deterministically. Install\nand load once:\n\n```bash\nnpm install @remotion\u002Fgoogle-fonts\n```\n\n```tsx\n\u002F\u002F load near the top of a composition file\nimport { loadFont } from \"@remotion\u002Fgoogle-fonts\u002FInter\";\nconst { fontFamily } = loadFont();\n\u002F\u002F then use: \u003Cdiv style={{ fontFamily }}>...\u003C\u002Fdiv>\n```\n\n`loadFont()` blocks the render until the font is ready, so on-screen text never\nflashes in an unstyled fallback. Pick the font that matches the brand - swap\n`Inter` for `Poppins`, `Roboto`, etc.\n\n## Step 6 - Smoke-test composition\n\nWrite a trivial composition to prove the environment renders end to end:\n\n```tsx\n\u002F\u002F src\u002Fcompositions\u002FHelloWorld.tsx\nimport { AbsoluteFill, useCurrentFrame, interpolate } from \"remotion\";\nimport { loadFont } from \"@remotion\u002Fgoogle-fonts\u002FInter\";\n\nconst { fontFamily } = loadFont();\n\nexport const HelloWorld: React.FC = () => {\n  const frame = useCurrentFrame();\n  const opacity = interpolate(frame, [0, 30], [0, 1], {\n    extrapolateRight: \"clamp\",\n  });\n  return (\n    \u003CAbsoluteFill style={{ backgroundColor: \"#0B0B0F\", justifyContent: \"center\", alignItems: \"center\" }}>\n      \u003Ch1 style={{ fontFamily, color: \"white\", fontSize: 90, opacity }}>\n        It works.\n      \u003C\u002Fh1>\n    \u003C\u002FAbsoluteFill>\n  );\n};\n```\n\nMake sure it is registered in `src\u002FRoot.tsx` (Step 4), then render it:\n\n```bash\nnpx remotion render src\u002Findex.ts HelloWorld out\u002Fsmoke-test.mp4\n```\n\nThe first render downloads headless Chromium (a few hundred MB - expect a one-time\nwait of a few minutes on a normal connection); after that, this 90-frame smoke test\nshould render in well under a minute. If `out\u002Fsmoke-test.mp4` plays a fading-in\ntitle, the environment is good. If the render fails, it is almost always\n(a) Chromium download\u002Fpermissions, (b) the composition not registered in\n`Root.tsx`, or (c) a Node version issue from Step 1.\n\n## Step 7 - Launch Remotion Studio for preview\n\nFor the interactive preview (scrub the timeline, hot-reload on edits):\n\n```bash\nnpx remotion studio\n```\n\nThis serves the Studio at **http:\u002F\u002Flocalhost:3000**. The `create-video` template\nalso wires `npm run dev` to the same thing. Leave Studio running while iterating -\nedits to composition files hot-reload instantly.\n\n## Deliverable\n\nThe user walks away with a working Remotion project: the scaffolded repo with the\n`src\u002Fcompositions\u002F` + `public\u002Fassets\u002F` layout in place, Remotion agent skills\ninstalled, a Google font wired, a registered smoke-test composition, a rendered\n`out\u002Fsmoke-test.mp4` that actually plays, and Remotion Studio running for preview.\nNothing is \"set up\" until the smoke-test MP4 exists and plays.\n\n## Do NOT\n\n- Do not skip the Node check and scaffold anyway - a sub-16 Node fails deep inside the Chromium render with a confusing error, not at install time.\n- Do not declare setup done without rendering the smoke test; a project that compiles but has never produced an MP4 has not proven the Chromium pipeline works.\n- Do not put compositions or assets in ad-hoc locations - later skills (`remotion-compose`, `remotion-render`) rely on `src\u002Fcompositions\u002F` and `public\u002Fassets\u002F` existing.\n- Do not reference assets by relative path or URL; use `staticFile()` from `public\u002F`, or renders will work locally and break elsewhere.\n- Do not use system or CSS-imported fonts for on-screen text - without `loadFont()` blocking, text can render in a fallback font on the render machine.\n- Do not pick a feature-heavy template for product videos; the Blank template avoids carrying demo code the user must delete later.\n\n## Quality bar\n\n- `node --version` is >= 16 and was checked before scaffolding.\n- `out\u002Fsmoke-test.mp4` exists and plays a fading-in title.\n- The folder conventions exist exactly as specified, and the smoke composition is registered in `src\u002FRoot.tsx`.\n- Text renders through `@remotion\u002Fgoogle-fonts` with `loadFont()`, not a system fallback.\n- Remotion Studio launches at localhost:3000 and hot-reloads an edit.\n\n## Handoff\n\nOnce the smoke test renders and Studio is up, tell the user the project is ready\nand hand off: *\"Setup is done. Describe the video you want - duration, scenes,\nbrand colors - and I'll write the composition (`remotion-compose`), then render\nand iterate (`remotion-render`).\"*\n","# Remotion Setup\n\nYou scaffold a fresh **Remotion** project and wire it so the rest of the workflow\nis \"just prompt Claude.\" This is the one-time environment work. Do it once per\nproject; afterward `remotion-compose` and `remotion-render` skip straight to the\ncreative loop.\n\nTrigger eagerly. If the user says anything about *making videos with Claude* -\n\"set up Remotion,\" \"create a Remotion project,\" \"I want to make product videos\nwith Claude,\" \"start a video project\" - run this skill.\n\n## Step 1 - Verify the toolchain\n\nRemotion renders with headless Chromium, so check Node before scaffolding:\n\n```bash\nnode --version   # need >= 16; prefer an active LTS release\n```\n\nIf Node is older than 16, stop and tell the user to upgrade (nvm: `nvm install --lts && nvm use --lts`).\nAlso confirm `npx` is available (ships with npm 5.2+).\n\n## Step 2 - Scaffold the project\n\n```bash\nnpx create-video@latest\n```\n\nThis is interactive. Recommend the **Blank** (Hello World) template - it is the\ncleanest base for product videos. The CLI asks for a project directory and a\npackage manager; let the user pick, then `cd` into the new folder and install:\n\n```bash\ncd \u003Cproject-name>\nnpm install\n```\n\n## Step 3 - Install the Remotion Agent Skills\n\nSo Claude Code has Remotion's own skill context available in this repo:\n\n```bash\nnpx remotion skills add remotion\n```\n\nThis drops Remotion's agent-skill files into the project. If the command is\nunavailable in the installed Remotion version, point the user at a newer\n`@remotion\u002Fcli` and continue - it is a convenience, not a hard dependency.\n\n## Step 4 - Establish folder conventions\n\nStandardize the layout so later skills always know where things go:\n\n```\nsrc\u002F\n  Root.tsx              # registers every \u003CComposition> (the entry registry)\n  index.ts              # registerRoot(RemotionRoot)\n  compositions\u002F         # one .tsx file per video - remotion-compose writes here\npublic\u002F\n  assets\u002F               # images, logos, audio - referenced via staticFile()\n```\n\nCreate the folders if the template did not:\n\n```bash\nmkdir -p src\u002Fcompositions public\u002Fassets\n```\n\n`src\u002FRoot.tsx` is the registry. Every video is a `\u003CComposition>` registered here:\n\n```tsx\n\u002F\u002F src\u002FRoot.tsx\nimport { Composition } from \"remotion\";\nimport { HelloWorld } from \".\u002Fcompositions\u002FHelloWorld\";\n\nexport const RemotionRoot: React.FC = () => {\n  return (\n    \u003CComposition\n      id=\"HelloWorld\"\n      component={HelloWorld}\n      durationInFrames={90}\n      fps={30}\n      width={1920}\n      height={1080}\n    \u002F>\n  );\n};\n```\n\n```ts\n\u002F\u002F src\u002Findex.ts\nimport { registerRoot } from \"remotion\";\nimport { RemotionRoot } from \".\u002FRoot\";\nregisterRoot(RemotionRoot);\n```\n\nSensible defaults to register with: 30 fps and 1920x1080 for landscape product\nvideos (1080x1920 for vertical social), and short durations - 90 frames at\n30 fps is 3 seconds, and most product demo videos land between 15 and 60\nseconds (450-1800 frames).\n\n## Step 5 - Load a Google font\n\nRemotion has first-class Google Fonts so text renders deterministically. Install\nand load once:\n\n```bash\nnpm install @remotion\u002Fgoogle-fonts\n```\n\n```tsx\n\u002F\u002F load near the top of a composition file\nimport { loadFont } from \"@remotion\u002Fgoogle-fonts\u002FInter\";\nconst { fontFamily } = loadFont();\n\u002F\u002F then use: \u003Cdiv style={{ fontFamily }}>...\u003C\u002Fdiv>\n```\n\n`loadFont()` blocks the render until the font is ready, so on-screen text never\nflashes in an unstyled fallback. Pick the font that matches the brand - swap\n`Inter` for `Poppins`, `Roboto`, etc.\n\n## Step 6 - Smoke-test composition\n\nWrite a trivial composition to prove the environment renders end to end:\n\n```tsx\n\u002F\u002F src\u002Fcompositions\u002FHelloWorld.tsx\nimport { AbsoluteFill, useCurrentFrame, interpolate } from \"remotion\";\nimport { loadFont } from \"@remotion\u002Fgoogle-fonts\u002FInter\";\n\nconst { fontFamily } = loadFont();\n\nexport const HelloWorld: React.FC = () => {\n  const frame = useCurrentFrame();\n  const opacity = interpolate(frame, [0, 30], [0, 1], {\n    extrapolateRight: \"clamp\",\n  });\n  return (\n    \u003CAbsoluteFill style={{ backgroundColor: \"#0B0B0F\", justifyContent: \"center\", alignItems: \"center\" }}>\n      \u003Ch1 style={{ fontFamily, color: \"white\", fontSize: 90, opacity }}>\n        It works.\n      \u003C\u002Fh1>\n    \u003C\u002FAbsoluteFill>\n  );\n};\n```\n\nMake sure it is registered in `src\u002FRoot.tsx` (Step 4), then render it:\n\n```bash\nnpx remotion render src\u002Findex.ts HelloWorld out\u002Fsmoke-test.mp4\n```\n\nThe first render downloads headless Chromium (a few hundred MB - expect a one-time\nwait of a few minutes on a normal connection); after that, this 90-frame smoke test\nshould render in well under a minute. If `out\u002Fsmoke-test.mp4` plays a fading-in\ntitle, the environment is good. If the render fails, it is almost always\n(a) Chromium download\u002Fpermissions, (b) the composition not registered in\n`Root.tsx`, or (c) a Node version issue from Step 1.\n\n## Step 7 - Launch Remotion Studio for preview\n\nFor the interactive preview (scrub the timeline, hot-reload on edits):\n\n```bash\nnpx remotion studio\n```\n\nThis serves the Studio at **http:\u002F\u002Flocalhost:3000**. The `create-video` template\nalso wires `npm run dev` to the same thing. Leave Studio running while iterating -\nedits to composition files hot-reload instantly.\n\n## Deliverable\n\nThe user walks away with a working Remotion project: the scaffolded repo with the\n`src\u002Fcompositions\u002F` + `public\u002Fassets\u002F` layout in place, Remotion agent skills\ninstalled, a Google font wired, a registered smoke-test composition, a rendered\n`out\u002Fsmoke-test.mp4` that actually plays, and Remotion Studio running for preview.\nNothing is \"set up\" until the smoke-test MP4 exists and plays.\n\n## Do NOT\n\n- Do not skip the Node check and scaffold anyway - a sub-16 Node fails deep inside the Chromium render with a confusing error, not at install time.\n- Do not declare setup done without rendering the smoke test; a project that compiles but has never produced an MP4 has not proven the Chromium pipeline works.\n- Do not put compositions or assets in ad-hoc locations - later skills (`remotion-compose`, `remotion-render`) rely on `src\u002Fcompositions\u002F` and `public\u002Fassets\u002F` existing.\n- Do not reference assets by relative path or URL; use `staticFile()` from `public\u002F`, or renders will work locally and break elsewhere.\n- Do not use system or CSS-imported fonts for on-screen text - without `loadFont()` blocking, text can render in a fallback font on the render machine.\n- Do not pick a feature-heavy template for product videos; the Blank template avoids carrying demo code the user must delete later.\n\n## Quality bar\n\n- `node --version` is >= 16 and was checked before scaffolding.\n- `out\u002Fsmoke-test.mp4` exists and plays a fading-in title.\n- The folder conventions exist exactly as specified, and the smoke composition is registered in `src\u002FRoot.tsx`.\n- Text renders through `@remotion\u002Fgoogle-fonts` with `loadFont()`, not a system fallback.\n- Remotion Studio launches at localhost:3000 and hot-reloads an edit.\n\n## Handoff\n\nOnce the smoke test renders and Studio is up, tell the user the project is ready\nand hand off: *\"Setup is done. Describe the video you want - duration, scenes,\nbrand colors - and I'll write the composition (`remotion-compose`), then render\nand iterate (`remotion-render`).\"*\n",{"name":5,"metadata":24,"description":7},{"title":25},"Remotion Setup","main","97a13607d669157a4a16d5ba79b77f208319f7b9","skills\u002Fremotion-setup",3,"https:\u002F\u002Fgithub.com\u002FSkillMedev\u002Fskills","https:\u002F\u002Fskillme.dev","https:\u002F\u002Fgithub.com\u002FSkillMedev","MCP-native catalog of Claude Agent Skills. Browse, recommend, install, and auto-apply skills in chat. Open source, every skill free and clonable on GitHub.","2026-10-14 03:19:31",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add SkillMedev\u002Fskills --skill remotion-setup",{"tool":41,"command":42},"bunx","bunx skills add SkillMedev\u002Fskills --skill remotion-setup",{"tool":44,"command":45},"pnpm","pnpm dlx skills add SkillMedev\u002Fskills --skill remotion-setup","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSkillMedev\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fremotion-setup\u002FSKILL.md",true,[],[50,60,67,74,81,88],{"skillNo":51,"name":52,"nameZh":53,"description":54,"descriptionZh":55,"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":59},"01M75271B256DF3FX2VG5VRYEE","zone-2-cardio-plan","有氧运动计划","Use when someone asks to build a steady-state cardio plan, train an aerobic base or Zone 2, structure easy or endurance weekly cardio, train by heart-rate zones, or improve resting heart rate, VO2, or endurance. Builds a heart-rate-zone aerobic training block with session structure, modality choice, and progression. General fitness guidance, not medical advice. Do NOT use to design a strength or lifting program (use Strength Training Plan), high-intensity interval conditioning, HIIT, or circuits (use Conditioning & HIIT Program), or a mobility\u002Fflexibility routine (use Mobility Routine).","当有人要求制定稳态有氧训练计划、进行有氧基础训练或达到第二区间、安排轻松或耐力型的每周有氧训练、按心率区间训练，或提高静息心率、最大摄氧量或耐力时，可以使用此方案。该方案构建了一个包含训练计划结构、训练方式选择和进度安排的心率区间有氧训练模块。本方案仅提供一般健身指导，不构成医疗建议。请勿用于设计力量或举重训练计划（请使用力量训练计划）、高强度间歇训练 (HIIT) 或循环训练（请使用体能训练和 HIIT 计划），或灵活性\u002F柔韧性训练（请使用灵活性训练计划）。","https:\u002F\u002Fgithub.com\u002FSkillMedev\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fzone-2-cardio-plan\u002FSKILL.md",[],[],"2026-11-11 18:27:18",{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":59},"01M7526VP1QBBKYBE17S1WR86Y","youtube-script-writer","Writes retention-engineered long-form YouTube scripts on a hook\u002Fbody\u002Fpayoff architecture - a first-30-seconds hook that survives the retention cliff, a beat-sheet body with mini-hooks and bridges, timed pattern interrupts, and a payoff that over-delivers - with B-roll and editing cues marked inline. Use when someone says \"script my next video\", \"my retention graph dies at the start\", \"tighten this draft\", or \"outline a video on X\". Do NOT use for the 3-second opener of TikTok, Reels, or Shorts - use video-hook-writer instead; do NOT use for spoken voiceover synced to on-screen tutorial actions - use narration-script instead; do NOT use for a sales demo built on a buyer's discovery notes - use demo-script instead; do NOT use to design the thumbnail and title - use thumbnail-concept instead.","https:\u002F\u002Fgithub.com\u002FSkillMedev\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube-script-writer\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":59},"01M7526P2T0WKMHDXS4Q58237T","win-back-campaign","Designs segmented win-back email sequences for dormant users - dormancy tiers, a three-beat sequence with a single proportional incentive, and a suppression rule - and measures success by re-activation, not opens. Use when someone says \"our users went quiet\", \"design a win-back campaign\", \"how do I re-engage lapsed customers\", \"should we email people who haven't logged in for months\", or lifecycle messaging has stopped landing with a lapsed segment. Do NOT use for recovering an unfinished checkout - use abandoned-cart-sequence instead. Do NOT use for diagnosing and fixing why active customers cancel - use churn-reduction instead. Do NOT use for building always-on onboarding or nurture flows - use email-drip-builder instead.","https:\u002F\u002Fgithub.com\u002FSkillMedev\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwin-back-campaign\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":59},"01M7526HF2RCDJ50P93WRZRHVV","wikipedia-style","Writes neutral, verifiable, encyclopedic prose following Wikipedia's core content policies and manual of style - NPOV, inline citations, notability-backed claims, and a strict ban on promotional language. Use when someone asks \"write this like a Wikipedia article\", \"draft a Wikipedia page for this company or person\", \"make this neutral and encyclopedic\", or \"why does my article draft keep getting rejected\". Do NOT use for persuasive or opinion writing - use op-ed-writer instead; for thesis-driven academic papers, use academic-essay; for verifying claims in existing text, use fact-checker.","https:\u002F\u002Fgithub.com\u002FSkillMedev\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwikipedia-style\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":59},"01M7526D43CTGRKGKNQ2GB0KVX","whitepapers","Structures and writes authoritative B2B whitepapers - a standalone executive summary, a data-sized problem statement, methodology, evidence-driven findings, recommendations, and a soft call to action - flagging every claim that needs a real citation. Use when a marketer asks \"write a whitepaper on this topic\", \"turn our research into a lead-gen asset\", \"make this credible enough for executives\", or a draft reads like a product pitch instead of analysis. Do NOT use for customer-story-driven proof - use case-study-builder instead; for policy audiences, use policy-brief.","https:\u002F\u002Fgithub.com\u002FSkillMedev\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwhitepapers\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":59},"01M75268423Y3K50SY5WC2NX2G","white-space-analysis","Finds unmet market gaps by ranking jobs-to-be-done on importance versus satisfaction, overlaying them against current solutions and workarounds, and validating that each gap is real, winnable, and worth winning. Use when someone asks \"where are the gaps in this market\", \"what's underserved here\", \"where should we play next\", or is hunting for product, feature, or market-entry opportunities. Do NOT use for profiling competitors and building battle cards - use competitive-intelligence instead; for putting a dollar figure on an identified opportunity - use market-sizing instead; for extracting jobs-to-be-done from raw customer interviews - use jtbd-extractor instead.","https:\u002F\u002Fgithub.com\u002FSkillMedev\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwhite-space-analysis\u002FSKILL.md",[],[]]