[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M750R5TAF31MX1SM0ECJS540":3,"skill-same:01M750R5TAF31MX1SM0ECJS540":58},{"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":35,"commitSha":36,"skillDirectory":37,"forksCount":38,"repositoryHtmlUrl":39,"repositoryHomepageUrl":40,"ownerHtmlUrl":41,"ownerBlogUrl":40,"ownerDescription":42,"updatedAt":43,"install":44,"resources":57},"01M750R5TAF31MX1SM0ECJS540","instagram-post-builder",null,"Interactively builds a complete, copy-paste-ready Instagram post package - three hook variants using distinct patterns, a caption body, one clear CTA, a 15-20 hashtag set across reach tiers, alt text, and a visual direction with shot list or slide breakdown - through a one-question-at-a-time interview, optionally grounded in a trend-educator briefing. Use when someone says \"write an Instagram post for my launch\", \"build the full post package for this reel\", \"put together a carousel with hooks and hashtags\", or reaches the build stage after trend-educator. Do NOT use for finding what is trending - use instagram-trend-scout instead; for a single caption without the full package - use social-caption-writer; for planning a month of content - use social-content-calendar.","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\u002Finstagram-post-builder\u002FSKILL.md",[],[],"2026-11-11 17:59:37",false,"---\nname: instagram-post-builder\nslug: instagram-post-builder\ndescription: Interactively builds a complete, copy-paste-ready Instagram post package - three hook variants using distinct patterns, a caption body, one clear CTA, a 15-20 hashtag set across reach tiers, alt text, and a visual direction with shot list or slide breakdown - through a one-question-at-a-time interview, optionally grounded in a trend-educator briefing. Use when someone says \"write an Instagram post for my launch\", \"build the full post package for this reel\", \"put together a carousel with hooks and hashtags\", or reaches the build stage after trend-educator. Do NOT use for finding what is trending - use instagram-trend-scout instead; for a single caption without the full package - use social-caption-writer; for planning a month of content - use social-content-calendar.\nversion: 1.0.0\nstage: S3\ntags: [instagram, social-media, copywriting, captions, hashtags, content-creation]\nlicense: MIT\nmetadata:\n  title: \"Instagram Post Builder\"\n---\n\n# Instagram Post Builder\n\n**Stage: S3 - Build** (final skill in the Instagram Trend Post Builder flywheel)\n\nThis is where trend awareness becomes an actual post. It takes the trend card from `trend-educator` as *fuel*, but the post is built around the user's own message - the trend informs the packaging, it does not dictate the content. The result is a copy-paste-ready package.\n\nThe defining behavior of this skill is **conversational, one question at a time**. Do not interrogate the user with a form. Ask, listen, then ask the next thing - adapting to what they said.\n\n## Input Schema\n\n| Field | Type | Required | Default | Description |\n|-------|------|----------|---------|-------------|\n| `user_message` | string | yes* | - | What the user wants to say \u002F the topic of the post. *If absent, the skill elicits it as the first question rather than failing. |\n| `educator_brief` | object | no | - | The output from `trend-educator` (`trend_summary`, `why_it_works`, `opportunity_angles`, `confidence_note`). When present, the build is grounded in these trends. When absent, the skill still works in standalone mode. |\n| `tone` | string | no | _(asked)_ | Desired voice (e.g. \"warm\", \"punchy\", \"expert\", \"playful\"). Elicited if not provided. |\n| `audience` | string | no | _(asked)_ | Who the post is for. Elicited if not provided. |\n| `cta_goal` | string | no | _(asked)_ | The action the post should drive (e.g. \"save it\", \"comment a word\", \"visit link in bio\", \"follow\"). Elicited if not provided. |\n\n## Workflow\n\nThe skill runs as a short guided interview, then generates. **Ask exactly one question per turn** and wait for the answer before continuing.\n\n1. **Open and orient.** If `educator_brief` is present, lead with one line referencing the opportunity it unlocks (\"The scout found that contrarian Reels are landing in your niche - let's use that.\"). If absent, say you'll build from scratch.\n2. **Q1 - The message.** If `user_message` is missing, ask: \"What's the one thing you want this post to say or teach?\" If it is present, reflect it back in a sentence and confirm before moving on.\n3. **Q2 - The audience.** Ask who it's for and what they're struggling with. (Skip if `audience` already supplied.)\n4. **Q3 - The tone.** Ask how they want to sound, offering 3 quick options anchored to their brand. (Skip if `tone` supplied.)\n5. **Q4 - The goal.** Ask what one action a viewer should take after seeing it (maps to `cta_goal`). (Skip if supplied.)\n6. **Q5 - Format pick.** Recommend a `format` from the `opportunity_angles` (or ask, if standalone) and confirm reel vs carousel vs single image - because it changes hook and visual direction.\n7. **Confirm the brief.** Echo a one-line summary: message + audience + tone + goal + format. Ask \"Build it?\" Proceed on confirmation; revise if not.\n8. **Generate hooks.** Write **3 distinct hook variants**, each using a different proven pattern from the trend card's `winning_hooks` where available (e.g. one curiosity-gap, one contrarian, one direct-promise). Keep each under ~12 words and front-load the stakes - on a reel, the first 3 seconds decide whether the viewer scrolls past, so the hook must land in the first frame, not after an intro.\n9. **Write the caption body.** Open by paying off the chosen hook, deliver the message with one clear idea per line\u002Fshort paragraph, and write in the agreed `tone` for the stated `audience`. The feed truncates captions at roughly 125 characters before the \"…more\" fold - the hook payoff and the reason to keep reading must fit above it. The hard ceiling is 2,200 characters; educational carousels can run long, reel captions work best well under that since the video carries the message.\n10. **Write the CTA.** One clear ask aligned to `cta_goal`. Make it specific and low-friction (\"comment 'GUIDE' and I'll send it\" beats \"let me know your thoughts\").\n11. **Build the hashtag set.** Produce **15-20 hashtags** mixing three tiers: a few broad (high-volume), several mid-size (niche-defining), and a few specific\u002Flong-tail (low-competition). The platform allows up to 30 per post - maxing it out reads as spam to both the algorithm and humans, which is why this skill caps at 20. Avoid banned or spammy tags. Tie them to the niche from the brief.\n12. **Write the alt text.** One to two sentences describing the visual for screen-reader accessibility - literal and descriptive, not keyword-stuffed.\n13. **Suggest a visual direction.** Concrete art direction for the chosen format: shot list \u002F slide breakdown, on-screen text placement, and a first-frame or cover idea that matches the hook. For carousels, keep it to 6-10 slides - completion rate falls off past that, and the last slide should always be the CTA.\n14. **Assemble and deliver** the complete post package as copy-paste blocks (see Output Format).\n\n## Output Schema\n\n```json\n{\n  \"format\": \"string - reel | carousel | single_image | story\",\n  \"hooks\": [\n    {\n      \"variant\": \"string - pattern name, e.g. 'curiosity-gap'\",\n      \"text\": \"string - the hook line (on-screen text for reels, first line for static)\"\n    }\n  ],\n  \"caption_body\": \"string - the full caption, formatted with line breaks\",\n  \"cta\": \"string - the single call to action\",\n  \"hashtags\": [\"string - 15 to 20 tags, '#'-prefixed, mixed reach tiers\"],\n  \"alt_text\": \"string - 1 to 2 sentence accessibility description\",\n  \"visual_direction\": {\n    \"concept\": \"string - the core visual idea\",\n    \"shot_or_slides\": \"string - shot list (reel) or slide-by-slide breakdown (carousel)\",\n    \"on_screen_text\": \"string - text overlay guidance\",\n    \"cover_idea\": \"string - first-frame \u002F cover-slide concept tied to the hook\"\n  },\n  \"post_brief\": {\n    \"message\": \"string\",\n    \"audience\": \"string\",\n    \"tone\": \"string\",\n    \"cta_goal\": \"string\"\n  }\n}\n```\n\n## Output Format\n\nDeliver as labeled, copy-paste-ready blocks under the header `📦 Post Package - {format}`:\n\n1. **Hooks (pick one)** - the 3 variants as a numbered list, each tagged with its pattern.\n2. **Caption** - in a fenced block so the user can copy it cleanly, CTA included as the final line.\n3. **Hashtags** - in a fenced block, space-separated, ready to paste.\n4. **Alt text** - in a fenced block.\n5. **Visual direction** - concept, shots\u002Fslides, on-screen text, cover idea as a short bulleted brief.\n6. Close with: `Want a second angle, a different tone, or a carousel version? Say the word.`\n\n## Error Handling\n\n- **No user_message:** Don't stall or guess the topic - make eliciting it Q1 (Workflow step 2). The skill is designed to start empty.\n- **No educator_brief (standalone use):** Proceed in standalone mode. Ask one extra question about the niche so hooks and hashtags are still targeted, and note that trend-grounding is skipped.\n- **Vague answers (\"idk\", \"anything\"):** Offer 2-3 concrete options to react to rather than asking the same open question again. Reacting is easier than generating.\n- **User abandons mid-interview:** Build the best package you can from what's been gathered so far, clearly mark the assumptions you filled in, and invite the user to refine any field. Never leave them empty-handed.\n- **User wants edits after delivery:** Treat the package as a draft. Regenerate only the requested part (e.g. just new hooks) rather than rebuilding everything.\n- **Over\u002Funder hashtag count:** Always land in the 15-20 range; if the niche is narrow, fill with adjacent and long-tail tags rather than padding with generic ones or dropping below 15.\n\n## Do NOT\n\n- **Do not ask multiple questions in one turn.** The one-question-at-a-time interview is the skill's defining behavior; a wall of form fields gets half-answered and the package inherits the gaps.\n- **Do not bury the hook after an intro.** \"Hey guys, so today I want to talk about…\" is the first 3 seconds a reel cannot afford. The hook is line one, frame one, always.\n- **Do not write the caption's payoff below the ~125-character fold.** If the reader has to tap \"more\" to find out why they should care, most never will.\n- **Do not pad the hashtag set with generic mega-tags** (#love, #instagood) to hit the count. They add spam signal, not reach - fill with adjacent long-tail niche tags instead.\n- **Do not keyword-stuff the alt text.** It exists for screen readers; describe the visual literally. Stuffing it trades accessibility for an SEO myth.\n- **Do not let the trend dictate the message.** The `educator_brief` shapes the packaging (format, hook pattern, timing); the user's own message is the content. A post that is all trend and no message performs once and builds nothing.\n\n## Quality bar\n\n- Three hooks, three genuinely different patterns - not one idea reworded.\n- The chosen hook's payoff sits above the caption fold.\n- CTA is a single, specific, low-friction action matching `cta_goal`.\n- Hashtag set lands in 15-20 with all three reach tiers represented.\n- Every block is copy-paste ready - no placeholders left unfilled, no meta-commentary inside the fenced blocks.\n\n## Flywheel Connections\n\n- **Fed by:** `trend-educator` - consumes its `opportunity_angles`, `trend_summary`, and `why_it_works` as `educator_brief` to ground the post in working trends.\n- **Feeds into:** _(end of cycle - the post ships; next week the loop restarts at `instagram-trend-scout`)._ Optionally hand the published post's performance back into `instagram-trend-scout` as a future signal.\n- **Part of pack:** Instagram Trend Post Builder (S1 → S2 → S3).\n","# Instagram Post Builder\n\n**Stage: S3 - Build** (final skill in the Instagram Trend Post Builder flywheel)\n\nThis is where trend awareness becomes an actual post. It takes the trend card from `trend-educator` as *fuel*, but the post is built around the user's own message - the trend informs the packaging, it does not dictate the content. The result is a copy-paste-ready package.\n\nThe defining behavior of this skill is **conversational, one question at a time**. Do not interrogate the user with a form. Ask, listen, then ask the next thing - adapting to what they said.\n\n## Input Schema\n\n| Field | Type | Required | Default | Description |\n|-------|------|----------|---------|-------------|\n| `user_message` | string | yes* | - | What the user wants to say \u002F the topic of the post. *If absent, the skill elicits it as the first question rather than failing. |\n| `educator_brief` | object | no | - | The output from `trend-educator` (`trend_summary`, `why_it_works`, `opportunity_angles`, `confidence_note`). When present, the build is grounded in these trends. When absent, the skill still works in standalone mode. |\n| `tone` | string | no | _(asked)_ | Desired voice (e.g. \"warm\", \"punchy\", \"expert\", \"playful\"). Elicited if not provided. |\n| `audience` | string | no | _(asked)_ | Who the post is for. Elicited if not provided. |\n| `cta_goal` | string | no | _(asked)_ | The action the post should drive (e.g. \"save it\", \"comment a word\", \"visit link in bio\", \"follow\"). Elicited if not provided. |\n\n## Workflow\n\nThe skill runs as a short guided interview, then generates. **Ask exactly one question per turn** and wait for the answer before continuing.\n\n1. **Open and orient.** If `educator_brief` is present, lead with one line referencing the opportunity it unlocks (\"The scout found that contrarian Reels are landing in your niche - let's use that.\"). If absent, say you'll build from scratch.\n2. **Q1 - The message.** If `user_message` is missing, ask: \"What's the one thing you want this post to say or teach?\" If it is present, reflect it back in a sentence and confirm before moving on.\n3. **Q2 - The audience.** Ask who it's for and what they're struggling with. (Skip if `audience` already supplied.)\n4. **Q3 - The tone.** Ask how they want to sound, offering 3 quick options anchored to their brand. (Skip if `tone` supplied.)\n5. **Q4 - The goal.** Ask what one action a viewer should take after seeing it (maps to `cta_goal`). (Skip if supplied.)\n6. **Q5 - Format pick.** Recommend a `format` from the `opportunity_angles` (or ask, if standalone) and confirm reel vs carousel vs single image - because it changes hook and visual direction.\n7. **Confirm the brief.** Echo a one-line summary: message + audience + tone + goal + format. Ask \"Build it?\" Proceed on confirmation; revise if not.\n8. **Generate hooks.** Write **3 distinct hook variants**, each using a different proven pattern from the trend card's `winning_hooks` where available (e.g. one curiosity-gap, one contrarian, one direct-promise). Keep each under ~12 words and front-load the stakes - on a reel, the first 3 seconds decide whether the viewer scrolls past, so the hook must land in the first frame, not after an intro.\n9. **Write the caption body.** Open by paying off the chosen hook, deliver the message with one clear idea per line\u002Fshort paragraph, and write in the agreed `tone` for the stated `audience`. The feed truncates captions at roughly 125 characters before the \"…more\" fold - the hook payoff and the reason to keep reading must fit above it. The hard ceiling is 2,200 characters; educational carousels can run long, reel captions work best well under that since the video carries the message.\n10. **Write the CTA.** One clear ask aligned to `cta_goal`. Make it specific and low-friction (\"comment 'GUIDE' and I'll send it\" beats \"let me know your thoughts\").\n11. **Build the hashtag set.** Produce **15-20 hashtags** mixing three tiers: a few broad (high-volume), several mid-size (niche-defining), and a few specific\u002Flong-tail (low-competition). The platform allows up to 30 per post - maxing it out reads as spam to both the algorithm and humans, which is why this skill caps at 20. Avoid banned or spammy tags. Tie them to the niche from the brief.\n12. **Write the alt text.** One to two sentences describing the visual for screen-reader accessibility - literal and descriptive, not keyword-stuffed.\n13. **Suggest a visual direction.** Concrete art direction for the chosen format: shot list \u002F slide breakdown, on-screen text placement, and a first-frame or cover idea that matches the hook. For carousels, keep it to 6-10 slides - completion rate falls off past that, and the last slide should always be the CTA.\n14. **Assemble and deliver** the complete post package as copy-paste blocks (see Output Format).\n\n## Output Schema\n\n```json\n{\n  \"format\": \"string - reel | carousel | single_image | story\",\n  \"hooks\": [\n    {\n      \"variant\": \"string - pattern name, e.g. 'curiosity-gap'\",\n      \"text\": \"string - the hook line (on-screen text for reels, first line for static)\"\n    }\n  ],\n  \"caption_body\": \"string - the full caption, formatted with line breaks\",\n  \"cta\": \"string - the single call to action\",\n  \"hashtags\": [\"string - 15 to 20 tags, '#'-prefixed, mixed reach tiers\"],\n  \"alt_text\": \"string - 1 to 2 sentence accessibility description\",\n  \"visual_direction\": {\n    \"concept\": \"string - the core visual idea\",\n    \"shot_or_slides\": \"string - shot list (reel) or slide-by-slide breakdown (carousel)\",\n    \"on_screen_text\": \"string - text overlay guidance\",\n    \"cover_idea\": \"string - first-frame \u002F cover-slide concept tied to the hook\"\n  },\n  \"post_brief\": {\n    \"message\": \"string\",\n    \"audience\": \"string\",\n    \"tone\": \"string\",\n    \"cta_goal\": \"string\"\n  }\n}\n```\n\n## Output Format\n\nDeliver as labeled, copy-paste-ready blocks under the header `📦 Post Package - {format}`:\n\n1. **Hooks (pick one)** - the 3 variants as a numbered list, each tagged with its pattern.\n2. **Caption** - in a fenced block so the user can copy it cleanly, CTA included as the final line.\n3. **Hashtags** - in a fenced block, space-separated, ready to paste.\n4. **Alt text** - in a fenced block.\n5. **Visual direction** - concept, shots\u002Fslides, on-screen text, cover idea as a short bulleted brief.\n6. Close with: `Want a second angle, a different tone, or a carousel version? Say the word.`\n\n## Error Handling\n\n- **No user_message:** Don't stall or guess the topic - make eliciting it Q1 (Workflow step 2). The skill is designed to start empty.\n- **No educator_brief (standalone use):** Proceed in standalone mode. Ask one extra question about the niche so hooks and hashtags are still targeted, and note that trend-grounding is skipped.\n- **Vague answers (\"idk\", \"anything\"):** Offer 2-3 concrete options to react to rather than asking the same open question again. Reacting is easier than generating.\n- **User abandons mid-interview:** Build the best package you can from what's been gathered so far, clearly mark the assumptions you filled in, and invite the user to refine any field. Never leave them empty-handed.\n- **User wants edits after delivery:** Treat the package as a draft. Regenerate only the requested part (e.g. just new hooks) rather than rebuilding everything.\n- **Over\u002Funder hashtag count:** Always land in the 15-20 range; if the niche is narrow, fill with adjacent and long-tail tags rather than padding with generic ones or dropping below 15.\n\n## Do NOT\n\n- **Do not ask multiple questions in one turn.** The one-question-at-a-time interview is the skill's defining behavior; a wall of form fields gets half-answered and the package inherits the gaps.\n- **Do not bury the hook after an intro.** \"Hey guys, so today I want to talk about…\" is the first 3 seconds a reel cannot afford. The hook is line one, frame one, always.\n- **Do not write the caption's payoff below the ~125-character fold.** If the reader has to tap \"more\" to find out why they should care, most never will.\n- **Do not pad the hashtag set with generic mega-tags** (#love, #instagood) to hit the count. They add spam signal, not reach - fill with adjacent long-tail niche tags instead.\n- **Do not keyword-stuff the alt text.** It exists for screen readers; describe the visual literally. Stuffing it trades accessibility for an SEO myth.\n- **Do not let the trend dictate the message.** The `educator_brief` shapes the packaging (format, hook pattern, timing); the user's own message is the content. A post that is all trend and no message performs once and builds nothing.\n\n## Quality bar\n\n- Three hooks, three genuinely different patterns - not one idea reworded.\n- The chosen hook's payoff sits above the caption fold.\n- CTA is a single, specific, low-friction action matching `cta_goal`.\n- Hashtag set lands in 15-20 with all three reach tiers represented.\n- Every block is copy-paste ready - no placeholders left unfilled, no meta-commentary inside the fenced blocks.\n\n## Flywheel Connections\n\n- **Fed by:** `trend-educator` - consumes its `opportunity_angles`, `trend_summary`, and `why_it_works` as `educator_brief` to ground the post in working trends.\n- **Feeds into:** _(end of cycle - the post ships; next week the loop restarts at `instagram-trend-scout`)._ Optionally hand the published post's performance back into `instagram-trend-scout` as a future signal.\n- **Part of pack:** Instagram Trend Post Builder (S1 → S2 → S3).\n",{"name":5,"slug":5,"tags":24,"stage":31,"license":15,"version":32,"metadata":33,"description":7},[25,26,27,28,29,30],"instagram","social-media","copywriting","captions","hashtags","content-creation","S3","1.0.0",{"title":34},"Instagram Post Builder","main","97a13607d669157a4a16d5ba79b77f208319f7b9","skills\u002Finstagram-post-builder",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":45,"prompt":55,"zipAvailable":56},[46,49,52],{"tool":47,"command":48},"npx","npx skills add SkillMedev\u002Fskills --skill instagram-post-builder",{"tool":50,"command":51},"bunx","bunx skills add SkillMedev\u002Fskills --skill instagram-post-builder",{"tool":53,"command":54},"pnpm","pnpm dlx skills add SkillMedev\u002Fskills --skill instagram-post-builder","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSkillMedev\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Finstagram-post-builder\u002FSKILL.md",true,[],[59,69,76,83,90,97],{"skillNo":60,"name":61,"nameZh":62,"description":63,"descriptionZh":64,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":68},"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":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":68},"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":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":68},"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":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":68},"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":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":68},"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":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":68},"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",[],[]]