skills/social-media-scheduling/SKILL.md
Use this skill when planning and packaging a full period of social media content for scheduling. Triggers on content calendars, posting cadence, content pillars, launch campaigns, social post queues, approval-ready post packages, and adapting one source asset across platforms.
npx skillsauth add absolutelyskilled/absolutelyskilled social-media-schedulingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Plan a scheduling-ready period of social content. The goal is not just to write posts. The goal is to turn a campaign goal, audience, channels, and constraints into a coherent queue that can be reviewed, approved, and scheduled.
This skill works for SaaS, AI tools, creator businesses, agencies, launches, and founder-led marketing.
Use this skill when the user wants to:
Do NOT use this skill for:
Gather or infer:
If the user only provides a rough goal, start with a lightweight assumptions block and proceed.
Create or confirm:
Assign a realistic weekly rhythm:
| Platform | Weekly Posts | Role | Formats | Notes | | --- | --- | --- | --- | --- |
Primary channels get original posts. Secondary channels get adapted or lighter posts. Do not recommend a high-volume video cadence unless production capacity exists.
Create a scheduling-ready table:
| Date | Time | Platform | Pillar | Angle | Format | CTA | Asset | Status | | --- | --- | --- | --- | --- | --- | --- | --- | --- |
Use status values:
readyneeds editneeds assetneeds fact checkblockedFor each important slot, produce platform-native copy:
End with a reviewable package:
| ID | Date | Time | Platform | Copy Status | Asset | CTA | Review Note | | --- | --- | --- | --- | --- | --- | --- | --- |
Then include final copy blocks by ID.
## Strategy
- Period:
- Audience:
- Goal:
- Primary CTA:
- Cadence:
- Assumptions:
## Pillars
| Pillar | Purpose | Formats | Proof Source | Ratio |
| --- | --- | --- | --- | --- |
## Calendar
| Date | Time | Platform | Pillar | Angle | Format | CTA | Asset | Status |
| --- | --- | --- | --- | --- | --- | --- | --- | --- |
## Final Copy
### [ID] [Platform]
[copy]
## Review Notes
- [claim, asset, or approval item]
The output can be used with any social scheduling workflow. It is especially useful with agent-driven posting pipelines and MCP-compatible schedulers such as AgentReacher, where the final table can become scheduled drafts or review tasks.
For the full AgentReacher social campaign skill pack:
npx skills add agentreacher/skills --all
development
Use when the user wants to simplify, clean up, refactor, tidy, or refine code — their staged/unstaged git changes or a target file/path. Reduces complexity, flattens nesting, removes redundancy and dead code, scores each change by value (holding low-value churn), then runs tests to prove nothing broke. Invoke on: "simplify", "simplify this", "simplify my code/changes", "clean up", "clean this up", "clean up my changes", "refactor this", "make this cleaner", "tidy this up", "reduce complexity", "flatten this", "remove dead code", "make it more readable", "polish before commit", or "absolute simplify". Acts on your working diff; for repo-wide dead code use absolute-prune; for lint/type debt use absolute-debt.
testing
Dependency upgrades: outdated/vulnerable deps planned into semver waves (patch/minor batched, majors gated and changelog-read), applied incrementally with lockfiles regenerated and tests green after each. Runs on green main. Triggers on "absolute upgrade", "upgrade our dependencies", "bump deps", "update packages", "move off the deprecated X", "clear the Dependabot backlog".
development
Lightweight standalone design spec for AI coding agents: codebase scan → bounded clarify pass (3–5 questions, not a grill) → reviewed design doc written to docs/plans/ → independent scored review → stop. No task board, no build. Use when you want a spec to discuss, hand off, or review before committing to implementation. Chains into absolute-work when ready to build. Triggers on "absolute spec", "write a spec", "spec out this feature", "draft a design doc", "I want a spec to hand off / review, don't build it yet".
tools
Dead code and dependency cleanup, repo-wide: unused deps, unreferenced exports, unreachable code, orphaned files — removed only with tool evidence, in reversible waves. Runs on green main. For diff-scoped cleanup use absolute-simplify. Triggers on "absolute prune", "remove dead code", "find unused deps/exports", "what can we delete", "clean up orphaned files".