Localized reading guide
social-content-enginePurpose, usage and source
Runs the owner's content operation as a standing thing rather than a one-off: keeps a rolling posting calendar, learns the owner's voice, generates on-brand Canva graphics, writes captions that sound like them, repurposes one asset into every channel format, and stages posts for approval instead of publishing on its own. Pulls product photos and prices from Shopify when connected; with no connectors, drafts the calendar and asset briefs for manual posting. Use this whenever the owner talks about posting, content, or social — including "I need to post more," "we've gone quiet on Instagram," "what should we post this month," "make the content," "give me a month of posts," "write this in my voice," "repurpose this," or "set up our content calendar." Reach for it for a single post as readily as for a full quarter. One handoff: a finished, approved campaign brief goes to canva-creator; this skill owns the standing operation.
Source retrieved:
- Source repository
- anthropics/knowledge-work-plugins
- SKILL.md
small-business/skills/social-content-engine/SKILL.md- Repository stars
- 34,049
- Repository updated
- 2026-10-30
- Categories
- Business
- Last collected
License: Apache-2.0
Workflow excerpts are reading aids, not executable instructions from Codez. No third-party Skill was run to produce this page.
The purpose and workflow passages below are upstream material, organized and translated for reading. They are distinct from the separately labeled Codez editorial analysis.
What this Skill does
Runs the owner's content operation as a standing thing rather than a one-off: keeps a rolling posting calendar, learns the owner's voice, generates on-brand Canva graphics, writes captions that sound like them, repurposes one asset into every channel format, and stages posts for approval instead of publishing on its own. Pulls product photos and prices from Shopify when connected; with no connectors, drafts the calendar and asset briefs for manual posting. Use this whenever the owner talks about posting, content, or social — including "I need to post more," "we've gone quiet on Instagram," "what should we post this month," "make the content," "give me a month of posts," "write this in my voice," "repurpose this," or "set up our content calendar." Reach for it for a single post as readily as for a full quarter. One handoff: a finished, approved campaign brief goes to canva-creator; this skill owns the standing operation.
How the upstream workflow works
Step 1 — Learn the voice before writing anything
Read the shared voice profile. Every skill that writes in the owner's name reads the same file, so a correction the owner makes once holds everywhere. If no profile exists, build one from their existing posts, newsletter, and sent mail, then confirm it. Do not guess a personality — a guessed voice produces exactly the generic copy the owner came here to avoid.
Upstream passage · L27 ↗Step 2 — Hold the calendar, don't rebuild it
Read reference/calendar.md for the standing-calendar format and cadence guidance. The calendar is the durable artifact. On each run, show what is scheduled, what has published, and what gaps are coming, then extend the horizon rather than starting over. Every row carries a Path column routing it to Canva or to text-only drafting. Email rows are always text-only. Canva is used for social posts only — Instagram, Facebook, X, LinkedIn. No email templates, no autofill, no design copies, no asset uploads, no exports for an email row. Email graphics are out of scope for this skill: Canva email autofill fills unused image slots with stock placeholder graphics, and its preview thumbnails do not render in chat. If the owner asks for a Canva email design, see reference/gotchas.md for the redirect.
Step 3 — Pull the source material
With Shopify connected, product images, titles, descriptions, and prices flow in directly — no manual upload and no retyped price. Read reference/shopify-assets.md for the mapping into design fields. With no Shopify, the source is the brief, the owner's photo folder, or the brand kit in Canva. That is a complete path; it just costs the owner an upload. Never restate a price, a discount, or an inventory count the connector did not return. A wrong price in a public post is the most expensive error this skill can make.
Generation budget for this batch:
Canva rows: 8
Candidates per row: 3 (default — say "single candidate" for 1)
Total designs: 24
API calls (approx): ~120
Canva's limit is 100 requests a minute. This runs about 2-3 minutes,
comfortably inside it. Proceed?Requirements and setup
No short requirements passage was selected from this file. This does not mean the Skill has no dependencies. Check the repository setup instructions and referenced files.
Limits and quality checks
Step 9 — Stage publishing, never publish
Read reference/publishing.md for field-level detail and fallbacks. HubSpot social staging on Marketing Hub Professional, otherwise a scheduling CSV the owner imports into whatever tool they already use. In every path the post is staged, never published — the owner controls go-live and can still cancel or edit. Check every scheduled time is actually in the future before staging; calendars built weeks ago quietly go stale.
Start with a safe trial
- Check the supported host and the repository installation instructions. Keep the Skill directory and its referenced scripts, assets and documentation together; SKILL.md alone may omit dependencies.
- Give the agent your real input, desired output and acceptance criteria. Invocation syntax and available tools depend on the host; this site does not assume a universal install command.
- Try the source workflow in a disposable project or on a copy. Review operations that change files, remote services or billable resources before allowing them.
- Validate the output against the source quality checks and your own requirements. A successful trigger or a high repository Star count does not establish a correct result.
Read further in the source
- Social Content Engine
- Step 1 — Learn the voice before writing anything
- Step 2 — Hold the calendar, don't rebuild it
- Step 3 — Pull the source material
- Step 4 — Set the generation budget before generating
- Step 5 — Inventory every image slot, one slot at a time
- Step 6 — Generate one calendar row at a time
- Step 7 — Repurpose instead of regenerating
- Step 8 — Write the copy in the owner's voice
- Step 9 — Stage publishing, never publish
- Closing offer
- What not to do
- Reference files
- Using a tool that isn't listed
Related Skills
Translation and scope
This reading guide selects passages from the pinned upstream SKILL.md. Translation is assisted. It is not a complete manual or a claim of tested compatibility. Read the original and its referenced files before use.
This introduction refers to the pinned version below; current repository activity and collection time are shown separately.
- Pinned source
- Read the original ↗
- Source retrieved
- Source commit
2574e29377c7173d0cecffef29a6ecbd7f8ccb5d- Source SHA-256
e1743fff779f221ba0570b0fe712a358482e7dc150c11fd8d1e45ebcceaf35a5