[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M751WMWR8ZGFH3XYKM8DMSZ9":3,"skill-same:01M751WMWR8ZGFH3XYKM8DMSZ9":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},"01M751WMWR8ZGFH3XYKM8DMSZ9","stock-photo-finder",null,"Source the right stock photograph for a brief by picking the best library and crafting the search. Use when you need a real photo or image for a hero, blog post, ad, slide, mockup, social post, or thumbnail and you are not sure where to look or what to search, or when someone says \"find me a photo of...\", \"where do I get images for this\", \"I need a hero image\", or \"good free stock photos for X\". It covers free libraries (Unsplash, Pexels, Pixabay), curated and boutique sources (Stocksy, Stills, Death to Stock), broad paid catalogs (Adobe Stock, Shutterstock, iStock), and editorial archives (Getty, AP, Reuters). Do NOT use to decide whether a license actually permits your use or whether you need a release -> use image-license-rights; do NOT use to fetch images programmatically in code -> use stock-photo-api; do NOT use to art-direct a cohesive set or fix a cliched look -> use visual-asset-curation.","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\u002Fstock-photo-finder\u002FSKILL.md",[],[],"2026-11-11 18:22:23",false,"---\nname: stock-photo-finder\ndescription: Source the right stock photograph for a brief by picking the best library and crafting the search. Use when you need a real photo or image for a hero, blog post, ad, slide, mockup, social post, or thumbnail and you are not sure where to look or what to search, or when someone says \"find me a photo of...\", \"where do I get images for this\", \"I need a hero image\", or \"good free stock photos for X\". It covers free libraries (Unsplash, Pexels, Pixabay), curated and boutique sources (Stocksy, Stills, Death to Stock), broad paid catalogs (Adobe Stock, Shutterstock, iStock), and editorial archives (Getty, AP, Reuters). Do NOT use to decide whether a license actually permits your use or whether you need a release -> use image-license-rights; do NOT use to fetch images programmatically in code -> use stock-photo-api; do NOT use to art-direct a cohesive set or fix a cliched look -> use visual-asset-curation.\nmetadata:\n  title: \"Find the Right Stock Photo\"\n---\n\n# Find the Right Stock Photo\n\nThis skill gets you from \"I need an image of X\" to a short list of strong\ncandidates from the *right* source. It owns two decisions: **which library to\nsearch** and **what to type into it**. It does not decide whether you may legally\nuse the result (that is `image-license-rights`), it does not fetch images in code\n(that is `stock-photo-api`), and it does not turn a pile of candidates into a\ncohesive, on-brand set (that is `visual-asset-curation`).\n\n## When to use a sibling instead\n\n- **\"Can I legally use this? Do I need attribution or a model release?\"** ->\n  **image-license-rights**. Always run it before you ship anything commercial.\n- **\"Pull stock photos into my app \u002F script automatically.\"** ->\n  **stock-photo-api**.\n- **\"I have ten options, which ones and in what order, and why do they look\n  cheap?\"** -> **visual-asset-curation**.\n\n## Step 1: Write the one-line visual brief\n\nNever search before you can fill this in. Vague searches return the most generic,\nmost-used (most cliched) images on the platform.\n\n- **Subject** - the concrete noun (\"a barista steaming milk\", not \"coffee\").\n- **Context \u002F setting** - where it happens (\"small independent cafe, morning light\").\n- **Mood \u002F emotion** - \"calm and focused\", \"energetic\", \"quiet luxury\".\n- **Use + placement** - hero banner, blog inline, ad, slide background. This sets\n  orientation and resolution.\n- **Commercial or editorial** - is it selling something (commercial) or\n  illustrating a story\u002Fnews (editorial)? This changes which sources are even\n  legal. Hand the call to **image-license-rights** if unsure.\n- **Budget** - free-only, or is paid on the table?\n\n## Step 2: Pick the source by use case\n\nMatch the brief to a library before you search. The order below is the default\ndecision path.\n\n- **Free, general-purpose, fast** -> **Unsplash, Pexels, Pixabay.** Huge free\n  catalogs, generous licenses, no cost. Trade-off: the popular shots are heavily\n  reused - a first-page result on these platforms can have hundreds of thousands\n  of downloads, which is exactly why it reads as \"stock\". Best for blogs, side\n  projects, MVPs, and backgrounds. Pexels and Pixabay also carry free stock *video*.\n- **Curated \u002F authentic \u002F premium-but-affordable** -> **Stocksy, Stills, Death to\n  Stock.** Smaller, art-directed collections that dodge the cliche look. Reach\n  here when the free libraries feel generic or the brand needs to look considered.\n  (Verify the license tier on the provider before relying on it - see\n  image-license-rights.)\n- **Broadest selection, paid, releases handled** -> **Adobe Stock, Shutterstock,\n  iStock \u002F Getty RF.** When you need a specific, hard-to-find shot and want\n  model\u002Fproperty releases already in place for commercial use. Subscriptions or\n  credit packs.\n- **Editorial: news, sports, celebrities, real events, brands** -> **Getty\n  Images, AP, Reuters.** These are *editorial-use-only* unless explicitly licensed\n  otherwise - you cannot use them to imply endorsement or to advertise. This is a\n  licensing trap; confirm with **image-license-rights**.\n- **Illustration, vector, icon, or 3D instead of a photo** -> Adobe Stock,\n  Freepik, unDraw, or icon-specific libraries. (Photo search heuristics below\n  still apply.)\n\nRule of thumb: start free for anything internal or low-stakes; move to curated or\npaid the moment the image is the hero of a brand-facing surface.\n\n## Step 3: Craft the search query\n\nSearch like a photo editor, not like Google.\n\n- **Lead with a concrete, photographable noun.** \"engineer debugging at night\",\n  not \"productivity\". Abstractions return the worst stock cliches.\n- **Add context and emotion as separate terms.** subject + setting + mood:\n  \"founder laptop coffee shop candid\".\n- **Use the platform filters**, not just words: orientation (landscape \u002F\n  portrait \u002F square), color, \"people \u002F no people\", and (on paid sites) number of\n  people, age, and editorial vs commercial toggles.\n- **Search synonyms and adjacent scenes.** If \"team meeting\" is all cliche,\n  try \"whiteboard sketching\", \"two people reviewing a screen\", \"office hallway\".\n  The strongest shot is often one query sideways from the obvious one. Run at\n  least 3 query variants before settling, and scroll past the first page or two\n  of results on free libraries - that is where the least-reused shots live.\n- **Match orientation to placement up front** - a wide hero needs landscape with\n  negative space on one side for text; a phone splash needs portrait. Filter for\n  it rather than cropping a square later.\n\n## Step 4: Evaluate the candidates\n\nFor each shortlisted image, check, in order:\n\n1. **Resolution \u002F aspect fits the placement** at full size. A full-width hero\n   needs an original of roughly 2400px or more on the long edge (about 2x the\n   rendered slot for retina screens); social posts and thumbnails need at least\n   ~1080px. Avoid upscaling.\n2. **Licensing is viable for the use** - flag editorial-only and\n   release-required shots and pass them to **image-license-rights** before\n   committing.\n3. **Identifiable people, logos, or artwork present?** -> likely needs a release\n   for commercial use. Note it; do not assume the platform handled it (free\n   libraries often have not).\n4. **Cliche check** - staged handshake, fake laughing at salad, isolated-on-white\n   \"teamwork\"? If the set looks generic, hand the finalists to\n   **visual-asset-curation** to tighten and de-cliche.\n\n## Deliverable\n\nProduce a shortlist of 3-8 candidate images, each with: the source URL, the\nlibrary and license type, resolution and orientation, and any editorial-only or\nrelease-required flag - plus the one-line brief and the queries that produced\nthe set, so the search can be re-run or extended. Hand the shortlist to\nimage-license-rights before anything ships commercially.\n\n## Quality bar\n\n- A written brief existed before the first search.\n- Source was chosen deliberately (free vs curated vs paid vs editorial), not by\n  habit.\n- At least one \"sideways\" query was tried beyond the obvious keyword.\n- Every finalist has its source URL recorded for the license check.\n- Editorial-only and release-required images are flagged, not silently shipped.\n\n## Do NOT\n\n- Do not grab the top first-page result on a free library - the most-downloaded\n  shots are the most reused, and readers have seen them on ten other sites.\n- Do not search abstract nouns (\"success\", \"innovation\", \"growth\") - they return\n  the platform's worst cliches; translate the concept into a photographable scene\n  first.\n- Do not use editorial-archive images (Getty editorial, AP, Reuters) in ads,\n  landing pages, or anything commercial - editorial-use-only is a legal line,\n  not a suggestion.\n- Do not crop your way out of a wrong orientation - a square chopped into a wide\n  hero loses composition and resolution; filter for the right orientation at\n  search time.\n- Do not assume \"free\" means release-free - free libraries frequently host\n  images of identifiable people and logos with no model or property release\n  attached.\n- Do not ship a finalist without its source URL and license type recorded - an\n  untraceable image is an unlicensable image.\n","# Find the Right Stock Photo\n\nThis skill gets you from \"I need an image of X\" to a short list of strong\ncandidates from the *right* source. It owns two decisions: **which library to\nsearch** and **what to type into it**. It does not decide whether you may legally\nuse the result (that is `image-license-rights`), it does not fetch images in code\n(that is `stock-photo-api`), and it does not turn a pile of candidates into a\ncohesive, on-brand set (that is `visual-asset-curation`).\n\n## When to use a sibling instead\n\n- **\"Can I legally use this? Do I need attribution or a model release?\"** ->\n  **image-license-rights**. Always run it before you ship anything commercial.\n- **\"Pull stock photos into my app \u002F script automatically.\"** ->\n  **stock-photo-api**.\n- **\"I have ten options, which ones and in what order, and why do they look\n  cheap?\"** -> **visual-asset-curation**.\n\n## Step 1: Write the one-line visual brief\n\nNever search before you can fill this in. Vague searches return the most generic,\nmost-used (most cliched) images on the platform.\n\n- **Subject** - the concrete noun (\"a barista steaming milk\", not \"coffee\").\n- **Context \u002F setting** - where it happens (\"small independent cafe, morning light\").\n- **Mood \u002F emotion** - \"calm and focused\", \"energetic\", \"quiet luxury\".\n- **Use + placement** - hero banner, blog inline, ad, slide background. This sets\n  orientation and resolution.\n- **Commercial or editorial** - is it selling something (commercial) or\n  illustrating a story\u002Fnews (editorial)? This changes which sources are even\n  legal. Hand the call to **image-license-rights** if unsure.\n- **Budget** - free-only, or is paid on the table?\n\n## Step 2: Pick the source by use case\n\nMatch the brief to a library before you search. The order below is the default\ndecision path.\n\n- **Free, general-purpose, fast** -> **Unsplash, Pexels, Pixabay.** Huge free\n  catalogs, generous licenses, no cost. Trade-off: the popular shots are heavily\n  reused - a first-page result on these platforms can have hundreds of thousands\n  of downloads, which is exactly why it reads as \"stock\". Best for blogs, side\n  projects, MVPs, and backgrounds. Pexels and Pixabay also carry free stock *video*.\n- **Curated \u002F authentic \u002F premium-but-affordable** -> **Stocksy, Stills, Death to\n  Stock.** Smaller, art-directed collections that dodge the cliche look. Reach\n  here when the free libraries feel generic or the brand needs to look considered.\n  (Verify the license tier on the provider before relying on it - see\n  image-license-rights.)\n- **Broadest selection, paid, releases handled** -> **Adobe Stock, Shutterstock,\n  iStock \u002F Getty RF.** When you need a specific, hard-to-find shot and want\n  model\u002Fproperty releases already in place for commercial use. Subscriptions or\n  credit packs.\n- **Editorial: news, sports, celebrities, real events, brands** -> **Getty\n  Images, AP, Reuters.** These are *editorial-use-only* unless explicitly licensed\n  otherwise - you cannot use them to imply endorsement or to advertise. This is a\n  licensing trap; confirm with **image-license-rights**.\n- **Illustration, vector, icon, or 3D instead of a photo** -> Adobe Stock,\n  Freepik, unDraw, or icon-specific libraries. (Photo search heuristics below\n  still apply.)\n\nRule of thumb: start free for anything internal or low-stakes; move to curated or\npaid the moment the image is the hero of a brand-facing surface.\n\n## Step 3: Craft the search query\n\nSearch like a photo editor, not like Google.\n\n- **Lead with a concrete, photographable noun.** \"engineer debugging at night\",\n  not \"productivity\". Abstractions return the worst stock cliches.\n- **Add context and emotion as separate terms.** subject + setting + mood:\n  \"founder laptop coffee shop candid\".\n- **Use the platform filters**, not just words: orientation (landscape \u002F\n  portrait \u002F square), color, \"people \u002F no people\", and (on paid sites) number of\n  people, age, and editorial vs commercial toggles.\n- **Search synonyms and adjacent scenes.** If \"team meeting\" is all cliche,\n  try \"whiteboard sketching\", \"two people reviewing a screen\", \"office hallway\".\n  The strongest shot is often one query sideways from the obvious one. Run at\n  least 3 query variants before settling, and scroll past the first page or two\n  of results on free libraries - that is where the least-reused shots live.\n- **Match orientation to placement up front** - a wide hero needs landscape with\n  negative space on one side for text; a phone splash needs portrait. Filter for\n  it rather than cropping a square later.\n\n## Step 4: Evaluate the candidates\n\nFor each shortlisted image, check, in order:\n\n1. **Resolution \u002F aspect fits the placement** at full size. A full-width hero\n   needs an original of roughly 2400px or more on the long edge (about 2x the\n   rendered slot for retina screens); social posts and thumbnails need at least\n   ~1080px. Avoid upscaling.\n2. **Licensing is viable for the use** - flag editorial-only and\n   release-required shots and pass them to **image-license-rights** before\n   committing.\n3. **Identifiable people, logos, or artwork present?** -> likely needs a release\n   for commercial use. Note it; do not assume the platform handled it (free\n   libraries often have not).\n4. **Cliche check** - staged handshake, fake laughing at salad, isolated-on-white\n   \"teamwork\"? If the set looks generic, hand the finalists to\n   **visual-asset-curation** to tighten and de-cliche.\n\n## Deliverable\n\nProduce a shortlist of 3-8 candidate images, each with: the source URL, the\nlibrary and license type, resolution and orientation, and any editorial-only or\nrelease-required flag - plus the one-line brief and the queries that produced\nthe set, so the search can be re-run or extended. Hand the shortlist to\nimage-license-rights before anything ships commercially.\n\n## Quality bar\n\n- A written brief existed before the first search.\n- Source was chosen deliberately (free vs curated vs paid vs editorial), not by\n  habit.\n- At least one \"sideways\" query was tried beyond the obvious keyword.\n- Every finalist has its source URL recorded for the license check.\n- Editorial-only and release-required images are flagged, not silently shipped.\n\n## Do NOT\n\n- Do not grab the top first-page result on a free library - the most-downloaded\n  shots are the most reused, and readers have seen them on ten other sites.\n- Do not search abstract nouns (\"success\", \"innovation\", \"growth\") - they return\n  the platform's worst cliches; translate the concept into a photographable scene\n  first.\n- Do not use editorial-archive images (Getty editorial, AP, Reuters) in ads,\n  landing pages, or anything commercial - editorial-use-only is a legal line,\n  not a suggestion.\n- Do not crop your way out of a wrong orientation - a square chopped into a wide\n  hero loses composition and resolution; filter for the right orientation at\n  search time.\n- Do not assume \"free\" means release-free - free libraries frequently host\n  images of identifiable people and logos with no model or property release\n  attached.\n- Do not ship a finalist without its source URL and license type recorded - an\n  untraceable image is an unlicensable image.\n",{"name":5,"metadata":24,"description":7},{"title":25},"Find the Right Stock Photo","main","97a13607d669157a4a16d5ba79b77f208319f7b9","skills\u002Fstock-photo-finder",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 stock-photo-finder",{"tool":41,"command":42},"bunx","bunx skills add SkillMedev\u002Fskills --skill stock-photo-finder",{"tool":44,"command":45},"pnpm","pnpm dlx skills add SkillMedev\u002Fskills --skill stock-photo-finder","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSkillMedev\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fstock-photo-finder\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",[],[]]