agentleFS
badgidsbadgids/Story-Film-Skills/skills/social-campaign/SKILL.md

social-campaign

Skill4 starsChanged 3 months agoApache-2.0View on GitHub

Plan a coordinated social-media release campaign with verified facts, audience segments, content pillars, platforms, placements, aspect ratios, deliverable matrix, spoiler rules, accessibility, and a relative or dated campaign calendar.

4 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 1 is distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read ../../references/SOCIAL_CAMPAIGN.md, film/trailer release facts, audience intent, canon, and approved marketing assets.

    line 13
  2. Very specific:

    Write 06_release/social/campaign.json with a CAMP-### ID.

    line 14
  3. Very specific:

    Write 06_release/social/deliverables.jsonl with stable SOC-### IDs.

    line 15
  4. Very specific:

    Create 06_release/social/calendar.csv.

    line 17
  5. Distinctive:

    Never invent ratings, awards, quotes, availability, cast credits, links, or dates.

    line 19

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Social Campaign

Workflow

  1. Read ../../references/SOCIAL_CAMPAIGN.md, film/trailer release facts, audience intent, canon, and approved marketing assets.
  2. Write 06_release/social/campaign.json with a CAMP-### ID.
  3. Write 06_release/social/deliverables.jsonl with stable SOC-### IDs.
  4. Cover requested video, still, key-art, thumbnail, caption, and copy formats.
  5. Create 06_release/social/calendar.csv. Use relative launch phases when exact dates are unknown.
  6. Record verified release facts separately from unresolved facts.
  7. Never invent ratings, awards, quotes, availability, cast credits, links, or dates.
  8. Validate the campaign with scripts/promo_validate.py.

Done

The campaign has a traceable deliverable matrix and no marketing claim depends on an invented fact.

Brand and repurposing state

For multi-asset campaigns, run campaign-brand before copy production and content-repurpose when one approved source is adapted into multiple destinations. CONTENT-### lineage records must preserve source IDs, transformation purpose, claim IDs, spoiler constraints, and destination. Use design-system for coordinated campaign visuals.

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.