A working marketer's skill library for Claude Code

Type a slash command, or describe the problem in your own words. The matching skill asks a couple of questions, reads your files only when you say yes, and does the work.

MIT No API key to start Four categories Two lines to install
~/your-project
>
01

Who it's for

Everything here runs real marketing work every week. It is not a showcase of skill ideas; it's the toolshed, with the sawdust left in.

The whole department

You own SEO, the blog, the ads, the newsletter and the launch, and there is no specialist to hand any of it to. The library is the specialist bench you don't have.

The lead who owns the number

The board slide, the pipeline diagnosis and the campaign read have to come out the same shape every month. Three reporting skills hold the format so the numbers are the only thing that changes.

The consultant across clients

Every client is a different folder and nothing may leak between them. No skill assumes a layout: it scans the folder you launched from, lists what it found, and reads nothing until you say yes.

Not for you if you want a dashboard product, a hosted tool, or an agency retainer. This is a folder of plain-text skills you read, diff and edit, and it only does anything inside Claude Code.

02

The shelf

One folder per skill, each with its own SKILL.md. The folder name is the slash command. Every skill is self-contained — take the whole library or copy one folder.

03

In action

Real output only. Everything below came out of a real run — nothing here is a mockup of what the library might do.

/cinemagraph "Make this hero move, but subtly."

The hero at the top of this repository's README, before and after. Light mode moves only what is already in the image — the dots march, the cursor blinks, current flows along the connectors. Nothing new was drawn. Drag the divider.

The marketing-skills schematic hero, static: three columns of what a marketer types and the command that answers it.
The same schematic hero as a seamless loop: the dot grid marches, the cursor blinks and current flows along the connector strip.
BEFORE · PNG AFTER · LOOP

Shipped as an animated WebP with a static PNG fallback, or a GIF when it has to live in a README. The renderer checks the loop seam, the moving region and the file weight before it hands anything back.

04

How a skill runs

Five stages, the same every time. A number the skill cannot get is written as unknown, never invented.

How a skill runs, in five stages: you say what you need in plain words or a slash command; it asks a couple of questions, one at a time; it scans your folder, lists what it found, and reads files only with your yes; it pulls GA4, Search Console or DataForSEO data when connected, else it asks you; it saves the work as a file you can edit.

Company context works the same way in every skill that needs it: scan the launch folder, list what was found, ask before reading a single file.

05

Take it home

Claude Code discovers skills one folder deep under ~/.claude/skills. This repo nests them by category, so the installer links each skill into place. Your edits land back in the repo, versioned — updating is a git pull.

WINDOWS · POWERSHELL
git clone https://github.com/risukisu/marketing-skills D:\marketing-skills
D:\marketing-skills\install.ps1
MACOS · LINUX
git clone https://github.com/risukisu/marketing-skills ~/marketing-skills
~/marketing-skills/install.sh

Just one skill

Every skill folder is self-contained. Copy it into ~/.claude/skills and it works on its own — no shared runtime, no registry.

Live data, optional

Connect Google Analytics 4 and Search Console and the data-driven skills stop asking you for numbers and start pulling them. Without them, every skill still runs; it asks instead.