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

campaign-brand

Skill4 starsChanged 3 months agoApache-2.0View on GitHub

Define and enforce durable campaign voice, terminology, naming, CTA, spoiler, accessibility, and prohibited-claim rules so trailers, social copy, press materials, and promotional art stay recognizably consistent.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    Read ../../references/CAMPAIGN_BRAND.md, campaign state, canon, verified release facts, and approved writing samples when available.

    line 11
  2. Distinctive:

    Keep campaign voice separate from character dialogue voice.

    line 14
  3. Distinctive:

    Use examples as calibration, not text to copy repeatedly.

    line 15
  4. Very specific:

    Run scripts/campaign_content.py PROJECT --validate when campaign copy and lineage exist.

    line 16

≈ “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

Campaign Brand

  1. Read ../../references/CAMPAIGN_BRAND.md, campaign state, canon, verified release facts, and approved writing samples when available.
  2. Write 06_release/social/brand_voice.json.
  3. Define voice attributes, perspective, preferred and avoided vocabulary, CTA behavior, spoiler limits, accessibility tone, exact naming rules, and prohibited claims.
  4. Keep campaign voice separate from character dialogue voice.
  5. Use examples as calibration, not text to copy repeatedly.
  6. Run scripts/campaign_content.py PROJECT --validate when campaign copy and lineage exist.

Done when downstream promotional writing can be checked against an explicit project voice rather than guessed from memory.

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.