From ciromaciel-marketing
Generate marketing copy (cold email sequences, LinkedIn/X posts, landing page sections, ad variations) using a client's brand voice profile and ICP. Produces multiple variations per asset (not one), with variables marked for client-specific substitution. Pure reasoning skill. Pair with `copy-critic` agent for review.
How this skill is triggered — by the user, by Claude, or both
Slash command
/ciromaciel-marketing:copy-generatorThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Generates marketing copy across canonical formats. Designed to be invoked one asset-type at a time (emails, then social, then landing, etc.) — not all at once.
Generates marketing copy across canonical formats. Designed to be invoked one asset-type at a time (emails, then social, then landing, etc.) — not all at once.
Built for: Founders without copywriting background, or marketers needing first drafts that match brand voice. Output should be specific to the client, never generic.
/new-campaign has produced a brief| Asset | Use this agent instead |
|---|---|
| Blog post / article / longform | blog-writer |
| LinkedIn organic post / carousel | linkedin-writer |
| Instagram feed / Reel / Story / carousel | instagram-writer |
| Video script (Reel, Shorts, TikTok, YouTube, LinkedIn video) | video-script-writer |
This skill stays for canonical short-form direct-response copy. Channel-native organic content goes to the channel specialists — they know the physics of each platform.
| Input | Path |
|---|---|
| Campaign brief | clients/<name>/campaigns/<campaign>.md |
| Brand voice profile | clients/<name>/research/brand-voice.md |
| ICP profile | clients/<name>/research/icp-*.md |
If brand voice is missing, halt. Generating copy without brand voice = generic copy = wasted output.
For each email in the sequence, structure:
## Email N — [purpose]
**Subject line variations (3):**
1. [...]
2. [...]
3. [...]
**Preheader (1-line):** [...]
**Body:**
[copy — max 80 words for outbound]
**CTA:** [single, specific — not "let me know if interested"]
**Variables to fill:**
- {{firstName}}
- {{companyName}}
- {{triggerEvent}}
Sequence structure (SaaS or service):
For each post:
## Post N — [angle]
**Format:** [insight / case study / hot take / how-to / behind-the-scenes]
**Hook (first 2 lines — must stop the scroll):**
[...]
**Body:**
[...]
**CTA:**
[single — comment prompt OR link OR DM ask]
**Variations:** Generate 2 alternative hooks for the same body.
Hook patterns that work:
Avoid:
Generate section by section:
## Hero
**Headline (3 variations):**
1. [...]
2. [...]
3. [...]
**Subhead (1):**
[1 sentence — clarifies WHO it's for + WHAT outcome]
**Primary CTA:** [...]
**Secondary CTA (optional):** [...]
Then optionally:
Generate 4-6 variations. Each:
## Ad N — [angle]
**Headline (max chars per platform):**
[...]
**Body:**
[...]
**Image direction:** [what should the image convey — not the image itself]
**CTA button:** [exact button copy]
**Targeting hint:** [if obvious — title / industry / interest]
Variation diversity rule: the 4-6 ads should differ in angle, not just wording. Specifically:
Before writing, extract from brand-voice.md:
Write a 1-line voice anchor at the top of your output:
Voice anchor: <3 adjectives> | Sentences: | Avoid: | Use:
Save to clients/<name>/campaigns/<campaign>-assets/<asset-type>/:
campaigns/<campaign>-assets/
├── emails/
│ ├── 01-cold-open.md
│ ├── 02-proof.md
│ └── 03-breakup.md
├── social/
│ ├── linkedin-01.md
│ └── linkedin-02.md
├── landing/
│ └── landing.md
└── ads/
├── linkedin-01.md
└── linkedin-02.md
Each file is pure Markdown — copy/paste-ready for the destination tool.
npx claudepluginhub ciro-maciel/ciromacielos --plugin ciromaciel-marketingProvides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.