[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6J8C04HTHCB4G78ASFFVTMW":3,"skill-same:01M6J8C04HTHCB4G78ASFFVTMW":78},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":6,"ownerHtmlUrl":49,"ownerBlogUrl":50,"ownerDescription":51,"updatedAt":52,"install":53,"resources":66},"01M6J8C04HTHCB4G78ASFFVTMW","ig-comment",null,"Write comments on other people's Instagram posts and reels that read as a person with an opinion, not a bot. Use when the user pastes a post or a reel and wants a comment, says \"comment on this\", \"engage with this\", \"what do I say here\", or wants a batch for their daily engagement round.","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-comment\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"ig","ig comment","post","batch","reel","for","posts","reels","comments","with","people","instagram","bot","as","do","say","daily","engagement","use","read","2026-11-10 10:12:30",false,"---\nname: ig-comment\ndescription: >-\n  Write comments on other people's Instagram posts and reels that read as a\n  person with an opinion, not a bot. Use when the user pastes a post or a reel\n  and wants a comment, says \"comment on this\", \"engage with this\", \"what do I\n  say here\", or wants a batch for their daily engagement round.\n---\n\n# ig-comment\n\nCommenting is the highest-leverage twenty minutes on Instagram and the easiest\nto do badly. A comment near the top of a reel with 40,000 views is seen by more\npeople than most accounts' own posts, and it is the one place where a stranger\ncan tap straight through to a profile.\n\nA generic comment is worse than none. It costs a tap that goes nowhere and it\nmarks the account as an engagement-pod account to the one person whose opinion\nmattered, which is the creator.\n\n## Input\n\nThe user pastes the post or reel text, or a screenshot, with the account name.\nIf they give a URL you cannot open, ask them to paste it. Do not use a browser\ntool to scrape the feed and do not post anything.\n\n## The nine comment types\n\nPick by what the post actually is. Never default to type 1.\n\n| # | type | when | shape |\n| --- | --- | --- | --- |\n| 1 | **Add a datum** | the post makes a claim you can support with a number | \"Same for us: 40% of...\" |\n| 2 | **Add the missing case** | the post is right but incomplete | \"This holds until {condition}.\" |\n| 3 | **Respectful disagree** | you genuinely think it is wrong | name the agreement first, then the fork |\n| 4 | **Extend one line** | one line in it is the good one | quote it, build on it |\n| 5 | **Ask the real question** | the post skipped the hard part | one question, specific |\n| 6 | **The receipt** | you have done the thing they described | what happened, two sentences |\n| 7 | **The correction** | there is a factual error | be right, be brief, be kind, be sure |\n| 8 | **The reframe** | right facts, wrong frame | \"Another way to read this:\" |\n| 9 | **The one-liner** | the post needs nothing, you want presence | under 10 words, must be funny or true |\n\n## Rules\n\n- **One to three sentences.** Instagram comments are read in a narrow column\n  under a video. A paragraph gets collapsed behind \"more\" and nobody taps it.\n- **Never open with** \"Great post\", \"Love this\", \"So true\", \"This ?\", \"Needed\n  this today\", or the creator's first name with an exclamation mark. All of\n  them are invisible.\n- **No emoji-only comments** and no emoji as the first character.\n- **Never restate the reel.** Everybody watching just watched it.\n- **One idea.** A comment with two points reads as a hijack.\n- **Say the specific thing.** If the comment could sit under any post on the\n  topic, it is not a comment, it is noise.\n- **No pitching, ever.** Not the offer, not the link, not \"check out my page\".\n  That is the fastest way to be blocked by exactly the person you were trying\n  to reach.\n- **Early matters more here than anywhere.** A comment in the first hour on a\n  reel that then travels gets carried with it.\n\n## Output\n\nGive **two options of different types**, labelled, plus one line on which you\nwould post and why. Run both through `\u002Fig-human` first: comments are short, so\nan em dash or a stock phrase is proportionally louder than it is in a caption.\n\n```\nCOMMENT OPTIONS  (on @acct's reel about pricing)\n\n[6 · Receipt]\nWe raised ours 40% last March and lost exactly one client, who was the one\ntaking up half the inbox. Took eight months to stop being scared of it.\n\n[3 · Respectful disagree]\nAgree on the anchoring. The part I would push back on is doing it mid-project.\nWe tried that and it cost us a renewal that was otherwise fine.\n\nPost the first. It concedes something and it has a number in it.\n```\n\n## Batch mode\n\nFor an engagement round, ask for the 5 to 10 posts as pasted text in one\nmessage, return one comment each in a single block, and keep a running note in\n`~\u002F.claude\u002Finstagram\u002Flog.md` of who has been commented on this week.\nCommenting on the same three accounts every day is visible and it looks like\nexactly what it is.\n\n## Never\n\nDo not auto-post, do not automate comments, and do not use a browser tool to\npublish on the user's behalf. Automated engagement violates Instagram's Terms\nof Use and gets accounts action-blocked. This skill writes the comment. The\nuser posts it.\n","# ig-comment\n\nCommenting is the highest-leverage twenty minutes on Instagram and the easiest\nto do badly. A comment near the top of a reel with 40,000 views is seen by more\npeople than most accounts' own posts, and it is the one place where a stranger\ncan tap straight through to a profile.\n\nA generic comment is worse than none. It costs a tap that goes nowhere and it\nmarks the account as an engagement-pod account to the one person whose opinion\nmattered, which is the creator.\n\n## Input\n\nThe user pastes the post or reel text, or a screenshot, with the account name.\nIf they give a URL you cannot open, ask them to paste it. Do not use a browser\ntool to scrape the feed and do not post anything.\n\n## The nine comment types\n\nPick by what the post actually is. Never default to type 1.\n\n| # | type | when | shape |\n| --- | --- | --- | --- |\n| 1 | **Add a datum** | the post makes a claim you can support with a number | \"Same for us: 40% of...\" |\n| 2 | **Add the missing case** | the post is right but incomplete | \"This holds until {condition}.\" |\n| 3 | **Respectful disagree** | you genuinely think it is wrong | name the agreement first, then the fork |\n| 4 | **Extend one line** | one line in it is the good one | quote it, build on it |\n| 5 | **Ask the real question** | the post skipped the hard part | one question, specific |\n| 6 | **The receipt** | you have done the thing they described | what happened, two sentences |\n| 7 | **The correction** | there is a factual error | be right, be brief, be kind, be sure |\n| 8 | **The reframe** | right facts, wrong frame | \"Another way to read this:\" |\n| 9 | **The one-liner** | the post needs nothing, you want presence | under 10 words, must be funny or true |\n\n## Rules\n\n- **One to three sentences.** Instagram comments are read in a narrow column\n  under a video. A paragraph gets collapsed behind \"more\" and nobody taps it.\n- **Never open with** \"Great post\", \"Love this\", \"So true\", \"This ?\", \"Needed\n  this today\", or the creator's first name with an exclamation mark. All of\n  them are invisible.\n- **No emoji-only comments** and no emoji as the first character.\n- **Never restate the reel.** Everybody watching just watched it.\n- **One idea.** A comment with two points reads as a hijack.\n- **Say the specific thing.** If the comment could sit under any post on the\n  topic, it is not a comment, it is noise.\n- **No pitching, ever.** Not the offer, not the link, not \"check out my page\".\n  That is the fastest way to be blocked by exactly the person you were trying\n  to reach.\n- **Early matters more here than anywhere.** A comment in the first hour on a\n  reel that then travels gets carried with it.\n\n## Output\n\nGive **two options of different types**, labelled, plus one line on which you\nwould post and why. Run both through `\u002Fig-human` first: comments are short, so\nan em dash or a stock phrase is proportionally louder than it is in a caption.\n\n```\nCOMMENT OPTIONS  (on @acct's reel about pricing)\n\n[6 · Receipt]\nWe raised ours 40% last March and lost exactly one client, who was the one\ntaking up half the inbox. Took eight months to stop being scared of it.\n\n[3 · Respectful disagree]\nAgree on the anchoring. The part I would push back on is doing it mid-project.\nWe tried that and it cost us a renewal that was otherwise fine.\n\nPost the first. It concedes something and it has a number in it.\n```\n\n## Batch mode\n\nFor an engagement round, ask for the 5 to 10 posts as pasted text in one\nmessage, return one comment each in a single block, and keep a running note in\n`~\u002F.claude\u002Finstagram\u002Flog.md` of who has been commented on this week.\nCommenting on the same three accounts every day is visible and it looks like\nexactly what it is.\n\n## Never\n\nDo not auto-post, do not automate comments, and do not use a browser tool to\npublish on the user's behalf. Automated engagement violates Instagram's Terms\nof Use and gets accounts action-blocked. This skill writes the comment. The\nuser posts it.\n",{"name":5,"description":7},"main","563fd9d0d01a7240bf22073090c9484e9070e8e8","external\u002Fig-comment",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":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add sgomez-dev\u002Fclaude-skills --skill ig-comment",{"tool":59,"command":60},"bunx","bunx skills add sgomez-dev\u002Fclaude-skills --skill ig-comment",{"tool":62,"command":63},"pnpm","pnpm dlx skills add sgomez-dev\u002Fclaude-skills --skill ig-comment","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsgomez-dev\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fexternal\u002Fig-comment\u002FSKILL.md",true,[67,72],{"path":68,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":71},"LICENSE","许可证",1073,"https:\u002F\u002Fgithub.com\u002Fsgomez-dev\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fexternal\u002Fig-comment\u002FLICENSE",{"path":73,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":76,"sourceHtmlUrl":77},"UPSTREAM.md","REFERENCE","参考文档",800,"https:\u002F\u002Fgithub.com\u002Fsgomez-dev\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fexternal\u002Fig-comment\u002FUPSTREAM.md",[79,90,98,109,123,132],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":39},"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",[],[81,86,87,88,89],"command palette","command","palette","keep",{"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":39},"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",[],[92,97],"line",{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":39},"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",[],[100,105,106,107,108,24],"Production","Video","video production","recipes",{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":120,"publishedAt":39},"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",[115],{"categoryNo":116,"categoryName":117,"taxonomyType":118,"taxonomyTypeDesc":119},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[121,122],"secret skill","never",{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":39},"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",[],[130,131],"license","external no license",{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":149,"publishedAt":39},"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",[138,141,144],{"categoryNo":139,"categoryName":140,"taxonomyType":118,"taxonomyTypeDesc":119},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":142,"categoryName":143,"taxonomyType":118,"taxonomyTypeDesc":119},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":145,"categoryName":146,"taxonomyType":147,"taxonomyTypeDesc":148},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[150,151,152,153,154,155,156,157,158,159,160,161,44,162,163,164,165,166,167,168],"swift","write","write swift","features","retain","testing","types","error","how to","problem","modeling","cycle","default","how","api","concurrency","performance","writing","design"]