[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6J8CMWPM92GP44X2DBK7MDG":3,"skill-same:01M6J8CMWPM92GP44X2DBK7MDG":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},"01M6J8CMWPM92GP44X2DBK7MDG","ig-plan",null,"Build the week on Instagram - what to post, which format, when, and who to engage with. Use when the user says \"plan my week\", \"what should I post\", \"content calendar\", \"I have nothing to post about\", or wants a posting schedule and an engagement list.","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-plan\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"plan","ig plan","ig","content calendar","content","my","which","with","about","post","format","posting","schedule","build","calendar","engagement","use","user","list","instagram","2026-11-10 10:12:30",false,"---\nname: ig-plan\ndescription: >-\n  Build the week on Instagram - what to post, which format, when, and who to\n  engage with. Use when the user says \"plan my week\", \"what should I post\",\n  \"content calendar\", \"I have nothing to post about\", or wants a posting\n  schedule and an engagement list.\n---\n\n# ig-plan\n\nThe control room. Everything else in this pack executes; this decides what gets\nexecuted. Run it once a week, on the same day.\n\n## Input\n\nIf `~\u002F.claude\u002Finstagram\u002Fvoice.md`, `swipe.md` and `log.md` exist, read them.\nThe swipe file is the user's own evidence from `\u002Fig-viral` about which formulas\nare landing in their niche right now, and it outranks anything in this file.\nThe log stops the plan repeating a theme from the last fortnight.\n\nIf they do not exist, ask for four things and write them down:\n\n1. What the user sells, and to whom.\n2. The three or four themes they want to be known for.\n3. What actually happened this week: a client call, a number, a mistake, a\n   thing they built, an argument they had. This is where posts come from.\n4. Ten accounts worth being visible to.\n\n## What to post\n\nFour to five posts a week, and at least three of them Reels. Reels are the only\nformat on Instagram that reliably reaches people who do not follow the account.\nCarousels go deep with the people who already do. Stories are daily and are\nplanned separately.\n\nMix across the week, never two of the same type back to back:\n\n| type | share | job |\n| --- | --- | --- |\n| **Proof** | 1 per week | something that happened, with a number. Reel. |\n| **Teach** | 1 to 2 per week | one thing the viewer can do today. Reel or carousel. |\n| **Opinion** | 1 per week | a position that could lose you followers. Reel. |\n| **Story** | 1 per fortnight | a scene with a cost. Reel. |\n| **Offer** | 1 per fortnight | what you sell, said plainly, no apology. Carousel or stories. |\n\nFor each slot give: the theme, the specific angle from what actually happened\nthis week, the format, and the hook formula number from `ig-reel\u002Fhooks.json`.\nNot a topic, an angle. \"AI\" is not a plan. \"The proposal we lost because the\ndraft had an em dash in it\" is a Reel.\n\n## When to post\n\nPost when the user's audience is awake and not at work. For most consumer\naudiences that is early evening local time; for a business audience, early\nmorning.\n\nBut say this plainly: **the hour matters far less than the first two seconds.**\nInstagram will keep showing a Reel for days if it performs, and will bury a\nwell-timed one that does not. If the user is optimising posting times before\ntheir hooks work, they are polishing the wrong thing, and you should say so.\n\nAnchor times to the audience's timezone, not the user's, if those differ.\n\n## The engagement round, which is not optional\n\n20 minutes a day, before posting, not after. Build a list of 10:\n\n- **5 reach** - accounts with an audience the user wants, where a good comment\n  gets seen. Comment early, before the thread is 200 deep.\n- **3 peers** - same size, same field. This is the group that reciprocates.\n- **2 buyers** - people who could actually buy. Comment for weeks before any\n  DM, and never pitch in a comment.\n\nHand the list to `\u002Fig-comment`.\n\n## Output\n\n```\nWEEK OF SEP 15\n\nMON  engage only  (20 min, list below)\nTUE  7:30pm  REEL      PROOF    #5  Time Collapse   - 5hr proposal to 20 min\nWED  stories only + engage\nTHU  7:00pm  CAROUSEL  TEACH    Job B caption       - the 4-slide clause breakdown\nFRI  7:30pm  REEL      OPINION  #2  Negative Command - stop doing discovery calls\nSAT  -\nSUN  6:00pm  REEL      STORY    #21 Mid-Sentence    - the refund email\n\nSTORIES  every day, 3 to 5 frames, question box on Thursday.\n\nENGAGE  (5 reach \u002F 3 peers \u002F 2 buyers)\n  ...\n\nSay \"write Tuesday\" and I will draft it.\n```\n\nWrite the plan to `~\u002F.claude\u002Finstagram\u002Fplan.md` so the other skills can read\nit. Nothing is scheduled or posted anywhere. This is a plan and the user runs\nit.\n","# ig-plan\n\nThe control room. Everything else in this pack executes; this decides what gets\nexecuted. Run it once a week, on the same day.\n\n## Input\n\nIf `~\u002F.claude\u002Finstagram\u002Fvoice.md`, `swipe.md` and `log.md` exist, read them.\nThe swipe file is the user's own evidence from `\u002Fig-viral` about which formulas\nare landing in their niche right now, and it outranks anything in this file.\nThe log stops the plan repeating a theme from the last fortnight.\n\nIf they do not exist, ask for four things and write them down:\n\n1. What the user sells, and to whom.\n2. The three or four themes they want to be known for.\n3. What actually happened this week: a client call, a number, a mistake, a\n   thing they built, an argument they had. This is where posts come from.\n4. Ten accounts worth being visible to.\n\n## What to post\n\nFour to five posts a week, and at least three of them Reels. Reels are the only\nformat on Instagram that reliably reaches people who do not follow the account.\nCarousels go deep with the people who already do. Stories are daily and are\nplanned separately.\n\nMix across the week, never two of the same type back to back:\n\n| type | share | job |\n| --- | --- | --- |\n| **Proof** | 1 per week | something that happened, with a number. Reel. |\n| **Teach** | 1 to 2 per week | one thing the viewer can do today. Reel or carousel. |\n| **Opinion** | 1 per week | a position that could lose you followers. Reel. |\n| **Story** | 1 per fortnight | a scene with a cost. Reel. |\n| **Offer** | 1 per fortnight | what you sell, said plainly, no apology. Carousel or stories. |\n\nFor each slot give: the theme, the specific angle from what actually happened\nthis week, the format, and the hook formula number from `ig-reel\u002Fhooks.json`.\nNot a topic, an angle. \"AI\" is not a plan. \"The proposal we lost because the\ndraft had an em dash in it\" is a Reel.\n\n## When to post\n\nPost when the user's audience is awake and not at work. For most consumer\naudiences that is early evening local time; for a business audience, early\nmorning.\n\nBut say this plainly: **the hour matters far less than the first two seconds.**\nInstagram will keep showing a Reel for days if it performs, and will bury a\nwell-timed one that does not. If the user is optimising posting times before\ntheir hooks work, they are polishing the wrong thing, and you should say so.\n\nAnchor times to the audience's timezone, not the user's, if those differ.\n\n## The engagement round, which is not optional\n\n20 minutes a day, before posting, not after. Build a list of 10:\n\n- **5 reach** - accounts with an audience the user wants, where a good comment\n  gets seen. Comment early, before the thread is 200 deep.\n- **3 peers** - same size, same field. This is the group that reciprocates.\n- **2 buyers** - people who could actually buy. Comment for weeks before any\n  DM, and never pitch in a comment.\n\nHand the list to `\u002Fig-comment`.\n\n## Output\n\n```\nWEEK OF SEP 15\n\nMON  engage only  (20 min, list below)\nTUE  7:30pm  REEL      PROOF    #5  Time Collapse   - 5hr proposal to 20 min\nWED  stories only + engage\nTHU  7:00pm  CAROUSEL  TEACH    Job B caption       - the 4-slide clause breakdown\nFRI  7:30pm  REEL      OPINION  #2  Negative Command - stop doing discovery calls\nSAT  -\nSUN  6:00pm  REEL      STORY    #21 Mid-Sentence    - the refund email\n\nSTORIES  every day, 3 to 5 frames, question box on Thursday.\n\nENGAGE  (5 reach \u002F 3 peers \u002F 2 buyers)\n  ...\n\nSay \"write Tuesday\" and I will draft it.\n```\n\nWrite the plan to `~\u002F.claude\u002Finstagram\u002Fplan.md` so the other skills can read\nit. Nothing is scheduled or posted anywhere. This is a plan and the user runs\nit.\n",{"name":5,"description":7},"main","563fd9d0d01a7240bf22073090c9484e9070e8e8","external\u002Fig-plan",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-plan",{"tool":59,"command":60},"bunx","bunx skills add sgomez-dev\u002Fclaude-skills --skill ig-plan",{"tool":62,"command":63},"pnpm","pnpm dlx skills add sgomez-dev\u002Fclaude-skills --skill ig-plan","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsgomez-dev\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fexternal\u002Fig-plan\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-plan\u002FLICENSE",{"path":73,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":76,"sourceHtmlUrl":77},"UPSTREAM.md","REFERENCE","参考文档",791,"https:\u002F\u002Fgithub.com\u002Fsgomez-dev\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fexternal\u002Fig-plan\u002FUPSTREAM.md",[79,90,98,110,124,133],{"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,109],"Production","Video","video production","recipes","for",{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":121,"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",[116],{"categoryNo":117,"categoryName":118,"taxonomyType":119,"taxonomyTypeDesc":120},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[122,123],"secret skill","never",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":130,"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",[],[131,132],"license","external no license",{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":150,"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",[139,142,145],{"categoryNo":140,"categoryName":141,"taxonomyType":119,"taxonomyTypeDesc":120},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":143,"categoryName":144,"taxonomyType":119,"taxonomyTypeDesc":120},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":146,"categoryName":147,"taxonomyType":148,"taxonomyTypeDesc":149},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[151,152,153,154,155,156,157,158,159,160,161,162,44,163,164,165,166,167,168,169],"swift","write","write swift","features","retain","testing","types","error","how to","problem","modeling","cycle","default","how","api","concurrency","performance","writing","design"]