[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BFV93DPTKP8AKEXX9D0JK2":3,"skill-same:01M7BFV93DPTKP8AKEXX9D0JK2":61},{"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":40,"commitSha":41,"skillDirectory":42,"forksCount":43,"repositoryHtmlUrl":44,"repositoryHomepageUrl":6,"ownerHtmlUrl":45,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":46,"install":47,"resources":60},"01M7BFV93DPTKP8AKEXX9D0JK2","social-media-content-calendar",null,"Plan multi-platform social campaigns: briefs to posting.","LIJALEN23\u002FBeryl","LIJALEN23","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F141412346?v=4","01M7AQK5G18E0M3NKP1S35F4KE","oneplusnine","01M7AQK5GNQE3MMPFJ9TCCJQCN",1,"MIT","https:\u002F\u002Fgithub.com\u002FLIJALEN23\u002FBeryl\u002Fblob\u002Fmaster\u002Flocal-agent\u002Foptional-skills\u002Fcreative\u002Fsocial-media-content-calendar\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: social-media-content-calendar\ndescription: \"Plan multi-platform social campaigns: briefs to posting.\"\nversion: 0.1.0\nauthor: Ben Barclay (benbarclay), Hermes Agent\nlicense: MIT\nplatforms: [linux, macos, windows]\nmetadata:\n  hermes:\n    tags: [Social-Media, Content-Calendar, Campaigns, Publishing]\n    related_skills: [xurl, humanizer]\n---\n\n# Social Media Content Calendar\n\nPlan a concrete calendar across selected social platforms. This skill owns campaign structure, post briefs, channel adaptation, approvals, and publishing verification; platform skills such as `xurl` own API commands. For platforms without a connector, the verified handoff ends at approved drafts for the user's scheduler — say so rather than claiming publication.\n\n## When to Use\n\n- \"Build next month's social calendar.\"\n- \"Turn this launch into posts for X, LinkedIn, Instagram, and TikTok.\"\n- \"Draft and schedule a campaign.\"\n- \"Repurpose these articles\u002Fvideos into social content.\"\n\nDon't use for: single one-off posts (use the platform skill directly).\n\n## Procedure\n\n### 1. Define campaign constraints\n\nRecord objective, audience, offer\u002Fmessage, platforms, date range, cadence, voice, mandatory\u002Fprohibited claims, links, tracking convention, localization, and approval\u002Fpublishing authority. Done when each proposed post has a clear business purpose.\n\n### 2. Inventory source material\n\nCollect verified product facts, launches, articles, media, testimonials with permission, brand assets, and key dates using `read_file` and `web_extract`. Mark claim owners and expiration. Done when unsupported claims and missing assets are visible.\n\n### 3. Build themes and calendar slots\n\nCreate a balanced mix such as education, proof, product, community, event, behind-the-scenes, and conversation. Account for platform cadence and campaign milestones. Done when dates, platforms, themes, and objectives form a coherent calendar rather than duplicate cross-posts.\n\n### 4. Write platform-specific briefs\n\nFor each post specify hook, core message, format, copy length, CTA, link, asset dimensions\u002Fcontent, accessibility text, tags\u002Fmentions, and success metric. Adapt rather than copy-paste between platforms. Done when a creator can produce the asset without hidden context.\n\n### 5. Draft copy and assets\n\nLoad `humanizer` for voice; generate visuals with the `image_generate` tool where assets are needed. Preserve factual claims and shared campaign identity while respecting platform norms. Done when every calendar slot has draft copy and asset status.\n\n### 6. Run editorial and risk review\n\nCheck factual accuracy, tone, repetition, rights\u002Fpermissions, accessibility, disclosures, link destination, date relevance, and crisis sensitivity. Mark `draft`, `needs review`, or `approved`; do not publish from draft. Done when every post has a disposition and owner.\n\n### 7. Schedule or hand off\n\nPresent the approval batch. Publish\u002Fschedule only approved posts using available platform skills (`xurl` for X); for platforms without a connector, deliver the approved package (copy, assets, timing) for the user's scheduling tool and mark those slots handed-off, not published. Read back scheduled time, account, content preview, and provider post\u002Fjob ID for anything actually published. Done when the calendar reflects verified publishing or handoff status per slot.\n\n## Pitfalls\n\n- Identical copy on every platform.\n- Filling cadence with low-value repetitive posts.\n- Publishing unverified metrics, testimonials, or future claims.\n- Confusing generated asset completion with scheduled publication.\n- Claiming \"scheduled\" for platforms where the handoff ended at drafts.\n\n## Verification\n\n- [ ] Every post traces to a campaign objective and a verified claim inventory.\n- [ ] No post was published from `draft` or `needs review` state.\n- [ ] Published slots have provider-confirmed IDs; handed-off slots are marked as such.\n- [ ] Rights, permissions, and disclosures checked before any publish.\n","# Social Media Content Calendar\n\nPlan a concrete calendar across selected social platforms. This skill owns campaign structure, post briefs, channel adaptation, approvals, and publishing verification; platform skills such as `xurl` own API commands. For platforms without a connector, the verified handoff ends at approved drafts for the user's scheduler — say so rather than claiming publication.\n\n## When to Use\n\n- \"Build next month's social calendar.\"\n- \"Turn this launch into posts for X, LinkedIn, Instagram, and TikTok.\"\n- \"Draft and schedule a campaign.\"\n- \"Repurpose these articles\u002Fvideos into social content.\"\n\nDon't use for: single one-off posts (use the platform skill directly).\n\n## Procedure\n\n### 1. Define campaign constraints\n\nRecord objective, audience, offer\u002Fmessage, platforms, date range, cadence, voice, mandatory\u002Fprohibited claims, links, tracking convention, localization, and approval\u002Fpublishing authority. Done when each proposed post has a clear business purpose.\n\n### 2. Inventory source material\n\nCollect verified product facts, launches, articles, media, testimonials with permission, brand assets, and key dates using `read_file` and `web_extract`. Mark claim owners and expiration. Done when unsupported claims and missing assets are visible.\n\n### 3. Build themes and calendar slots\n\nCreate a balanced mix such as education, proof, product, community, event, behind-the-scenes, and conversation. Account for platform cadence and campaign milestones. Done when dates, platforms, themes, and objectives form a coherent calendar rather than duplicate cross-posts.\n\n### 4. Write platform-specific briefs\n\nFor each post specify hook, core message, format, copy length, CTA, link, asset dimensions\u002Fcontent, accessibility text, tags\u002Fmentions, and success metric. Adapt rather than copy-paste between platforms. Done when a creator can produce the asset without hidden context.\n\n### 5. Draft copy and assets\n\nLoad `humanizer` for voice; generate visuals with the `image_generate` tool where assets are needed. Preserve factual claims and shared campaign identity while respecting platform norms. Done when every calendar slot has draft copy and asset status.\n\n### 6. Run editorial and risk review\n\nCheck factual accuracy, tone, repetition, rights\u002Fpermissions, accessibility, disclosures, link destination, date relevance, and crisis sensitivity. Mark `draft`, `needs review`, or `approved`; do not publish from draft. Done when every post has a disposition and owner.\n\n### 7. Schedule or hand off\n\nPresent the approval batch. Publish\u002Fschedule only approved posts using available platform skills (`xurl` for X); for platforms without a connector, deliver the approved package (copy, assets, timing) for the user's scheduling tool and mark those slots handed-off, not published. Read back scheduled time, account, content preview, and provider post\u002Fjob ID for anything actually published. Done when the calendar reflects verified publishing or handoff status per slot.\n\n## Pitfalls\n\n- Identical copy on every platform.\n- Filling cadence with low-value repetitive posts.\n- Publishing unverified metrics, testimonials, or future claims.\n- Confusing generated asset completion with scheduled publication.\n- Claiming \"scheduled\" for platforms where the handoff ended at drafts.\n\n## Verification\n\n- [ ] Every post traces to a campaign objective and a verified claim inventory.\n- [ ] No post was published from `draft` or `needs review` state.\n- [ ] Published slots have provider-confirmed IDs; handed-off slots are marked as such.\n- [ ] Rights, permissions, and disclosures checked before any publish.\n",{"name":5,"author":24,"license":15,"version":25,"metadata":26,"platforms":36,"description":7},"Ben Barclay (benbarclay), Hermes Agent","0.1.0",{"hermes":27},{"tags":28,"related_skills":33},[29,30,31,32],"Social-Media","Content-Calendar","Campaigns","Publishing",[34,35],"xurl","humanizer",[37,38,39],"linux","macos","windows","master","4a5caebee4b5f9068d3a68c9a7ecd8df12bd4962","local-agent\u002Foptional-skills\u002Fcreative\u002Fsocial-media-content-calendar",0,"https:\u002F\u002Fgithub.com\u002FLIJALEN23\u002FBeryl","https:\u002F\u002Fgithub.com\u002FLIJALEN23","2026-09-01 14:02:08",{"source":8,"skillName":5,"commands":48,"prompt":58,"zipAvailable":59},[49,52,55],{"tool":50,"command":51},"npx","npx skills add LIJALEN23\u002FBeryl --skill social-media-content-calendar",{"tool":53,"command":54},"bunx","bunx skills add LIJALEN23\u002FBeryl --skill social-media-content-calendar",{"tool":56,"command":57},"pnpm","pnpm dlx skills add LIJALEN23\u002FBeryl --skill social-media-content-calendar","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FLIJALEN23\u002FBeryl\u002Fblob\u002Fmaster\u002Flocal-agent\u002Foptional-skills\u002Fcreative\u002Fsocial-media-content-calendar\u002FSKILL.md",true,[],[62,69,76,83,90,97],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7BGCRH58RARQTF3R8CZ84DB","test-driven-development","TDD: enforce RED-GREEN-REFACTOR, tests before code.","https:\u002F\u002Fgithub.com\u002FLIJALEN23\u002FBeryl\u002Fblob\u002Fmaster\u002Flocal-agent\u002Fskills\u002Fsoftware-development\u002Ftest-driven-development\u002FSKILL.md",[],[],{"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":19},"01M7BGCK0GGNV3K6NWMM0MDN3W","systematic-debugging","4-phase root cause debugging: understand bugs before fixing.","https:\u002F\u002Fgithub.com\u002FLIJALEN23\u002FBeryl\u002Fblob\u002Fmaster\u002Flocal-agent\u002Fskills\u002Fsoftware-development\u002Fsystematic-debugging\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":19},"01M7BGCF0TAZPKSM4WMYA27XGD","spike","Throwaway experiments to validate an idea before build.","https:\u002F\u002Fgithub.com\u002FLIJALEN23\u002FBeryl\u002Fblob\u002Fmaster\u002Flocal-agent\u002Fskills\u002Fsoftware-development\u002Fspike\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":19},"01M7BGCBH01YYYBQWR7ZFRMX27","simplify-code","Parallel 4-agent cleanup of recent code changes.","https:\u002F\u002Fgithub.com\u002FLIJALEN23\u002FBeryl\u002Fblob\u002Fmaster\u002Flocal-agent\u002Fskills\u002Fsoftware-development\u002Fsimplify-code\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":19},"01M7BGC8MGHS5SRJ3NZYYNAKJY","requesting-code-review","Pre-commit review: security scan, quality gates, auto-fix.","https:\u002F\u002Fgithub.com\u002FLIJALEN23\u002FBeryl\u002Fblob\u002Fmaster\u002Flocal-agent\u002Fskills\u002Fsoftware-development\u002Frequesting-code-review\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":19},"01M7BGC4HB5ZJP5N19MZTZXKZ1","python-debugpy","Debug Python: pdb REPL + debugpy remote (DAP).","https:\u002F\u002Fgithub.com\u002FLIJALEN23\u002FBeryl\u002Fblob\u002Fmaster\u002Flocal-agent\u002Fskills\u002Fsoftware-development\u002Fpython-debugpy\u002FSKILL.md",[],[]]