agentleFS
link7373link7373/agentic-sales-marketing/.claude/skills/create-content/SKILL.md

create-content

Skill1 starsChanged 3 months agoMITView on GitHub

Plan and produce a content batch — platform-native social posts, SEO articles, email newsletter issues — on the give-value-then-ask rhythm, batched for one publishing approval. Run weekly or per the strategy's cadence.

The file

Files
SKILL.md

/create-content — Earn Attention Before Asking

Inputs: knowledge/strategy.md (channels + cadence), knowledge/positioning.md, knowledge/audience-profiles.md, knowledge/content-calendar.md, performance notes in knowledge/content/. Agents: content-marketer leads; copywriter drafts; tools-operator schedules/publishes. Method: knowledge/methods/content-and-social.md, knowledge/methods/digital-channel-strategy.md (SEO).

Steps

  1. Review what's working. Last batch's numbers: formats and topics that earned engagement get more; underperformers get one more fair try or the axe.
  2. Plan the batch. Fill templates/content-calendar.md for the period: topics from customer questions/language, formats native to each platform, give/ask ratio enforced (several value pieces per ask; asks contain exactly one plain CTA).
  3. Draft natively. Each piece crafted for its platform's format, tone, and consumption speed — no verbatim cross-posting. Two-second test on every piece: hook/image/first line carries the value.
  4. SEO pieces: target one real question per article, answer it better than what currently ranks, structure for scanning. Marketplace businesses: treat listing titles/tags as the SEO surface.
  5. Quality pass. Voice check (standards/voice.md), claims check including the Claims Review Checklist (standards/compliance.md), positioning alignment. Where a piece makes or implies a results claim, pull real proof from knowledge/research/social-proof.md rather than asserting.
  6. Batch approval. Present the whole calendar to the operator at once — the publishing gate covers the batch; approved pieces post on schedule without further asks.
  7. Schedule & publish. tools-operator loads the batch into the scheduler (or posts on cadence). Confirm each goes live.
  8. Log performance as results land; feed next batch's step 1.

Before you start

  1. Required inputs: knowledge/strategy.md approved (content must serve a chosen channel), knowledge/positioning.md at seeded+, standards/voice.md Brand voice section (or house defaults if not yet defined).
  2. Scan knowledge/decision-log.md for tags content, channel, voice. For SEO articles, check knowledge/research/ for any /grow-seo briefs — those take priority over invented topics.
  3. Gate check: publishing gate covers the batch (step 6); nothing posts without the batch approval ref.

If things go wrong

  • Scheduler unavailable/unauthorized → publish manually on cadence via guided steps, or park the approved batch in knowledge/pending.md with its schedule.
  • Batch approval doesn't come before the first slot → nothing posts; slide the calendar rather than posting unapproved.
  • A piece's platform rejects it (policy, format) → adapt per platform rules or swap in the next calendar item; log the rejection reason in knowledge/content/.

Outputs

An approved, scheduled content batch; updated rolling calendar. Content batches live in knowledge/content/YYYY-MM-<slug>/. Close with the report per templates/skill-report.md.

Writeback

knowledge/content-calendar.md; drafts + results to knowledge/content/; approval to knowledge/approvals-log.md; content decisions (tag: content) to knowledge/decision-log.md.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.