[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CTJSV8E95PCZAVQMQ8GYB5":3,"skill-same:01M7CTJSV8E95PCZAVQMQ8GYB5":59},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":39,"commitSha":40,"skillDirectory":41,"forksCount":13,"repositoryHtmlUrl":42,"repositoryHomepageUrl":6,"ownerHtmlUrl":43,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":44,"install":45,"resources":58},"01M7CTJSV8E95PCZAVQMQ8GYB5","social-media-content-calendar",null,"Plan multi-platform social campaigns: briefs to posting.","dwikanugraha13\u002FProject-Anara","dwikanugraha13","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F63535036?v=4","01M7CTBN0DG8GDNP4QZ68W8M0A","01M7CTBN10Q015JDBYJS6AJRGN",0,"MIT","https:\u002F\u002Fgithub.com\u002Fdwikanugraha13\u002FProject-Anara\u002Fblob\u002Fmain\u002Fbackend\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), Anara Agent\nlicense: MIT\nplatforms: [linux, macos, windows]\nmetadata:\n  anara:\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":23,"license":14,"version":24,"metadata":25,"platforms":35,"description":7},"Ben Barclay (benbarclay), Anara Agent","0.1.0",{"anara":26},{"tags":27,"related_skills":32},[28,29,30,31],"Social-Media","Content-Calendar","Campaigns","Publishing",[33,34],"xurl","humanizer",[36,37,38],"linux","macos","windows","main","3e6d6b7ffb6ab43ddf3991509e5cfb5f8c90cd1a","backend\u002Foptional-skills\u002Fcreative\u002Fsocial-media-content-calendar","https:\u002F\u002Fgithub.com\u002Fdwikanugraha13\u002FProject-Anara","https:\u002F\u002Fgithub.com\u002Fdwikanugraha13","2026-10-13 07:57:21",{"source":8,"skillName":5,"commands":46,"prompt":56,"zipAvailable":57},[47,50,53],{"tool":48,"command":49},"npx","npx skills add dwikanugraha13\u002FProject-Anara --skill social-media-content-calendar",{"tool":51,"command":52},"bunx","bunx skills add dwikanugraha13\u002FProject-Anara --skill social-media-content-calendar",{"tool":54,"command":55},"pnpm","pnpm dlx skills add dwikanugraha13\u002FProject-Anara --skill social-media-content-calendar","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdwikanugraha13\u002FProject-Anara\u002Fblob\u002Fmain\u002Fbackend\u002Foptional-skills\u002Fcreative\u002Fsocial-media-content-calendar\u002FSKILL.md",true,[],[60,67,73,81,88,95],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":18},"01M7CVK8W5MPQ8H45A6XE6RPK1","youtube-content","YouTube transcripts to summaries, threads, blogs.","https:\u002F\u002Fgithub.com\u002Fdwikanugraha13\u002FProject-Anara\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fyoutube-content\u002FSKILL.md",[],[],{"skillNo":68,"name":33,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":18},"01M7CVK56KG9399ZZVE9KM54WS","X\u002FTwitter via xurl CLI: raw post search, posting, DM, media.","https:\u002F\u002Fgithub.com\u002Fdwikanugraha13\u002FProject-Anara\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fxurl\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":77,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":18},"01M7CVK22A44A88NPPBAC1FVQP","xlsx","Create, read, edit Excel .xlsx workbooks and CSVs.","https:\u002F\u002Fgithub.com\u002Fdwikanugraha13\u002FProject-Anara\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fxlsx\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fdwikanugraha13\u002FProject-Anara\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fxlsx\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":18},"01M7CVJX88C8PY2T6RQZ5GCG15","weights-and-biases","W&B: log ML experiments, sweeps, model registry, dashboards.","https:\u002F\u002Fgithub.com\u002Fdwikanugraha13\u002FProject-Anara\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fweights-and-biases\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":18},"01M7CVJR3W1FBRGC56DG6BJ1Y3","weekly-review-planning","Weekly reset: commitments, stalled work, next-week plan.","https:\u002F\u002Fgithub.com\u002Fdwikanugraha13\u002FProject-Anara\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fweekly-review-planning\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":18},"01M7CVJGPJNPQDM8S1KTTMJN7M","touchdesigner-mcp","Control TouchDesigner via twozero MCP.","https:\u002F\u002Fgithub.com\u002Fdwikanugraha13\u002FProject-Anara\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Ftouchdesigner-mcp\u002FSKILL.md",[],[]]