marketing-machine
Own the whole marketing content pipeline for this codebase — set itself up, scan the product for what actually works, write the copy, enforce the rules mechanically, and render cards (PNG) and video (MP4) from one HTML contract. Use for "set up marketing", "write a post", "review this copy", "make a card for this", "render a video", "scan the product", or "do the whole thing".
cagatayuncu · Static checks on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add cagatayuncu/marketing-machine --skill marketing-machineAbout this skill
name: marketing-machine description: Own the whole marketing content pipeline for this codebase — set itself up, scan the product for what actually works, write the copy, enforce the rules mechanically, and render cards (PNG) and video (MP4) from one HTML contract. Use for "set up marketing", "write a post", "review this copy", "make a card for this", "render a video", "scan the product", or "do the whole thing". allowed-tools: Read, Write, Edit, Glob, Grep, Bash
marketing-machine
Argument: $ARGUMENTS — what to do. Examples:
setup · write post about inventory turnover · review marketing/posts/12-report.md ·
card 12 · video intro · scan · everything
This skill owns the pipeline end to end. Nobody should need to read a README or run a script by hand: if something is missing, set it up; if a command fails, read its error and act on it.
Toolchain path: <TOOLCHAIN>. If that still reads as a placeholder (angle brackets intact), this
skill arrived without init having run — resolve the path yourself, first match wins:
$CLAUDE_PLUGIN_ROOTis set in your environment → that directory IS the toolchain (plugin install; scripts, rules and templates travel with it).- A
TOOLCHAINfile sits next to this SKILL.md → its single line is the path. - Neither → the toolchain is not on this machine yet. Clone it, then continue:
git clone https://github.com/cagatayuncu/marketing-machine ../marketing-machineand use../marketing-machine.
Every command below runs from the host repo root.
The chain
setup ──▶ scan ──▶ (human confirms facts) ──▶ write ──▶ visual / video ──▶ lint ──▶ report
│ ▲
└── config, fonts, brand roles, CI gate every output goes through here
Asked to do "everything", walk the whole chain and stop at the two points that genuinely need a human: confirming which product facts are true, and deciding which claims are defensible. Never invent an answer to either.
0 · Orient
First, check whether the machine is installed: is there a marketing.config.json at the repo
root?
- No → go to §1 SETUP. Do not try anything else first; every other command needs the config.
- Yes → run doctor, then load context:
node <TOOLCHAIN>/scripts/doctor.mjs
If doctor reports a failure, fix it (§1.3 covers the two common ones). Do not proceed with a red doctor: a missing font or an unmapped brand role produces output that looks fine and is wrong.
Doctor also reports whether this machinery is current — skill copy (does the installed skill
still match the toolchain that drives it) and toolchain version (is the toolchain behind its
upstream repository). Neither blocks work, but do not swallow them: tell the user in one line and
name the fix — init --refresh for a stale copy; git pull in the toolchain (or the plugin
marketplace update) for an old version, then init --refresh. If the user says update, update
first: producing content with yesterday's rules and then re-doing it is the expensive order.
Offline is fine — an unreachable upstream reads as unknown, not as a problem to fix.
Then read marketing.config.json and these three files in full (do not skim):
<paths.context>/product-facts.md— what actually works. The single arbiter.<paths.context>/claims.md— which claims are usable<paths.context>/brand-voice.md— tone, bans, word preferences
Read at least two already-published pieces from <paths.posts> to calibrate the voice. If there are
none yet, say so — the first piece has no reference and needs closer review.
1 · SETUP — setup
1.1 Install
Pick the agent target from what the repo already uses: .claude/ present → claude,
.cursor/ → cursor, AGENTS.md → agents. If several or none, ask.
node <TOOLCHAIN>/scripts/init.mjs --agent <target>
Read the output carefully and relay it: it lists what was derived from the codebase and what could not be. That report is the only place naming the fields still needing a human.
1.2 Interview
init reports what it derived. Now ask about what a codebase cannot know. Ask these as one short
conversation, not one question at a time, and write the answers where they belong.
Content language. init infers one from the locale files, but the product's interface
languages and the marketing language are different decisions. A product whose UI ships in three
languages may market in one; a product with no localisation at all still markets in something. Ask
which language the copy will be written in, and if the product ships several, ask whether marketing
follows all of them or starts with one.
If the answer differs from what was inferred:
node <TOOLCHAIN>/scripts/init.mjs --refresh --lang <code>
That re-derives the language-dependent pieces — the rule pack, the verification-table heading, the
verify marker — while keeping paths, channels and anything already tuned. Do not hand-edit
language.primary on its own; the rule pack and the in-content headings move with it.
If there is no rule pack for that language yet, say so plainly: only the structural rules will be
enforced, the vocabulary bans will not, and someone has to write rules/lang.<code>.json for that
half to exist.
Channel. Which surface is this for — a social feed, a blog, email, a landing page? It sets the
card and video geometry, and it decides the post anatomy. Do not set up channels nobody asked for;
config.channels ships three geometries and one of them is usually enough to start.
Audience. Fill <paths.context>/audience.md from the answers: who they are, the words they use
for the problem, what they already tried, the first objection, and who this is explicitly not for.
That last one matters — without it the copy drifts vague.
Product. product.oneLiner in the user's own words, and product.stage. Do