sickn33/agentic-awesome-skills / plugins/aasb-aas-localization-international-growth/skills/content-creator
content-creator
UnverifiedDraft and review audience-specific content using supplied brand examples, local text diagnostics, and adaptable channel templates.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 9.8 KB |
| assets/content_calendar_template.md | markdown | 1.8 KB |
| references/brand_guidelines.md | markdown | 6.3 KB |
| references/content_frameworks.md | markdown | 10.8 KB |
| references/social_media_optimization.md | markdown | 3.6 KB |
| scripts/brand_voice_analyzer.py | script | 7.5 KB |
| scripts/seo_optimizer.py | script | 14.1 KB |
references/social_media_optimization.md
View on GitHub# Social media adaptation and verification
Use the actual audience, approved claims, account capabilities and production budget.
A platform name does not identify a demographic or guarantee engagement. Previous
fixed posting times, hashtag quotas and reach multipliers were unsupported and have
been retired from this guide.
## Choose the channel by the task
| Channel | Drafting focus | Check before handoff |
| --- | --- | --- |
| LinkedIn | Explain a professional problem with a specific example | Current post/document options, accessible preview, permitted mentions |
| X | Put the useful fact first; split only when needed | Current account character/media limits and thread order |
| Instagram | Ensure the visual communicates and the caption adds context | Current feed/Reel/Story composer, crop, captions, alt-text support |
| Facebook | Give the relevant community context and practical next step | Page/group permissions, current composer, link preview |
| TikTok | Demonstrate one clear idea with readable captions | Current duration/audio rights, safe crop and native preview |
Check these details in the current native composer and the platform's official help.
Do not bypass account restrictions, upload a test publicly, or acquire new paid tools
just to complete a draft. Use existing tools and authorized read-only account data.
## Adapt without changing the facts
1. Identify one audience question and the approved source that answers it.
2. Draft the shortest complete answer for that channel. Preserve qualifications,
prices, dates and limitations from the source.
3. Preview text, links, crops, contrast and captions. Do not put essential information
only in an image. Use relevant tags and mentions; avoid engagement bait.
4. Confirm rights for music, images and user content, and the required disclosures
with the campaign owner. This checklist is not a legal compliance determination.
5. Return draft, assets, source links and a suggested slot with timezone. Sending or
scheduling needs the user's existing authorization; do not infer it from drafting.
## Measure an actual question
Start with one outcome such as qualified visits to a help article. Define denominator,
window, timezone, source and missing-data handling before comparing posts. Separate
reach, impressions, clicks, saves and conversions; platforms define them differently.
An engagement rate can be interactions / reach when those counts cover the same
population and window. If reach is zero or unavailable, report no rate, not zero.
Attribution does not establish causality. A small successful post is not proof of an
algorithm rule or a universally optimal time.
Test a small number of timing/format hypotheses using account evidence and comparable
content. Record audience, creative, paid support and seasonality as possible confounders.
Use the content calendar's performance review to retain useful lessons, with no hidden
analytics or automatic export of account data.
## Worked adaptation
For an approved help article about CSV export, prepare a product screenshot with
captions and a short explanation of where export lives. Link to the source where the
channel supports it. Verify the destination and crop in preview. Record the proposed
publication time as a hypothesis, not an optimal slot. Expected handoff: a reviewable
draft and preview checks; no post is sent and no engagement increase is claimed.
## Community and incidents
Respond within the team's agreed coverage, with verified facts and an owner. Do not
invent an incident cause or promise a resolution deadline. Escalate sensitive cases
through the existing process; a draft response is not authorization to send it.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |