agentleFS
pradeep-sankaran-07pradeep-sankaran-07/team-os-gdrive-template/.agents/skills/acme-marketing/SKILL.md

acme-marketing

Skill0 starsChanged 2 months agoMITView on GitHub

How Acme Corp writes publicly and what it is allowed to claim. Use when the output will be READ BY SOMEONE OUTSIDE THE COMPANY as Acme's own marketing or public communication, whatever the format: blog post, landing or comparison page, press release, social copy, email campaign, ad copy, case study, brochure, whitepaper, video script, event collateral. Also use to check whether a claim is cleared to publish. Triggers: "write a blog post about...", "draft a landing page", "write the copy for...", "a comparison page vs <competitor>", "write a case study", "is it OK to say that we...", "how do we position...". NOT for internal material however polished: roadmaps, status reports, internal decks, ops dashboards, board material are acme-brand alone. NOT for a prospect decision document (use solution-brief) or a call write-up (use customer-call-summary).

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If you cannot tell whether the output is internal or public, ask one short question before writing.

    line 40
  2. Distinctive:

    If a claim you want is not in the file, write the copy without it and list it under "not cleared" for a human to decide.

    line 57
  3. Very specific:

    Every number traces to references/claims.md with its basis.

    line 77
  4. Distinctive:

    Every named customer has recorded permission.

    line 78
  5. Distinctive:

    No competitor is characterised, only described.

    line 79

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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

Acme marketing

This skill is mandatory by audience, not by format. Ask one question: will someone outside the company read this as Acme speaking for itself? If yes, this applies, whatever it is. If it is internal, it does not apply however polished the document is.

Format and audience are separate questions. Answer both: acme-brand almost always runs alongside this one.

Step 1 - Establish the audience

If you cannot tell whether the output is internal or public, ask one short question before writing. Guessing wrong in either direction is expensive: an internal doc run through a marketing pass reads like a press release to your own team, and a public page written without one makes claims nobody cleared.

Step 2 - Check every claim against references/claims.md

That file is the list of what Acme may say in public, each claim paired with its basis. The rules:

  • A number may be published only if it is in that file, and it is published with the comparison basis it was measured against. A number without its basis is not a claim, it is a shape.
  • A customer may be named only where accounts/<slug>/profile.md records permission.
  • Competitors are described by capability, never by characterisation. "Their product does not do X" needs a source; "they are worse at X" is not publishable.
  • If a claim you want is not in the file, write the copy without it and list it under "not cleared" for a human to decide. Do not soften an uncleared claim into a vaguer version of itself and publish that.

Step 3 - Write

House voice: plain, specific, short sentences. Say what the product does and for whom. No superlatives, no "revolutionary", no invented urgency. Rule 0 applies with full force here, because marketing copy is where mannered prose hides best.

Structure any page as: the problem in the reader's words, what Acme does about it, the proof, what to do next.

Step 4 - Record

File the draft to the author's outputs/ folder. Add one line to _ops/log.md. Public copy is never published straight from a skill run.

Review before delivering (required)

  • Every number traces to references/claims.md with its basis.
  • Every named customer has recorded permission.
  • No competitor is characterised, only described.
  • No em dashes.
  • A human has read it end to end and approved publication.

Things that have gone wrong before

  • Never publish a number without its comparison basis. Why: a figure quoted bare invites the reader to assume the most flattering baseline, and the first prospect who asks "compared with what" gets an answer that undercuts the claim. (2026-09-16)

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.