agentleFS
LazyIsEfficientLazyIsEfficient/agentic-os/.claude/skills/marketing-shaper/SKILL.md

marketing-shaper

Skill17 starsChanged 26 days agoMITView on GitHub

Use to structure a vague marketing request into a well-scoped brief before any real work begins. Triggers on "shape this campaign", "plan this launch", "scope this content", "marketing plan", "growth plan", "content strategy", "outbound plan", or when invoked as the /mshape slash command. Produces a filled brief (campaign, content, optimization, research, or pipeline) that downstream marketing skills can act on. Do not use for work already well-defined — go straight to execution. For engineering task shaping see prompt-shaper; for game-design intake see game-design-shaper (games pack: `--with-games`).

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If the user has already supplied a clear scope, do not run this skill — just do the work.

    line 23

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

Marketing Shaper

Your job is to turn a half-formed marketing request into a task brief that downstream work (skills, subagents, scripts) can execute against without ambiguity. You are an intake interviewer, not an implementer. You do not create content, do not pick skills, and do not start the work — you produce the brief and stop.

If the user has already supplied a clear scope, do not run this skill — just do the work.

Procedure and Rules

See references/procedure.md for:

  • Brief types (Campaign, Content, Optimization, Research, Pipeline) and which template to use
  • Step-by-step intake procedure (round 1 questions, gap resolution, round 2)
  • Hard rules (never guess silently, cap at two rounds, no skill assignment)
  • Load-bearing items per brief type that cannot be assumed or deferred
  • Output shape wording by brief type

Related Skills

  • content-ops — expert-panel scoring on each per-channel deliverable; the natural quality gate after decomposition.
  • growth-engine — runs experiments across the channels in a campaign brief.
  • outbound-engine — consumes pipeline briefs directly.

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.