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

social-copy

Skill4 starsChanged 3 months agoApache-2.0View on GitHub

Write coordinated campaign captions, hooks, calls to action, accessibility text, hashtags, keywords, and platform variants using verified release facts and an explicit no-invented-claims rule.

2 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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

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

    Read the campaign brief, one or more SOC-### deliverables, verified release facts, tone rules, spoiler policy, and the actual media being …

    line 13
  2. Very specific:

    Write 06_release/social/copy.jsonl using stable COPY-### IDs.

    line 14
  3. Distinctive:

    Avoid repeating identical copy across every platform when placement context differs.

    line 18
  4. Very specific:

    When present, read 06_release/social/brand_voice.json before drafting.

    line 26

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “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 Copy

Workflow

  1. Read the campaign brief, one or more SOC-### deliverables, verified release facts, tone rules, spoiler policy, and the actual media being promoted.
  2. Write 06_release/social/copy.jsonl using stable COPY-### IDs.
  3. Separate hook, body, CTA, accessibility description, hashtags, and keywords.
  4. Cite or list the verified project facts used by each copy record.
  5. Omit unresolved release dates, URLs, ratings, awards, review quotes, and availability claims.
  6. Avoid repeating identical copy across every platform when placement context differs.

Done

Each deliverable that needs text has destination-appropriate copy grounded only in verified project information.

Brand and evidence controls

When present, read 06_release/social/brand_voice.json before drafting. Record factual public claims with CLAIM-### references and validate them through campaign_content.py. Record each transformed public content item in content_lineage.jsonl so repurposing does not silently change facts, spoilers, or campaign promises.

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.