Free tools / Rewrite copy
Rewrite copy
Produce 2–3 on-brand copy variants per section without breaking message match.
- Category
- Package skills
- Format
- SKILL.md
- Compatible with
- Claude Code · Cursor · any agent that loads SKILL.md
- License
- Open for learning and client work · Non-commercial productization ban
- Built by
- Frezpo
Why use it
You need alternatives for A/B or client review, not a second strategy pass.
What it does
Loads 01_content.md and build_context content segments, keeps CTA intent and locked facts, emits section-mapped variants.
What you get
- Universal skill (same text in every Frezpo package)
- Locked vs editable table so agents do not invent proof
- Offline package-file procedure
Why Frezpo makes it better
Variants still match the winning ad
The package already pairs hooks with hero promise. Rewrite-copy stays inside that envelope; Frezpo created the envelope.
How to use
- Read the markdown below, or download / copy it.
- Install into Claude Code (see install guide) or open the SKILL.md in your agent.
- For package skills, unzip a Frezpo Build package first — sample pack works offline.
The skill (SKILL.md)
Raw markdown source — copy or download to use offline.
markdown · SKILL.md
---
name: rewrite-copy
description: Produce on-brand landing copy variants from a Frezpo package without re-running the pipeline.
license: PolyForm-Noncommercial-1.0.0
---
> Frezpo free tool — open for learning and paid client work. May not be sold or productized as a competing skill pack. Built by Frezpo (https://frezpo.com).
# Skill: rewrite-copy
**Package-native skill** — run in the user's local LLM or coding agent.
**Do not re-run the ads-landing pipeline.**
## When to use
Produce 2–3 on-brand alternative copy variants for landing sections while preserving
message-match with ad hooks.
## Inputs (read first)
1. `01_content.md` — copy, hooks, message-match pairings (edit surface).
2. `machine/build_context.json` — structured sections + `content` (hook_seed, pairings).
3. Optional user notes: angles to emphasize, length limits, tone tweaks.
## Procedure
1. Load project, language, audience, core promise, and dominant angle from handoffs.
2. Map variants **per section** in content / `content.segments`.
3. Keep CTA **intent** unchanged (same job for the button; wording may vary slightly).
4. Stay in the package language from `build_context.language` / content pack.
5. Do not invent testimonials, stats, guarantees, or claims absent from package fields.
6. Respect disqualifiers and dominant angle from hook seed / content pack.
## Locked vs editable
| Locked | Editable |
|--------|----------|
| Message-match intent (winning ad ↔ hero) | Alternate phrasings per section |
| Facts / proof not in package | Length, rhythm, CTA label microcopy (same intent) |
| Pipeline re-run | Which angle variant to emphasize (if arsenal allows) |
## Output
- Variants mapped per section, each noting which hook angle it supports.
- Primary CTA language remains scannable above the fold.
## Notes
- Soft-fill (`Not produced in this run.`) is not invent-license.
- Prefer editing `01_content.md` or a side doc; only patch `build_context` if the user
wants structured fields updated too.
Other tools
Need the full campaign story (hooks + landing structure together)?