[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M751JA0D94FX1RQBX3KNN7VC":3,"skill-same:01M751JA0D94FX1RQBX3KNN7VC":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},"01M751JA0D94FX1RQBX3KNN7VC","remotion-render",null,"Renders a Remotion composition to MP4 and runs the edit-and-re-render loop - CLI render commands, 1080p\u002F4K\u002F9:16 presets, concurrency tuning, codec selection, batch variants from a JSON data file, and Lambda for cloud rendering. Use when someone says \"render this Remotion video\", \"export the composition to MP4\", \"the animation is too fast, fix and re-render\", \"batch render one video per customer\", or \"move rendering to Lambda\". Do NOT use for authoring or restructuring scenes, animations, or components - use remotion-compose instead; do NOT use for project scaffolding and initial setup - use remotion-setup instead. This skill owns everything from a finished composition to a delivered file.","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-render\u002FSKILL.md",[],[],"2026-11-11 18:21:06",false,"---\nname: remotion-render\ndescription: Renders a Remotion composition to MP4 and runs the edit-and-re-render loop - CLI render commands, 1080p\u002F4K\u002F9:16 presets, concurrency tuning, codec selection, batch variants from a JSON data file, and Lambda for cloud rendering. Use when someone says \"render this Remotion video\", \"export the composition to MP4\", \"the animation is too fast, fix and re-render\", \"batch render one video per customer\", or \"move rendering to Lambda\". Do NOT use for authoring or restructuring scenes, animations, or components - use remotion-compose instead; do NOT use for project scaffolding and initial setup - use remotion-setup instead. This skill owns everything from a finished composition to a delivered file.\nmetadata:\n  title: \"Remotion Render\"\n---\n# Remotion Render\n\nDrive the render-and-iterate loop: turn a composition into an MP4, take natural-language feedback, make the smallest edit that satisfies it, and re-render. The costly failure mode is the opposite loop - rewriting whole scene files for a copy tweak, or re-rendering at full quality for every check - which destroys the approved work and the iteration speed that makes Remotion worth using.\n\n## Operating procedure\n\n### Step 1: Gather inputs\n\n- Composition ID (the `id` on the `\u003CComposition>` in `src\u002FRoot.tsx`, not a filename) and the entry point (the file calling `registerRoot`, typically `src\u002Findex.ts`).\n- Target: platform\u002Faspect (landscape 16:9, vertical 9:16, square), resolution (1080p default; 4K only on request), and whether transparency is needed.\n- Machine cores (for concurrency) and whether this is one render, an iteration session, or a batch.\n\n### Step 2: The base render\n\n```bash\nnpx remotion render src\u002Findex.ts \u003CCompositionId> out\u002Fvideo.mp4\n```\n\nDefault output is H.264 MP4 at the composition's own width\u002Fheight\u002Ffps; Remotion creates `out\u002F` if needed.\n\n### Step 3: Resolution, fps, and codec presets\n\nResolution and fps live on the `\u003CComposition>` (width\u002Fheight\u002Ffps) - change them at the source. Use flags only for scaling and container:\n\n```bash\n# 1080p landscape - Composition authored 1920x1080@30\nnpx remotion render src\u002Findex.ts ProductDemo out\u002F1080p.mp4\n\n# 4K - upscale the 1080p canvas without touching layout\nnpx remotion render src\u002Findex.ts ProductDemo out\u002F4k.mp4 --scale=2\n\n# 9:16 vertical - render a Composition authored at 1080x1920\nnpx remotion render src\u002Findex.ts ProductDemoVertical out\u002Fvertical.mp4\n```\n\nCodec rules:\n\n- Social\u002Fweb delivery stays H.264 MP4 (the default) - maximum compatibility.\n- Transparency: `--codec=vp8` or `vp9` (WebM), or `--codec=prores` with alpha for editing pipelines. H.264 cannot carry alpha.\n- True 60fps means `fps={60}` on the Composition with frame counts scaled to match - a flag-only fps change desyncs every animation timed in frames.\n\n### Step 4: Tune concurrency\n\nRendering is CPU-bound (each frame is a headless-Chromium screenshot). Default is roughly half the cores; explicit tuning is the easiest local speedup:\n\n```bash\nnpx remotion render src\u002Findex.ts ProductDemo out\u002Fvideo.mp4 --concurrency=8\n```\n\nStart at the number of physical cores (`--concurrency=50%` accepts a percentage); back off if the machine swaps or thermal-throttles - past the sweet spot, more Chromium tabs make it slower, not faster.\n\n### Step 5: Run the iterative refinement loop\n\nKeep Studio open (`npx remotion studio`, http:\u002F\u002Flocalhost:3000) so the user previews instantly; reserve full renders for sign-off.\n\n1. User previews in Studio and gives feedback in plain language.\n2. Translate it to a surgical edit - change only the relevant value:\n   - \"Too fast\" → widen the `interpolate` input range or raise spring `damping`.\n   - \"Logo should pop more\" → lower spring `damping` \u002F add overshoot.\n   - \"Change the CTA copy\" → edit the prop \u002F `defaultProps`, touch nothing else.\n   - \"Different accent color\" → change one hex in the colors object.\n   - \"Hold the last feature longer\" → bump that `\u003CSequence>`'s `durationInFrames` AND re-derive the Composition's total `durationInFrames`.\n3. Re-render, or let Studio hot-reload for the visual check.\n\nSurgical edit vs rewrite: edit in place when the change is a value, prop, color, or one scene's timing; rewrite only when scene *structure* changes (adding\u002Fremoving\u002Freordering scenes - and route structural authoring to remotion-compose). Default to surgical: it preserves everything already approved.\n\n### Step 6: Batch variants\n\nThe composition is data-driven, so N variants = N prop sets in a JSON file:\n\n```json\n[\n  { \"out\": \"out\u002Facme.mp4\",   \"props\": { \"logoText\": \"Acme\",   \"colors\": { \"accent\": \"#6C5CE7\" }, \"cta\": \"Try Acme\" } },\n  { \"out\": \"out\u002Fglobex.mp4\", \"props\": { \"logoText\": \"Globex\", \"colors\": { \"accent\": \"#00B894\" }, \"cta\": \"Try Globex\" } }\n]\n```\n\n`--props` takes inline JSON or a file path; for more than a couple of variants, write a small Node script that reads the JSON and shells out per entry, or use `@remotion\u002Frenderer`'s `renderMedia()` for a typed loop. Localize or A\u002FB copy and colors entirely by editing the JSON.\n\n### Step 7: Lambda when local is the bottleneck\n\nReach for Lambda when a single render takes minutes locally or the batch is large - it fans frames out across serverless workers. Otherwise local is simpler and free.\n\n```bash\nnpx remotion lambda functions deploy            # one-time per AWS account\u002Fregion\nnpx remotion lambda sites create src\u002Findex.ts --site-name=product-demo\nnpx remotion lambda render product-demo ProductDemo --props='{\"logoText\":\"Acme\"}'\n```\n\nRequires AWS credentials and IAM permissions per Remotion's Lambda setup.\n\n### Step 8: Troubleshoot the three common failures\n\n1. **Frame-count mismatch** - animation cuts off early or the clip has a dead tail. Cause: a `\u003CSequence>` duration changed but the Composition total did not. Fix: make the total equal the sum of its sequences; recompute after every timing edit. This is the #1 render surprise.\n2. **Missing `staticFile()` reference** - render fails or an asset is blank. Cause: an asset imported by path or outside `public\u002F`. Fix: put it in `public\u002Fassets\u002F` and reference `staticFile(\"assets\u002F\u003Cname>\")`.\n3. **Font flash\u002Ffallback** - text renders in the wrong font or shifts. Cause: `@remotion\u002Fgoogle-fonts` `loadFont()` missing or called too late. Fix: call `loadFont()` at module top level and apply the returned `fontFamily`; the render then waits for the font.\n\n## Deliverable\n\nA rendered file in `out\u002F` at the requested preset, plus - for iteration sessions - the loop offer: name the tweakable dimensions (pacing, copy, color, timing) and re-render on feedback. For batches, the variants JSON and the per-variant outputs.\n\n## Do NOT\n\n- Do NOT rewrite a scene file for a value-level change - surgical edits preserve approved work.\n- Do NOT change fps via flags alone - set it on the Composition and rescale frame counts.\n- Do NOT change a Sequence duration without re-deriving the Composition's total `durationInFrames`.\n- Do NOT full-render every iteration - Studio hot-reload is the preview loop; render at sign-off.\n- Do NOT push concurrency past physical cores on a machine that is swapping or throttling.\n- Do NOT reach for Lambda when local renders finish in seconds - it adds AWS setup and cost for nothing.\n- Do NOT author new scenes or restructure the composition here - that is remotion-compose.\n\n## Quality bar\n\n- The output plays at the requested resolution\u002Faspect\u002Ffps with no dead tail and no early cutoff (Composition total matches sequence sum).\n- Assets and fonts render correctly on the first frame - no fallback-font flash, no blank assets.\n- An iteration changed only the lines the feedback required; everything previously approved is untouched.\n- Batch outputs differ only by their prop sets.\n\n## Escalation\n\nScene authoring, animation design, and component structure go to remotion-compose; project scaffolding to remotion-setup; scoring and audio timing to sound-and-music-sync.\n","# Remotion Render\n\nDrive the render-and-iterate loop: turn a composition into an MP4, take natural-language feedback, make the smallest edit that satisfies it, and re-render. The costly failure mode is the opposite loop - rewriting whole scene files for a copy tweak, or re-rendering at full quality for every check - which destroys the approved work and the iteration speed that makes Remotion worth using.\n\n## Operating procedure\n\n### Step 1: Gather inputs\n\n- Composition ID (the `id` on the `\u003CComposition>` in `src\u002FRoot.tsx`, not a filename) and the entry point (the file calling `registerRoot`, typically `src\u002Findex.ts`).\n- Target: platform\u002Faspect (landscape 16:9, vertical 9:16, square), resolution (1080p default; 4K only on request), and whether transparency is needed.\n- Machine cores (for concurrency) and whether this is one render, an iteration session, or a batch.\n\n### Step 2: The base render\n\n```bash\nnpx remotion render src\u002Findex.ts \u003CCompositionId> out\u002Fvideo.mp4\n```\n\nDefault output is H.264 MP4 at the composition's own width\u002Fheight\u002Ffps; Remotion creates `out\u002F` if needed.\n\n### Step 3: Resolution, fps, and codec presets\n\nResolution and fps live on the `\u003CComposition>` (width\u002Fheight\u002Ffps) - change them at the source. Use flags only for scaling and container:\n\n```bash\n# 1080p landscape - Composition authored 1920x1080@30\nnpx remotion render src\u002Findex.ts ProductDemo out\u002F1080p.mp4\n\n# 4K - upscale the 1080p canvas without touching layout\nnpx remotion render src\u002Findex.ts ProductDemo out\u002F4k.mp4 --scale=2\n\n# 9:16 vertical - render a Composition authored at 1080x1920\nnpx remotion render src\u002Findex.ts ProductDemoVertical out\u002Fvertical.mp4\n```\n\nCodec rules:\n\n- Social\u002Fweb delivery stays H.264 MP4 (the default) - maximum compatibility.\n- Transparency: `--codec=vp8` or `vp9` (WebM), or `--codec=prores` with alpha for editing pipelines. H.264 cannot carry alpha.\n- True 60fps means `fps={60}` on the Composition with frame counts scaled to match - a flag-only fps change desyncs every animation timed in frames.\n\n### Step 4: Tune concurrency\n\nRendering is CPU-bound (each frame is a headless-Chromium screenshot). Default is roughly half the cores; explicit tuning is the easiest local speedup:\n\n```bash\nnpx remotion render src\u002Findex.ts ProductDemo out\u002Fvideo.mp4 --concurrency=8\n```\n\nStart at the number of physical cores (`--concurrency=50%` accepts a percentage); back off if the machine swaps or thermal-throttles - past the sweet spot, more Chromium tabs make it slower, not faster.\n\n### Step 5: Run the iterative refinement loop\n\nKeep Studio open (`npx remotion studio`, http:\u002F\u002Flocalhost:3000) so the user previews instantly; reserve full renders for sign-off.\n\n1. User previews in Studio and gives feedback in plain language.\n2. Translate it to a surgical edit - change only the relevant value:\n   - \"Too fast\" → widen the `interpolate` input range or raise spring `damping`.\n   - \"Logo should pop more\" → lower spring `damping` \u002F add overshoot.\n   - \"Change the CTA copy\" → edit the prop \u002F `defaultProps`, touch nothing else.\n   - \"Different accent color\" → change one hex in the colors object.\n   - \"Hold the last feature longer\" → bump that `\u003CSequence>`'s `durationInFrames` AND re-derive the Composition's total `durationInFrames`.\n3. Re-render, or let Studio hot-reload for the visual check.\n\nSurgical edit vs rewrite: edit in place when the change is a value, prop, color, or one scene's timing; rewrite only when scene *structure* changes (adding\u002Fremoving\u002Freordering scenes - and route structural authoring to remotion-compose). Default to surgical: it preserves everything already approved.\n\n### Step 6: Batch variants\n\nThe composition is data-driven, so N variants = N prop sets in a JSON file:\n\n```json\n[\n  { \"out\": \"out\u002Facme.mp4\",   \"props\": { \"logoText\": \"Acme\",   \"colors\": { \"accent\": \"#6C5CE7\" }, \"cta\": \"Try Acme\" } },\n  { \"out\": \"out\u002Fglobex.mp4\", \"props\": { \"logoText\": \"Globex\", \"colors\": { \"accent\": \"#00B894\" }, \"cta\": \"Try Globex\" } }\n]\n```\n\n`--props` takes inline JSON or a file path; for more than a couple of variants, write a small Node script that reads the JSON and shells out per entry, or use `@remotion\u002Frenderer`'s `renderMedia()` for a typed loop. Localize or A\u002FB copy and colors entirely by editing the JSON.\n\n### Step 7: Lambda when local is the bottleneck\n\nReach for Lambda when a single render takes minutes locally or the batch is large - it fans frames out across serverless workers. Otherwise local is simpler and free.\n\n```bash\nnpx remotion lambda functions deploy            # one-time per AWS account\u002Fregion\nnpx remotion lambda sites create src\u002Findex.ts --site-name=product-demo\nnpx remotion lambda render product-demo ProductDemo --props='{\"logoText\":\"Acme\"}'\n```\n\nRequires AWS credentials and IAM permissions per Remotion's Lambda setup.\n\n### Step 8: Troubleshoot the three common failures\n\n1. **Frame-count mismatch** - animation cuts off early or the clip has a dead tail. Cause: a `\u003CSequence>` duration changed but the Composition total did not. Fix: make the total equal the sum of its sequences; recompute after every timing edit. This is the #1 render surprise.\n2. **Missing `staticFile()` reference** - render fails or an asset is blank. Cause: an asset imported by path or outside `public\u002F`. Fix: put it in `public\u002Fassets\u002F` and reference `staticFile(\"assets\u002F\u003Cname>\")`.\n3. **Font flash\u002Ffallback** - text renders in the wrong font or shifts. Cause: `@remotion\u002Fgoogle-fonts` `loadFont()` missing or called too late. Fix: call `loadFont()` at module top level and apply the returned `fontFamily`; the render then waits for the font.\n\n## Deliverable\n\nA rendered file in `out\u002F` at the requested preset, plus - for iteration sessions - the loop offer: name the tweakable dimensions (pacing, copy, color, timing) and re-render on feedback. For batches, the variants JSON and the per-variant outputs.\n\n## Do NOT\n\n- Do NOT rewrite a scene file for a value-level change - surgical edits preserve approved work.\n- Do NOT change fps via flags alone - set it on the Composition and rescale frame counts.\n- Do NOT change a Sequence duration without re-deriving the Composition's total `durationInFrames`.\n- Do NOT full-render every iteration - Studio hot-reload is the preview loop; render at sign-off.\n- Do NOT push concurrency past physical cores on a machine that is swapping or throttling.\n- Do NOT reach for Lambda when local renders finish in seconds - it adds AWS setup and cost for nothing.\n- Do NOT author new scenes or restructure the composition here - that is remotion-compose.\n\n## Quality bar\n\n- The output plays at the requested resolution\u002Faspect\u002Ffps with no dead tail and no early cutoff (Composition total matches sequence sum).\n- Assets and fonts render correctly on the first frame - no fallback-font flash, no blank assets.\n- An iteration changed only the lines the feedback required; everything previously approved is untouched.\n- Batch outputs differ only by their prop sets.\n\n## Escalation\n\nScene authoring, animation design, and component structure go to remotion-compose; project scaffolding to remotion-setup; scoring and audio timing to sound-and-music-sync.\n",{"name":5,"metadata":24,"description":7},{"title":25},"Remotion Render","main","97a13607d669157a4a16d5ba79b77f208319f7b9","skills\u002Fremotion-render",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-render",{"tool":41,"command":42},"bunx","bunx skills add SkillMedev\u002Fskills --skill remotion-render",{"tool":44,"command":45},"pnpm","pnpm dlx skills add SkillMedev\u002Fskills --skill remotion-render","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSkillMedev\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fremotion-render\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",[],[]]