[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6J8DAS74YTA4V0W2QWVESYP":3,"skill-same:01M6J8DAS74YTA4V0W2QWVESYP":73},{"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":34,"linkOnly":35,"markdownContent":36,"markdownBody":37,"frontMatter":38,"refName":39,"commitSha":40,"skillDirectory":41,"forksCount":42,"repositoryHtmlUrl":43,"repositoryHomepageUrl":6,"ownerHtmlUrl":44,"ownerBlogUrl":45,"ownerDescription":46,"updatedAt":47,"install":48,"resources":61},"01M6J8DAS74YTA4V0W2QWVESYP","ig-reply",null,"Handle the comments under the user's own reels and posts - draft replies to the ones worth answering, sorted by which ones are. Use when the user pastes their comments, says \"reply to these\", \"handle my comments\", \"someone said X on my reel\", or is dealing with a critic, a hater or a lead in the comments.","sgomez-dev\u002Fclaude-skills","sgomez-dev","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F81492002?v=4","01M6J7TFP3PR3PTGBAG3N9Z007","Santiago Gómez de la Torre Romero","01M6J7TFT704JY40NG1YE3V5JQ",1,"MIT","https:\u002F\u002Fgithub.com\u002Fsgomez-dev\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fexternal\u002Fig-reply\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33],"reply","ig","ig reply","critic","user","use","draft","with","comments","reels","posts","replies","which","my","reel","2026-11-10 10:12:30",false,"---\nname: ig-reply\ndescription: >-\n  Handle the comments under the user's own reels and posts - draft replies to\n  the ones worth answering, sorted by which ones are. Use when the user pastes\n  their comments, says \"reply to these\", \"handle my comments\", \"someone said X\n  on my reel\", or is dealing with a critic, a hater or a lead in the comments.\n---\n\n# ig-reply\n\nThe comment thread under your own post is where reach is decided. Every reply\nis another interaction on the post, replies arriving in the first hour do most\nof the work, and on Instagram a reply can also be a Reel, which is the single\nmost underused move on the platform.\n\nBut the value is not equal across comments, so this skill sorts before it\nwrites.\n\n## Input\n\nThe user pastes the comments, ideally with handles. Screenshots are fine. Do\nnot scrape the thread with a browser tool.\n\n## Triage first\n\nSort every comment into one of six buckets and say the counts out loud:\n\n| bucket | what it is | what it gets |\n| --- | --- | --- |\n| **KEYWORD** | the word you asked them to comment | the promised thing, sent by hand or by your approved tool |\n| **LEAD** | someone describing the problem you solve | a real answer in public, then a door |\n| **SUBSTANCE** | adds data, disagrees, extends | the longest reply on the thread |\n| **QUESTION** | a question a lot of people have | this one becomes a Reel, not just a reply |\n| **SUPPORT** | \"?\", \"great post\", a tag | a like, and 3 to 8 words at most |\n| **NOISE** | pitch, spam, bad faith, bait | nothing, or one line and out |\n\nWrite in that order and stop when the value stops.\n\n## The move most people miss\n\nIf a question in the comments is one that thirty other people also have,\n**reply to it with a Reel**. Instagram will attach the comment to the new video\nas a sticker, the person who asked gets notified, and a question with real\ndemand behind it becomes a post with the hook already written for you. Flag\nevery QUESTION that qualifies and hand it to `\u002Fig-reel` as formula #16.\n\n## How to reply\n\n- **Answer the actual question.** If someone asks how, tell them how, in the\n  reply. Do not send them to the DMs to hear an answer they could have had.\n- **Use their name once**, at the start, without an exclamation mark.\n- **Match their length.** A four-word comment does not get a four-line reply.\n- **To a critic:** concede the true part first, in their words, then hold the\n  line. Never delete, never get defensive, never reply twice on the same\n  thread.\n- **To a hater:** nothing. A reply is reach, and reach is what they came for.\n  Hide the comment if it is abusive. Instagram's comment controls exist and\n  using them is not losing.\n- **To a lead:** answer fully in public. The door is one sentence at the end\n  and it is an offer of help, not a pitch. The public answer is what makes the\n  next person DM you.\n\n## Keyword comments\n\nIf the post used a keyword ask, those comments are the whole point of the post.\nEvery one of them is a person who raised their hand. Reply to each, then send\nwhat was promised. If the user has automation set up through Instagram's own\ntools or an approved partner, say so and let it run; if not, the replies are\nmanual and that is fine at this volume. Never bulk-DM people who did not\ncomment.\n\n## Output\n\nOne block, grouped by bucket, each reply copy-ready and already humanized:\n\n```\nREPLIES  ·  84 comments  ·  41 KEYWORD, 2 LEAD, 3 SUBSTANCE, 2 QUESTION, 34 SUPPORT, 2 NOISE\n\nKEYWORD  (41)  send the clause. One line each, same warmth, not copy-paste.\n\nLEAD\n@handle - \"we had this exact thing happen in June\"\n> The bit that fixed it for us was moving the payment trigger off approval\n> entirely. Happy to send the wording if it is useful.\n\nQUESTION -> REEL\n@handle - \"what do you do if they refuse to sign it?\"\n  34 likes on this comment. That is a Reel, not a reply. Formula #16.\n\nNOISE  (2)  skipped. Replying gives them reach.\n```\n\nThen the gate: nothing is posted until the user says yes. They paste the\nreplies.\n","# ig-reply\n\nThe comment thread under your own post is where reach is decided. Every reply\nis another interaction on the post, replies arriving in the first hour do most\nof the work, and on Instagram a reply can also be a Reel, which is the single\nmost underused move on the platform.\n\nBut the value is not equal across comments, so this skill sorts before it\nwrites.\n\n## Input\n\nThe user pastes the comments, ideally with handles. Screenshots are fine. Do\nnot scrape the thread with a browser tool.\n\n## Triage first\n\nSort every comment into one of six buckets and say the counts out loud:\n\n| bucket | what it is | what it gets |\n| --- | --- | --- |\n| **KEYWORD** | the word you asked them to comment | the promised thing, sent by hand or by your approved tool |\n| **LEAD** | someone describing the problem you solve | a real answer in public, then a door |\n| **SUBSTANCE** | adds data, disagrees, extends | the longest reply on the thread |\n| **QUESTION** | a question a lot of people have | this one becomes a Reel, not just a reply |\n| **SUPPORT** | \"?\", \"great post\", a tag | a like, and 3 to 8 words at most |\n| **NOISE** | pitch, spam, bad faith, bait | nothing, or one line and out |\n\nWrite in that order and stop when the value stops.\n\n## The move most people miss\n\nIf a question in the comments is one that thirty other people also have,\n**reply to it with a Reel**. Instagram will attach the comment to the new video\nas a sticker, the person who asked gets notified, and a question with real\ndemand behind it becomes a post with the hook already written for you. Flag\nevery QUESTION that qualifies and hand it to `\u002Fig-reel` as formula #16.\n\n## How to reply\n\n- **Answer the actual question.** If someone asks how, tell them how, in the\n  reply. Do not send them to the DMs to hear an answer they could have had.\n- **Use their name once**, at the start, without an exclamation mark.\n- **Match their length.** A four-word comment does not get a four-line reply.\n- **To a critic:** concede the true part first, in their words, then hold the\n  line. Never delete, never get defensive, never reply twice on the same\n  thread.\n- **To a hater:** nothing. A reply is reach, and reach is what they came for.\n  Hide the comment if it is abusive. Instagram's comment controls exist and\n  using them is not losing.\n- **To a lead:** answer fully in public. The door is one sentence at the end\n  and it is an offer of help, not a pitch. The public answer is what makes the\n  next person DM you.\n\n## Keyword comments\n\nIf the post used a keyword ask, those comments are the whole point of the post.\nEvery one of them is a person who raised their hand. Reply to each, then send\nwhat was promised. If the user has automation set up through Instagram's own\ntools or an approved partner, say so and let it run; if not, the replies are\nmanual and that is fine at this volume. Never bulk-DM people who did not\ncomment.\n\n## Output\n\nOne block, grouped by bucket, each reply copy-ready and already humanized:\n\n```\nREPLIES  ·  84 comments  ·  41 KEYWORD, 2 LEAD, 3 SUBSTANCE, 2 QUESTION, 34 SUPPORT, 2 NOISE\n\nKEYWORD  (41)  send the clause. One line each, same warmth, not copy-paste.\n\nLEAD\n@handle - \"we had this exact thing happen in June\"\n> The bit that fixed it for us was moving the payment trigger off approval\n> entirely. Happy to send the wording if it is useful.\n\nQUESTION -> REEL\n@handle - \"what do you do if they refuse to sign it?\"\n  34 likes on this comment. That is a Reel, not a reply. Formula #16.\n\nNOISE  (2)  skipped. Replying gives them reach.\n```\n\nThen the gate: nothing is posted until the user says yes. They paste the\nreplies.\n",{"name":5,"description":7},"main","563fd9d0d01a7240bf22073090c9484e9070e8e8","external\u002Fig-reply",0,"https:\u002F\u002Fgithub.com\u002Fsgomez-dev\u002Fclaude-skills","https:\u002F\u002Fgithub.com\u002Fsgomez-dev","https:\u002F\u002Fsgomez.dev","\"Volnuratus non victus\"","2026-10-01 18:25:47",{"source":8,"skillName":5,"commands":49,"prompt":59,"zipAvailable":60},[50,53,56],{"tool":51,"command":52},"npx","npx skills add sgomez-dev\u002Fclaude-skills --skill ig-reply",{"tool":54,"command":55},"bunx","bunx skills add sgomez-dev\u002Fclaude-skills --skill ig-reply",{"tool":57,"command":58},"pnpm","pnpm dlx skills add sgomez-dev\u002Fclaude-skills --skill ig-reply","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsgomez-dev\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fexternal\u002Fig-reply\u002FSKILL.md",true,[62,67],{"path":63,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":65,"sourceHtmlUrl":66},"LICENSE","许可证",1073,"https:\u002F\u002Fgithub.com\u002Fsgomez-dev\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fexternal\u002Fig-reply\u002FLICENSE",{"path":68,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":71,"sourceHtmlUrl":72},"UPSTREAM.md","REFERENCE","参考文档",794,"https:\u002F\u002Fgithub.com\u002Fsgomez-dev\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fexternal\u002Fig-reply\u002FUPSTREAM.md",[74,85,93,105,119,128],{"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":34},"01M6J8Q0WEP76PV381RJDTRTV4","template","YOUR_DESCRIPTION_HERE (shown in command palette, keep under 80 chars)","https:\u002F\u002Fgithub.com\u002Fsgomez-dev\u002Fclaude-skills\u002Fblob\u002Fmain\u002Ftemplate\u002FSKILL.md",[],[76,81,82,83,84],"command palette","command","palette","keep",{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":34},"01M6J8PY4KNE7SQP5BD2X1YMHJ","multi","Line one continues here.   Second sentence.","https:\u002F\u002Fgithub.com\u002Fsgomez-dev\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fsite\u002Ftests\u002Ffixtures\u002Frepo\u002Fexternal\u002Fmulti\u002FSKILL.md",[],[87,92],"line",{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":34},"01M6J8PVS7AY0AWP36JRQ7T8S6","ffmpeg","FFmpeg recipes for video production.","https:\u002F\u002Fgithub.com\u002Fsgomez-dev\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fsite\u002Ftests\u002Ffixtures\u002Frepo\u002Fexternal\u002Fffmpeg\u002FSKILL.md",[],[95,100,101,102,103,104],"Production","Video","video production","recipes","for",{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":116,"publishedAt":34},"01M6J8PS6NDT2VY6Y72QW3NGGH","secret-skill","Private, never published.","https:\u002F\u002Fgithub.com\u002Fsgomez-dev\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fsite\u002Ftests\u002Ffixtures\u002Frepo\u002Fexternal\u002F.local\u002Fsecret-skill\u002FSKILL.md",[111],{"categoryNo":112,"categoryName":113,"taxonomyType":114,"taxonomyTypeDesc":115},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[117,118],"secret skill","never",{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":34},"01M6J8PQETD1FW6BWPPSWXFH5N","external-no-license","Has no license.","https:\u002F\u002Fgithub.com\u002Fsgomez-dev\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fsite\u002Ftests\u002Ffixtures\u002Frepo\u002Fbroken\u002Fexternal-no-license\u002FSKILL.md",[],[126,127],"license","external no license",{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":145,"publishedAt":34},"01M6J8PJ5XGMZZZZGECEDHN13J","write-swift","How to write modern Swift well — modeling with value types, Swift 6 data-race safety and approachable concurrency (@concurrent, main-actor-by-default, actors, task groups), protocols and generics (some vs any), API design, performance and ARC, Swift Testing, macros, and the modern language features agents don't know about yet. Use when writing, reviewing, or migrating Swift, or when a concurrency error, a hang, a data race, a retain cycle, or a performance problem needs fixing.","https:\u002F\u002Fgithub.com\u002Fsgomez-dev\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fexternal\u002Fwrite-swift\u002FSKILL.md",[134,137,140],{"categoryNo":135,"categoryName":136,"taxonomyType":114,"taxonomyTypeDesc":115},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":138,"categoryName":139,"taxonomyType":114,"taxonomyTypeDesc":115},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":141,"categoryName":142,"taxonomyType":143,"taxonomyTypeDesc":144},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[146,147,148,149,150,151,152,153,154,155,156,157,39,158,159,160,161,162,163,164],"swift","write","write swift","features","retain","testing","types","error","how to","problem","modeling","cycle","default","how","api","concurrency","performance","writing","design"]