skills/copy-editing/SKILL.md
Use when editing, reviewing, or improving existing marketing or conversion copy. Also use when the user mentions copy feedback, proofreading, polish, or copy sweep. NEVER use for writing new copy from scratch (use copywriting skill), structural page optimization (use page-cro), or non-marketing content editing.
npx skillsauth add sharkitect-solutions/sharkitect-claude-toolkit copy-editingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
| File | Purpose | When to Load | |---|---|---| | SKILL.md | Seven Sweeps framework, edit depth calibration, sweep conflict resolution, quick-pass editing reference, copy editing checklist | Always (auto-loaded) | | industry-tone-calibration.md | Industry-specific editing rules (SaaS, e-commerce, financial, healthcare, agency), cross-industry traps, tone spectrum reference | When editing copy for a specific industry or when regulatory language constraints apply | | performance-driven-editing.md | Metric-to-sweep mapping, common edits that decrease conversion, heatmap-informed editing, A/B test integration, copy scoring | When performance data is available or when edits target measurable conversion improvement | | multi-format-editing.md | Format-specific sweep modifications (landing pages, emails, ads, product descriptions, social), cross-format consistency, character limits | When editing across multiple formats or adapting copy for a specific channel |
| This Skill Handles | Defer To | |---|---| | Editing and improving existing marketing/conversion copy | copywriting (writing new copy from scratch) | | Sequential sweep-based copy review methodology | page-cro (structural page layout optimization) | | Voice and tone consistency across copy | frontend-design (visual design conventions) | | Industry-specific copy editing constraints | content-research-writer (research-backed long-form content) | | Format-specific editing for emails, ads, landing pages | email-composer (writing email copy and tone) | | Performance-driven editing from A/B test data | marketing-psychology (psychological frameworks for campaigns) |
You are an expert copy editor specializing in marketing and conversion copy. Systematically improve existing copy through focused sequential passes while preserving the core message and author's voice.
Edit through seven sequential passes, each focusing on one dimension. After each sweep, loop back to verify previous sweeps are uncompromised -- this back-check loop is mandatory.
Focus: Can the reader understand what you're saying on first read?
After this sweep: Confirm Rule of One (one main idea per section) and You Rule (speaks directly to reader) are intact.
Focus: Is the copy consistent in how it sounds throughout?
After this sweep: Return to Sweep 1 (Clarity) -- voice edits often introduce ambiguity.
Focus: Does every claim answer "why should I care?"
For every statement, ask "Okay, so what?" If the copy doesn't answer with a deeper benefit, add the bridge.
After this sweep: Return to Sweeps 2, 1.
Focus: Is every claim supported with evidence?
After this sweep: Return to Sweeps 3, 2, 1.
Focus: Is the copy concrete enough to be compelling?
| Vague | Specific | |-------|----------| | Save time | Save 4 hours every week | | Many customers | 2,847 teams | | Fast results | Results in 14 days | | Great support | Response within 2 hours |
Highlight vague words ("improve," "enhance," "optimize"). Add numbers, timeframes, or examples. Remove content that cannot be made specific -- it is filler.
After this sweep: Return to Sweeps 4, 3, 2, 1.
Focus: Does the copy make the reader feel something?
After this sweep: Return to Sweeps 5, 4, 3, 2, 1.
Focus: Have we removed every barrier to action?
After this sweep: Final pass through all previous sweeps: 6, 5, 4, 3, 2, 1.
Not every piece needs all seven sweeps. Calibrate based on copy maturity and stakes.
| Situation | Recommended Depth | Focus Sweeps | |-----------|-------------------|--------------| | Quick polish on finished copy | 1-2 sweeps | 1 (Clarity), 2 (Voice) | | Pre-launch review of near-final copy | 3-4 sweeps | 1, 3 (So What), 4 (Prove It), 7 (Zero Risk) | | Major revision of underperforming copy | All 7 sweeps | Full sequence with back-checks | | First draft just written | 4-5 sweeps | Skip Sweep 2 initially -- voice inconsistency is expected in drafts |
When improving one sweep dimension degrades another, use this resolution order:
| Conflict | Resolution | |----------|------------| | Adding specificity (S5) weakens emotional resonance (S6) | Keep specificity -- emotion built on vague claims is fragile. Add emotional framing around the specific detail instead. | | Adding proof (S4) breaks voice consistency (S2) | Integrate proof using the established voice; rewrite the testimonial lead-in, not the testimonial. | | Heightened emotion (S6) creates unsupported claims (S4) | Anchor emotion to a real outcome -- if no proof exists, soften the claim rather than exaggerate. | | Zero Risk additions (S7) make copy feel defensive | Move risk reversals to natural trust-building moments (near social proof) rather than clustering at CTA. | | So What bridges (S3) make sentences too long (S1) | Break into two sentences: claim, then benefit. Never bury the benefit in a subordinate clause. |
Patterns where well-intentioned edits made copy perform worse.
| Failure Name | What Happened | Quantified Impact | Prevention | |---|---|---|---| | The Clarity Overcorrection | Editor simplified technical SaaS copy to be "more readable." Lost audience-specific terms that signaled expertise. | 23% drop in demo requests (reduced perceived credibility with technical buyers) | Calibrate jargon level to the LEAST technical person on the buying committee, not the general public | | The Proof Purge | Editor removed "lengthy" testimonials and case study references to "tighten" the page. Left claims unsupported. | 35% conversion drop; rebounded after restoring proof sections (Unbounce case study) | Never remove proof to save space. Compress it -- shorter testimonial, not absent testimonial. | | The Voice Homogenizer | Editor standardized tone across an email sequence written with intentional tone variation (casual welcome -> professional onboarding -> urgent deadline). | 18% lower click-through on deadline email (urgency was edited out for "consistency") | Check if tone variation is intentional before standardizing. Email sequences often use deliberate escalation. | | The Benefit Stuffing | Editor added benefit bridges to every feature, making copy 2.5x longer. Every sentence tried to answer "so what?" | Scroll depth dropped from 65% to 31%; conversion down 12% (too much to read, decision fatigue) | Apply So What (S3) to key claims, not every single statement. Some supporting details can be features-only. | | The Risk Reversal Cluster | Editor added money-back guarantee, free trial, cancel anytime, and no credit card required all around the CTA. | CTA area felt desperate; conversion dropped 8% vs single strong guarantee (VWO test) | One strong risk reversal near CTA. Additional trust signals distributed throughout the page. |
| Category | Remove / Replace | |----------|-----------------| | Weak intensifiers | very, really, extremely, incredibly | | Filler words | just, actually, basically, that (often) | | Verbose phrases | "in order to" -> "to"; "make a decision" -> "decide" | | Corporate synonyms | utilize->use, leverage->use, facilitate->help, seamless->smooth, robust->strong | | Structural | passive voice -> active; adverbs -> stronger verbs; max 25 words/sentence |
If you need more context before starting:
| Decision | Rationale | |----------|-----------| | Seven sequential sweeps with back-checks | Each pass has one focus; back-checks catch regressions introduced by previous edits -- expert methodology not replicated by a single review pass | | Back-check loops mandatory after each sweep | Edits in one dimension routinely break adjacent dimensions; the loop is what makes the framework reliable | | Edit Depth Calibration by stakes | Full seven sweeps on a quick social post is waste; calibrating prevents over-editing and under-editing | | Sweep Conflict Resolution table | Conflicting directives (add proof vs. maintain voice) have a deterministic resolution order -- removes guesswork | | Remove "Common Copy Problems & Fixes" | Claude already knows wall-of-features, corporate speak, and buried CTAs are problems -- listing them adds lines without adding capability | | Preserve Specificity upgrade table | Concrete before/after examples for vague->specific upgrades are the most commonly needed in-context reference |
development
When the user wants help with paid advertising campaigns on Google Ads, Meta (Facebook/Instagram), LinkedIn, Twitter/X, or other ad platforms. Also use when the user mentions 'PPC,' 'paid media,' 'ad copy,' 'ad creative,' 'ROAS,' 'CPA,' 'ad campaign,' 'retargeting,' or 'audience targeting.' This skill covers campaign strategy, ad creation, audience targeting, and optimization.
testing
--- name: using-sharkitect-methodology description: Use when starting any conversation in a Sharkitect workspace OR before any task involving NEW pricing, positioning, proposal, strategy, plan-execution, or schema-design work — mandates invocation of Sharkitect-specific methodology skills (pricing-strategy, marketing-strategy-pmm, smb-cfo, hq-revenue-ops, executing-plans, brainstorming) under the same anti-rationalization discipline as using-superpowers. Documentation has failed 4 times across H
testing
Use when user says 'end session', 'wrap up', 'stop for the day', 'done for today', 'close out', 'save session', 'wrapping up', or invokes /end-session. Runs the full 9-step end-of-session protocol: resource audit, MEMORY.md update, lessons capture, plan status, pending items, workspace checklist, .tmp/ audit, git commit+push, Supabase brain sync, session brief, summary. Final step schedules a detached self-kill of the current session ONLY (3s delay) so the window closes cleanly. Other claude.exe processes (active workspaces) are NOT touched -- orphan cleanup is handled separately by Claude-Orphan-Cleanup-Hourly with proper age safeguards. Do NOT use for: mid-session quick saves (use session-checkpoint), skill syncing (use sync-skills.py), brain memory queries (use supabase-sync.py pull), document freshness reviews (use document-lifecycle), resource gap detection (use resource-auditor).
testing
Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's comprehensive "Signs of AI writing" guide. Detects and fixes patterns including: inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, passive voice, negative parallelisms, and filler phrases.