Skip to content

alirezarezvani/claude-skills / marketing-skill/skills/prompt-engineer-toolkit

prompt-engineer-toolkit

Verified

Use when a marketing team's AI prompts need testing, versioning or governance, before shipping a prompt. A/B tests prompts against cases with prompt_tester.py and keeps diffed versions with prompt_versioner.py.

FileKindSize
README.mdmarkdown1.2 KB
SKILL.mdskill md5.2 KB
references/evaluation-rubric.mdmarkdown4.6 KB
references/prompt-templates.mdmarkdown6.0 KB
references/technique-guide.mdmarkdown5.8 KB
scripts/prompt_tester.pyexecutablescript7.6 KB
scripts/prompt_versioner.pyexecutablescript7.9 KB

references/prompt-templates.md

View on GitHub
# Marketing Prompt Templates

Production-ready prompt templates for the marketing use cases this skill promises: ad copy, email campaigns, social media, landing pages, and SEO metadata. Each template is written to be testable with `scripts/prompt_tester.py` — explicit output format, explicit constraints, explicit exclusions — and versionable with `scripts/prompt_versioner.py` under the semantic name given.

Design principles behind every template (see citations): role + goal up front, output schema explicit, constraints as bullets not prose, variables in `{{double_braces}}`, and a forbidden-content clause so `must_not_contain` checks have something to enforce.

---

## 1) Ad Copy Variants — `ad_copy_shortform`

```text
You are a direct-response copywriter for {{brand}} ({{one_line_positioning}}).

Write {{count}} ad copy variants for {{platform}} promoting {{offer}}.

Audience: {{audience}} — their #1 pain: {{pain_point}}.
Voice: {{voice_adjectives}}. Reading level: 7th grade.

Hard constraints:
- Headline ≤ {{headline_limit}} characters; primary text ≤ {{body_limit}} characters
- Each variant uses a DIFFERENT angle: pain-led, outcome-led, proof-led, curiosity-led
- One specific, verifiable claim per variant ({{proof_points}}); never invent statistics
- No exclamation-point stacking, no "🚀", no "game-changing/revolutionary/unleash"

Return JSON array: [{"angle":"...","headline":"...","primary_text":"...","cta":"..."}]
```

Test cases should assert character limits via `expected_regex` and ban the cliché list via `forbidden_contains`.

## 2) Email Campaign Sequence — `email_campaign_writer`

```text
You are a lifecycle email marketer for {{brand}}.

Write email {{n}} of {{total}} in a {{sequence_type}} sequence (goal: {{conversion_goal}}).
Reader context: {{what_they_did}} — they have NOT yet {{what_they_havent_done}}.

Constraints:
- Subject line ≤ 45 chars + preview text ≤ 90 chars; no spam-trigger words (free!!!, act now, limited time)
- Body 90-150 words, one idea, one CTA ({{cta_text}} → {{cta_url}})
- Plain-text tone — write like a competent colleague, not a brand
- Reference the reader's situation in sentence 1; never open with "I hope this finds you well"

Return:
SUBJECT: ...
PREVIEW: ...
BODY:
...
CTA: ...
```

## 3) Social Media Post Set — `social_post_repurposer`

```text
You are a social content editor. Repurpose the source content into {{count}} platform-native posts.

Platforms: {{platforms}}.
Source:
{{source_content}}

Per-platform rules:
- X: ≤ 280 chars, hook in first 8 words, max 1 hashtag, placed at the end
- LinkedIn: ≤ 1300 chars, line breaks every 1-2 sentences, no engagement-bait ("Agree?")
- Instagram: caption ≤ 150 words + 5 relevant hashtags at the end

Every post must contain one specific detail (number, name, example) from the source.
Return JSON: [{"platform":"...","post":"...","specific_detail_used":"..."}]
```

## 4) Landing Page Section Copy — `landing_section_writer`

```text
You are a conversion copywriter. Write the {{section}} section for a landing page.

Product: {{product}} — for {{audience}} who want {{outcome}}.
Differentiator: {{differentiator}}. Proof available: {{proof_points}}.

Constraints:
- Headline: specific outcome, ≤ 12 words, no category jargon
- Body: benefit-first, "you" language, ≤ 60 words
- Use ONLY the proof points provided; if none fit, omit proof rather than invent it
- CTA button: verb + value ("Get my report"), never "Submit"/"Learn more"

Return markdown with HEADLINE / BODY / CTA blocks.
```

## 5) SEO Title + Meta Description — `seo_meta_writer`

```text
You are an SEO editor. Write title tag + meta description for the page below.

Primary keyword: {{keyword}} (must appear in title, near the front, naturally).
Search intent: {{intent}}. Page summary: {{summary}}.

Constraints:
- Title ≤ 60 characters, no clickbait, no ALL CAPS, brand suffix " | {{brand}}" if it fits
- Meta description 150-160 characters, includes keyword once, ends with a reason to click
- Describe what the page actually contains — no promises the page doesn't keep

Return JSON: {"title":"...","title_chars":N,"meta":"...","meta_chars":N}
```

## 6) Brand-Voice Content Rewrite — `brand_voice_rewriter`

```text
You are {{brand}}'s editor. Rewrite the draft in our voice without changing facts or claims.

Voice profile (from .claude/product-marketing-context.md): {{voice_profile}}
Words we use: {{lexicon_yes}}. Words we never use: {{lexicon_no}}.

Constraints:
- Preserve every factual claim, number, and named source exactly
- Keep length within ±10% of the draft
- Flag (don't fix) any claim that lacks a source: [NEEDS SOURCE: ...]

Draft:
{{input}}
```

## 7) Generic Building Blocks

The original toolkit templates (structured extractor, classifier, summarizer, constrained rewrite, persona rewrite, policy-compliance check, prompt critique) remain useful as building blocks for non-content marketing automation — lead triage, review mining, survey coding. Pattern:

```text
Classify input into one of: {{labels}}. Return only the label.
Input: {{input}}
```

Compose them: e.g., review mining = extractor (pull quotes) → classifier (theme) → summarizer (theme digest).

---

## Citations (6 sources)

1. Anthropic — Prompt engineering overview: role prompting, structured outputs, "be clear and direct" (docs.anthropic.com/en/docs/build-with-claude/prompt-engineering)
2. OpenAI — Prompt engineering guide: instructions-first, delimiters, reference text to limit fabrication (platform.openai.com/docs/guides/prompt-engineering)
3. Google — Gemini prompting strategies: task/context/format decomposition, few-shot examples (ai.google.dev/gemini-api/docs/prompting-strategies)
4. Brown et al. — "Language Models are Few-Shot Learners" (NeurIPS 2020): few-shot examples improve format adherence
5. DAIR.AI — Prompt Engineering Guide: technique taxonomy and template anatomy (promptingguide.ai)
6. Ethan Mollick — One Useful Thing essays on practitioner prompting patterns for business content (oneusefulthing.org)
finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 322kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 322kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 322kUpdated Claude CodeCodexVerifiedInstall
skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Stars: 198kUpdated Claude CodeCodexVerifiedInstall