More screenshots
Works with the AI Agents you already use
Claude Code
Cursor
Codex CLI
DeepSeek
Muse+22 moreClaude CodeCursorCodex CLIDeepSeekMuse
Dots
Manus
Grok
Grok Bot+18 agentsRewrite Me — Copy Rewrite Against Your BRIEF.md
Mockups get built fast, with rough or placeholder copy, before business requirements are fully pinned down.
$9
Rewrite Me — Copy Rewrite Against Your BRIEF.md
Example session with this skill installed
Demo project
LOOP THREAD, a scoped-down three-view Astro e-commerce demo for a Japan-based sustainable apparel brand (T-shirts, sweatshirts, outerwear — organic cotton and recycled polyester only, full supply-chain traceability per item). BRIEF.md already existed in the project root before this run:
Site Type: E-commerce demo site — a scoped-down, three-view build (home/top, product listing, product detail); no cart or checkout flow.
Target Audience: Ethically-conscious consumers (B2C) who prioritize sustainable sourcing over trend-driven fashion.
Persona Detail: Roughly age 30, environmentally aware, willing to pay a premium (¥6,000–¥28,000) for transparent, responsibly made basics. Values traceability and material integrity over fast-fashion novelty.
Product / Value Proposition: Basics-only apparel line made exclusively from organic cotton and recycled polyester. Core differentiator: full supply-chain traceability disclosed on every product page — origin, process, CO2 emissions.
Competitive Differentiation: Transparency — per-item traceability data surfaced directly in the product detail view. The brand's main point of distinction.
Notes: Clean and minimal aesthetic — let the product photography and supply-chain data do the talking. Avoid visual noise.
The target file was src/pages/index.astro — its existing copy already gestured at "traceability," but in generic, interchangeable phrasing that could describe almost any eco-conscious apparel brand, not one built specifically around a differentiation of per-item, NFC-scannable proof.
The skill's AskUserQuestion call asked granularity and volume in one pass:
- Rewrite granularity → Full rewrite (not anchored to the existing wording's tone)
- Text volume → Keep as-is (same amount of text, sharper content)
Site Type is a multi-page e-commerce demo, not a single-page conversion pitch, so the LP-only persuasion-framing question (behavioral-economics round) was correctly skipped — it never appeared.
- Read your context and instructions
- Compiled the rewrite me
The skill rewrote six copy elements in src/pages/index.astro, leaving every class name, component boundary, and data value (prices, materials, emissions figures) untouched:
| Element | Before | After |
|---|---|---|
Page <title> / meta description | "LOOP THREAD — Traceable Everyday Basics" / generic supply-chain-transparency description | "LOOP THREAD — Every Fiber, Fully Traceable" / names the specific disclosure (origin, process, carbon footprint) per piece |
Hero eyebrow + aria-label | "Traceable Everyday Basics" | "Every Fiber, Fully Traceable" |
| Hero H1 | "Honest thread from seed to garment" | "Basics you can trace back to the farm" — concrete verb ("trace back"), not an abstract adjective ("honest") |
| Hero body copy | "100% visible coordinates of our entire farm-to-spinning supply chain" | "Every piece ships with its own origin, process, and CO2 data" — restates the differentiation as a per-item property, matching BRIEF.md's Competitive Differentiation section exactly |
| Hero CTAs | "Explore the Collection" / "Trace supply chain" | "Shop the Basics" / "See the supply chain" — plainer, more direct action verbs |
| Categories heading | "Sourced responsibly, built endlessly" | "Three categories, one sourcing standard" — ties directly to the three product categories shown below it |
| Featured-products heading | "Traceable to the origin farm" | "Each piece, traced to its origin farm" — "each piece" reinforces the per-item claim |
| Transparency section H2 + body + CTA | "Every stage of production is fully visible to you" / "By scanning the NFC chip... No hidden steps. No vague claims." / "Read Our Transparency Code" | "Nothing about this garment is hidden from you" / restates the NFC-chip claim as "the standard we hold ourselves to on every single piece" / "Read Our Transparency Standard" |
Every rewritten sentence traces back to an existing BRIEF.md claim — no new numbers, no new certifications, no fabricated testimonials were introduced; the emissions table and price/material data (real content elsewhere on the page) were left completely untouched.
Summary
| Step | Result |
|---|---|
| Step 1 (target file) | src/pages/index.astro, resolved directly from the user's page name |
| Step 2 (BRIEF.md) | Already existed — read directly, no requirements interview needed |
| Step 3 (granularity/volume) | 1 question call, 2 questions — Full rewrite / Keep as-is; LP-only persuasion question correctly skipped for a multi-page e-commerce Site Type |
| Step 4 (rewrite) | 6 copy locations edited via targeted edits (not a full-file rewrite) — title/meta, hero eyebrow+H1+body+CTAs+aria-label, categories heading, featured heading, transparency H2+body+CTA |
| Step 5 (report) | Scoped git diff, before/after table above, no layout-strain flags (volume was kept constant) |
The rewrite turned a generic "we're sustainable and transparent" pitch into copy that repeatedly reinforces the one differentiation claim the brief says should be the centerpiece — a real, per-piece, NFC-verifiable data trail — without touching a single class, prop, or structural element in the file.
Connects securely to your tools. The creator never sees your data.
About this skill
Mockups get built fast, with rough or placeholder copy, before business requirements are fully pinned down. Once you have a BRIEF.md (or one gets created for you), this skill goes back into already-implemented page code and rewrites the visible text — headings, body copy, CTA labels, alt text — to actually match it. It never touches markup structure, CSS classes, or component boundaries; only text content changes.
What it does
- Reads your BRIEF.md and rewrites the visible copy in the page files you point it at
- Lets you choose the rewrite granularity — a full rewrite from scratch, or a light touch-up that preserves as much existing phrasing as possible
- Lets you dial text volume up (more detail, examples, explanation) or down (cut to the essential point) as a separate, independent choice
- For landing pages specifically, can apply behavioral-economics persuasion framing — social proof, authority, loss aversion, anchoring, default effect — as an optional lens over your real content
- Reports every change with a scoped diff, tied back to the specific BRIEF.md section that drove it
How it works
- Identifies the target file(s) from what you name, or asks if nothing matches
- Resolves BRIEF.md — reads it if present; if missing, uses a requirements-interview skill if one is installed, or falls back to a short guided Q&A to build a minimal one
- Asks granularity and volume in one question, plus a persuasion-framing question only when the brief describes a conversion-oriented landing page
- Rewrites each visible text node — never class names, props, or structural markup — and applies changes with targeted edits so the diff stays reviewable
- Reports what changed and why, file by file
No fabrication, ever
The persuasion-framing option reframes real content — it never invents user counts, deadlines, testimonials, or "in high demand" claims that don't already exist in BRIEF.md or the page. A vague claim stays vague; it never gets sharpened into a specific number or track-record-sounding language the source doesn't support. If a selected principle would need data that isn't there, the skill skips that instance and reports the gap instead of guessing.
Requirements
A Claude Code agent and an existing BRIEF.md (or a requirements-interview skill installed alongside this one, or a few minutes to answer a short fallback Q&A). No network calls, no external MCP server. Edits only the page files you point it at.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Prompt & Skill Engineering.
Only rewrites text content — headings, body copy, CTA labels, alt text. Never touches layout, CSS classes, or component structure; a volume increase that overflows a fixed-height container is flagged in the report, not fixed automatically. The behavioral-economics persuasion option only applies to single-goal landing pages, and only reframes data that already exists in BRIEF.md or the page — it will not add social proof, urgency, or authority claims that aren't already backed by real content.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 1 month ago
Permissions
This skill edits only the page file(s) you point it at (and, only as a fallback when no BRIEF.md and no requirements-interview skill exist, writes a minimal BRIEF.md to the project root). It reads the target page file(s) and BRIEF.md, and runs git diff scoped to the edited files for its final report. No network calls, no other project files touched.