agentleFS
mia-pppmia-ppp/PMM-Skills/skills/marketing-copy/SKILL.md

marketing-copy

Skill2 starsChanged 30 days agoMITView on GitHub

Produce marketing artifacts from approved positioning and messaging. Use for copywriting, copy editing, homepage and landing copy, Seven Sweeps, proofreading and content refresh. Modes are draft, edit and refresh; independent quality and messaging reviews remain separate.

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

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

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 2

    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 ../_shared/evidence-gaps.md and ../_shared/ssot-consumption.md.

    line 12
  2. Very specific:

    Read ../_shared/segment-selection.md when an audience decision is needed.

    line 14
  3. Very specific:

    Do not edit SSOT. Route proposed canon changes to ssot-context-loop for human review and approval.

    line 16
  4. Distinctive:

    Draft: Read draft methodology. Clarify audience, page role, intended action, source message, proof and constraints.

    line 20
  5. Distinctive:

    Edit: Read Seven Sweeps. Preserve intent and voice.

    line 21
  6. Very specific:

    Read ../_shared/creative-brief.md when commissioning visuals or a demo narrative and ../_shared/behavioral-principles.md only when a …

    line 29

“Common” is measured: kept by at least 6 in 10 of the 3 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

Marketing Copy

Approved context and evidence

Read ../_shared/evidence-gaps.md and ../_shared/ssot-consumption.md. Load only relevant approved manifest context and record sources in Inputs and assumptions. Read ../_shared/segment-selection.md when an audience decision is needed; inherit accepted segments and ICP. Separate sources, interpretation, and proposals. Missing evidence remains Assumed or Gap. Do not edit SSOT. Route proposed canon changes to ssot-context-loop for human review and approval.

Modes

  • Draft: Read draft methodology. Clarify audience, page role, intended action, source message, proof and constraints. Develop structure, benefits, specific headlines and CTAs before final copy.
  • Edit: Read Seven Sweeps. Preserve intent and voice; sweep clarity, voice/tone, so-what benefits, proof, specificity, emotion and risk. Explain consequential edits and return an edited artifact, not just advice.
  • Refresh: First identify what became stale: product truth, buyer needs, proof, traffic intent, links or dates. Compare refresh versus rewrite by scope of changed meaning. Preserve effective structure and voice when strategy remains valid; request approval for upstream changes before a strategic rewrite. Apply the drafting or editing reference to affected sections.

Workflow and required output

Record Inputs and assumptions, mode, audience, originating brief, approved message, proof sources and unsupported claims. Use plain English, concrete benefits and credible commitments. Do not invent metrics, endorsements, roadmap, scarcity or guarantees. Produce ready-to-review copy, meaningful alternatives where requested, explained edits/change rationale, proof-check results, owner handoffs and ranked Evidence gaps. Keep proof gaps out of customer-facing claims as required by the evidence contract. For listings, read description templates: vary channel expression while preserving approved strategic meaning. Read ../_shared/creative-brief.md when commissioning visuals or a demo narrative and ../_shared/behavioral-principles.md only when a behavioral hypothesis helps the brief.

Ownership

positioning-strategy owns competitive meaning; messaging-framework owns reusable message architecture. This skill expresses those decisions in artifacts. Email sequences, cold outbound, social and ad batches route to their specialized execution owners. Editing does not certify its own output: output-quality-check checks originating requirements, messaging-consistency-audit checks approved meaning, and launch-readiness-check checks launch-wide readiness.

Related skills

positioning-strategy, messaging-framework, email-sequence, cold-email, social-content, ad-creative, output-quality-check, messaging-consistency-audit, launch-readiness-check.

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.