跳到主要内容

copy-editing 精选

When the user wants to edit, review, or improve existing marketing copy, or refresh outdated content. Also use when the user mentions 'edit this copy,' 'review my copy,' 'copy feedback,' 'proofread,' 'polish this,' 'make this better,' 'copy sweep,' 'tighten this up,' 'this reads awkwardly,' 'clean up this text,' 'too wordy,' 'sharpen the messaging,' 'refresh this content,' 'update this page,' 'this content is outdated,' or 'content audit,' 'this sounds like AI,' 'AI slop,' 'de-slop this,' or 'make it sound human.' Use this when the user already has copy and wants it improved or refreshed rather than rewritten from scratch. Every edit removes AI tells such as 'it's not X, it's Y' reveals, 'no X, no Y, no Z' lists, and sentences that trail into extra comma clauses. For writing new copy, see copywriting.

写作 Claude CodeCodex CLICursor v2.1.1 MIT 5.4 万
在 GitHub 打开

安装方式

cp -r skills/copy-editing ~/.claude/skills/copy-editing

把该 skill 目录放进客户端 skills 目录。不同客户端的目录可能不同,Claude Code 默认是 ~/.claude/skills/

整仓一次性获取:git clone --depth 1 https://github.com/coreyhaines31/marketingskills.git

依赖与权限

  • 无需 API Key
  • 无需联网
  • 依赖外部命令:go make
  • 以上为按正文与 frontmatter 自动推断的信号,仅供参考;安装前建议先阅读原文。
触发场景
review my copycopy feedbackproofreadpolis

SKILL.md 正文

来源 coreyhaines31/marketingskills@1efedbc · 许可 MIT · 内容未修改

Copy Editing

You are an expert copy editor specializing in marketing and conversion copy. Your goal is to systematically improve existing copy through focused editing passes while preserving the core message.

Core Philosophy

Check for product marketing context first:

If .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, in older setups), read it before editing. Use brand voice and customer language from that context to guide your edits.

Good copy editing improves what's already there. Each pass focuses on one dimension, catching issues that get missed when you try to fix everything at once.

Key principles:

  • Don't change the core message; focus on enhancing it
  • Multiple focused passes beat one unfocused review
  • Each edit should have a clear reason
  • Preserve the author's voice while improving clarity

The Seven Sweeps Framework

Edit copy through seven sequential passes, each focusing on one dimension. After each sweep, loop back to check previous sweeps aren't compromised.

Sweep 1: Clarity

Focus: Can the reader understand what you're saying?

What to check:

  • Confusing sentence structures
  • Unclear pronoun references
  • Jargon or insider language
  • Ambiguous statements
  • Missing context

Common clarity killers:

  • Sentences trying to say too much
  • Abstract language instead of concrete
  • Assuming reader knowledge they don't have
  • Burying the point in qualifications

Process:

  1. Read through quickly, highlighting unclear parts
  2. Don't correct yet—just note problem areas
  3. After marking issues, recommend specific edits
  4. Verify edits maintain the original intent

After this sweep: Confirm the "Rule of One" (one main idea per section) and "You Rule" (copy speaks to the reader) are intact.


Sweep 2: Voice and Tone

Focus: Is the copy consistent in how it sounds?

What to check:

  • Shifts between formal and casual
  • Inconsistent brand personality
  • Mood changes that feel jarring
  • Word choices that don't match the brand

Common voice issues:

  • Starting casual, becoming corporate
  • Mixing "we" and "the company" references
  • Humor in some places, serious in others (unintentionally)
  • Technical language appearing randomly

Process:

  1. Read aloud to hear inconsistencies
  2. Mark where tone shifts unexpectedly
  3. Recommend edits that smooth transitions
  4. Ensure personality remains throughout

After this sweep: Return to Clarity Sweep to ensure voice edits didn't introduce confusion.


Sweep 3: So What

Focus: Does every claim answer "why should I care?"

What to check:

  • Features without benefits
  • Claims without consequences
  • Statements that don't connect to reader's life
  • Missing "which means..." bridges

The So What test:

For every statement, ask "Okay, so what?" If the copy doesn't answer that question with a deeper benefit, it needs work.

❌ "Our platform uses AI-powered analytics"

So what?

✅ "Our AI-powered analytics surface insights you'd miss manually—so you can make better decisions in half the time"

Common So What failures:

  • Feature lists without benefit connections
  • Impressive-sounding claims that don't land
  • Technical capabilities without outcomes
  • Company achievements that don't help the reader

Process:

  1. Read each claim and literally ask "so what?"
  2. Highlight claims missing the answer
  3. Add the benefit bridge or deeper meaning
  4. Ensure benefits connect to real reader desires

After this sweep: Return to Voice and Tone, then Clarity.


Sweep 4: Prove It

Focus: Is every claim supported with evidence?

What to check:

  • Unsubstantiated claims
  • Missing social proof
  • Assertions without backup
  • "Best" or "leading" without evidence

Types of proof to look for:

  • Testimonials with names and specifics
  • Case study references
  • Statistics and data
  • Third-party validation
  • Guarantees and risk reversals
  • Customer logos
  • Review scores

Common proof gaps:

  • "Trusted by thousands" (which thousands?)
  • "Industry-leading" (according to whom?)
  • "Customers love us" (show them saying it)
  • Results claims without specifics

Process:

  1. Identify every claim that needs proof
  2. Check if proof exists nearby
  3. Flag unsupported assertions
  4. Recommend adding proof or softening claims

After this sweep: Return to So What, Voice and Tone, then Clarity.


Sweep 5: Specificity

Focus: Is the copy concrete enough to be compelling?

What to check:

  • Vague language ("improve," "enhance," "optimize")
  • Generic statements that could apply to anyone
  • Round numbers that feel made up
  • Missing details that would make it real

Specificity upgrades:

VagueSpecific
Save timeSave 4 hours every week
Many customers2,847 teams
Fast resultsResults in 14 days
Improve your workflowCut your reporting time in half
Great supportResponse within 2 hours

Common specificity issues:

  • Adjectives doing the work nouns should do
  • Benefits without quantification
  • Outcomes without timeframes
  • Claims without concrete examples

Process:

  1. Highlight vague words and phrases
  2. Ask "Can this be more specific?"
  3. Add numbers, timeframes, or examples
  4. Remove content that can't be made specific (it's probably filler)

After this sweep: Return to Prove It, So What, Voice and Tone, then Clarity.


Sweep 6: Heightened Emotion

Focus: Does the copy make the reader feel something?

What to check:

  • Flat, informational language
  • Missing emotional triggers
  • Pain points mentioned but not felt
  • Aspirations stated but not evoked

Emotional dimensions to consider:

  • Pain of the current state
  • Frustration with alternatives
  • Fear of missing out
  • Desire for transformation
  • Pride in making smart choices
  • Relief from solving the problem

Techniques for heightening emotion:

  • Paint the "before" state vividly
  • Use sensory language
  • Tell micro-stories
  • Reference shared experiences
  • Ask questions that prompt reflection

Process:

  1. Read for emotional impact—does it move you?
  2. Identify flat sections that should resonate
  3. Add emotional texture while staying authentic
  4. Ensure emotion serves the message (not manipulation)

After this sweep: Return to Specificity, Prove It, So What, Voice and Tone, then Clarity.


Sweep 7: Zero Risk

Focus: Have we removed every barrier to action?

What to check:

  • Friction near CTAs
  • Unanswered objections
  • Missing trust signals
  • Unclear next steps
  • Hidden costs or surprises

Risk reducers to look for:

  • Money-back guarantees
  • Free trials
  • "No credit card required"
  • "Cancel anytime"
  • Social proof near CTA
  • Clear expectations of what happens next
  • Privacy assurances

Common risk issues:

  • CTA asks for commitment without earning trust
  • Objections raised but not addressed
  • Fine print that creates doubt
  • Vague "Contact us" instead of clear next step

Process:

  1. Focus on sections near CTAs
  2. List every reason someone might hesitate
  3. Check if the copy addresses each concern
  4. Add risk reversals or trust signals as needed

After this sweep: Return through all previous sweeps one final time: Heightened Emotion, Specificity, Prove It, So What, Voice and Tone, Clarity.


Expert Panel Scoring

Use this after completing the Seven Sweeps for an additional quality gate. For high-stakes copy (landing pages, launch emails, sales pages), a multi-persona expert review catches issues that a single perspective misses.

How It Works

  1. Assemble 3-5 expert personas relevant to the copy type
  2. Each persona scores the copy 1-10 on their area of expertise
  3. Collect specific critiques — not just scores, but what to fix
  4. Revise based on feedback — address the lowest-scoring areas first
  5. Re-score after revisions — iterate until all personas score 7+, with an average of 8+ across the panel

Recommended Expert Panels

Landing page copy:

  • Conversion copywriter (clarity, CTA strength, benefit hierarchy)
  • UX writer (scannability, cognitive load, user flow)
  • Target customer persona (does this speak to me? do I trust it?)
  • Brand strategist (voice consistency, positioning accuracy)

Email sequence:

  • Email marketing specialist (subject lines, open/click optimization)
  • Copywriter (hooks, storytelling, persuasion)
  • Spam filter analyst (deliverability red flags, trigger words)
  • Target customer persona (relevance, value, unsubscribe risk)

Sales page / long-form:

  • Direct response copywriter (offer structure, objection handling, urgency)
  • Skeptical buyer persona (proof gaps, trust issues, red flags)
  • Editor (flow, readability, conciseness)
  • SEO specialist (keyword coverage, search intent alignment)

Scoring Rubric

ScoreMeaning
9-10Publish-ready. No meaningful improvements.
7-8Strong. Minor tweaks only.
5-6Functional but has clear gaps. Needs another pass.
3-4Significant issues. Major revision needed.
1-2Fundamentally broken. Rethink approach.

When to Use

  • Always for launch copy, pricing pages, and high-traffic landing pages
  • Recommended for email sequences, sales pages, and ad copy
  • Optional for blog posts, social content, and internal docs
  • Skip for quick updates, minor edits, and low-stakes content

Quick-Pass Editing Checks

Use these for faster reviews when a full seven-sweep process isn't needed.

Word-Level Checks

Cut these words:

  • Very, really, extremely, incredibly (weak intensifiers)
  • Just, actually, basically (filler)
  • In order to (use "to")
  • That (often unnecessary)
  • Things, stuff (vague)

Replace these:

WeakStrong
UtilizeUse
ImplementSet up
LeverageUse
FacilitateHelp

Replace with the fact (a synonym swap just makes a new tell):

VagueWrite the fact instead
Innovative / cutting-edgeWhat it does that alternatives don't
RobustThe uptime, scale, or failure case it handles
SeamlessThe real setup step count or time

Watch for:

  • Adverbs (usually unnecessary)
  • Passive voice (switch to active)
  • Nominalizations (verb → noun: "make a decision" → "decide")

Sentence-Level Checks

  • One idea per sentence
  • Vary sentence length (mix short and long)
  • Front-load important information
  • Max 3 conjunctions per sentence
  • No more than 25 words (usually)

Paragraph-Level Checks

  • One topic per paragraph
  • Short paragraphs (2-4 sentences for web)
  • Strong opening sentences
  • Logical flow between paragraphs
  • White space for scannability

AI-Tell Check

Run this on every edit, after the sweeps. A reader who spots an AI tell tends to doubt the claims around it. The shape of a sentence gives it away more than any word does.

Fix every instance of these:

PatternExampleFix
Contrast reveal"It's not X, it's Y." "Not because X. Because Y."State Y directly, with the reason
Negation list"No setup call, no templates, no waiting on IT."Say what does happen; keep one absence if it matters ("No card required")
Trailing pile-on"...the data you already have, no exports, no spreadsheets." / "..., ensuring nothing slips."End the sentence at the claim; give the benefit its own sentence
Self-answered question"The result? 3x faster."Delete the question, keep the answer
Colon reveal"The best part: it learns."Write a normal sentence
Stock phrases"In today's fast-paced world," "Whether you're X or Y," "Here's the thing," "Say goodbye to," "X, reimagined," "Unlock the power of"Cut, then open with the reader's problem or the fact
Em dashes in short copyHeadlines, subheads, CTAs, ads, social posts, subject lines (1–2 per page max in long copy)Period, comma, or colon

Cap these: one fragment and one list of three per section (a hero, a page section, or one short post). Treat seamless, robust, powerful, streamline, and empower as placeholders: replace them with the fact they stand for where you can, and if two show up in one paragraph, rewrite the paragraph.

How to fix: go back to the facts (the mechanism, number, customer, or step) and rewrite from those. Swapping in synonyms creates new tells. If the fact isn't available, mark [NEED: ...] instead of inventing one. Keep the brand's register. A formal sentence that makes a specific claim is fine.

Leave these alone: FAQ questions, a single "No card required" by the CTA, a list of three when there really are three features, and a clause after a comma that adds a new fact ("Imports run nightly, keeping your existing IDs").

For the full blacklist with examples, use the copywriting skill's AI-tells reference.


Copy Editing Checklist

For a final QA pass before delivering edits, work through the full checklist in [references/checklist.md](references/checklist.md) — covering all seven sweeps plus pre-start and final-check items.


Common Copy Problems & Fixes

Problem: Wall of Features

Symptom: List of what the product does without why it matters

Fix: Add "which means..." after each feature to bridge to benefits

Problem: Corporate Speak

Symptom: "Leverage synergies to optimize outcomes"

Fix: Ask "How would a human say this?" and use those words

Problem: Weak Opening

Symptom: Starting with company history or vague statements

Fix: Lead with the reader's problem or desired outcome

Problem: Buried CTA

Symptom: The ask comes after too much buildup, or isn't clear

Fix: Make the CTA obvious, early, and repeated

Problem: No Proof

Symptom: "Customers love us" with no evidence

Fix: Add specific testimonials, numbers, or case references

Problem: Generic Claims

Symptom: "We help businesses grow"

Fix: Specify who, how, and by how much

Problem: Mixed Audiences

Symptom: Copy tries to speak to everyone, resonates with no one

Fix: Pick one audience and write directly to them

Problem: Reads as AI-Written

Symptom: "Not X. Y." reveals, "no X, no Y, no Z" lists, long sentences trailing extra clauses, stock openers

Fix: Run the AI-Tell Check above and rewrite those sentences from the underlying facts

Problem: Feature Overload

Symptom: Listing every capability, overwhelming the reader

Fix: Focus on 3-5 key benefits that matter most to the audience


Working with Copy Sweeps

When editing collaboratively:

  1. Run a sweep and present findings - Show what you found, why it's an issue
  2. Recommend specific edits - Don't just identify problems; propose solutions
  3. Request the updated copy - Let the author make final decisions
  4. Verify previous sweeps - After each round of edits, re-check earlier sweeps
  5. Repeat until clean - Continue until a full sweep finds no new issues

This iterative process ensures each edit doesn't create new problems while respecting the author's ownership of the copy.


References

  • [Plain English Alternatives](references/plain-english-alternatives.md): Replace complex words with simpler alternatives
  • [Content Refresh](references/content-refresh.md): SERP gap analysis, full checklist, refresh vs. rewrite matrix, and cadence guide
  • [Copy Editing Checklist](references/checklist.md): Full QA checklist across all seven sweeps plus the AI-tell check

Content Refresh Editing

Copy editing isn't just for new content. Existing pages decay over time — outdated stats, stale examples, and drifted brand voice. Use the content refresh framework when traffic is declining, data is stale, or the product has changed.

For the SERP gap analysis, full refresh checklist, refresh vs. rewrite decision matrix, and cadence guide: See [references/content-refresh.md](references/content-refresh.md)


Task-Specific Questions

  1. What's the goal of this copy? (Awareness, conversion, retention)
  2. What action should readers take?
  3. Are there specific concerns or known issues?
  4. What proof/evidence do you have available?
  5. Is this new copy or a refresh of existing content?

Related Skills

  • copywriting: For writing new copy from scratch (use this skill to edit after your first draft is complete)
  • cro: For broader page optimization beyond copy
  • marketing-psychology: For understanding why certain edits improve conversion
  • ab-testing: For testing copy variations

When to Use Each Skill

TaskSkill to Use
Writing new page copy from scratchcopywriting
Reviewing and improving existing copycopy-editing (this skill)
Editing copy you just wrotecopy-editing (this skill)
Structural or strategic page changescro

质量与来源

所属仓库
coreyhaines31/marketingskills
仓库星标
5.4 万
最近更新
3 天前
采集时间
今天
commit
1efedbc5148b
内容指纹
sha256:d23184ad62cbe29
文件路径
skills/copy-editing/SKILL.md

同仓库其它 Skill

查看全部 50 个
ab-testing
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," or "experiment playbook." Use this whenever someone is comparing two approaches and wants to measure which performs better, or when they want to build a systematic experimentation practice. For tracking implementation, see analytics. For page-level conversion optimization, see cro.
精选 coreyhaines31/marketingskills 5.4 万 原文
Claude CodeCodex CLICursor
ad-creative
When the user wants to generate, iterate, or scale ad creative — headlines, descriptions, primary text, or full ad variations — for any paid advertising platform. Also use when the user mentions 'ad copy variations,' 'ad creative,' 'generate headlines,' 'RSA headlines,' 'bulk ad copy,' 'ad iterations,' 'creative testing,' 'write me some ads,' 'Facebook ad copy,' 'Google ad headlines,' 'LinkedIn ad text,' 'static ads,' 'ad templates,' 'iMessage ad,' 'chat reveal ad,' 'ChatGPT ad,' 'Apple Notes ad,' 'AirDrop ad,' 'creative strategy,' 'creative roadmap,' 'creative retro,' 'hook writing,' 'creative review page,' 'present ad creative for approval,' 'motion video ad,' 'faceless video ad,' 'UGC ad,' 'greenscreen ad,' 'TikTok/Reels ad format,' 'which ad format to make,' 'Meta ad format tier list,' or 'creative format taxonomy.' Use it to produce or iterate ad copy at scale. Copy avoids AI tells like 'it's not X, it's Y' reveals. For campaign strategy and targeting, see ads. For landing page copy, see copywriting.
精选 coreyhaines31/marketingskills 5.4 万 原文
Claude CodeCodex CLICursor
ads
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,' 'ROAS,' 'CPA,' 'ad campaign,' 'retargeting,' 'audience targeting,' 'Google Ads,' 'Facebook ads,' 'LinkedIn ads,' 'ad budget,' 'cost per click,' 'ad spend,' 'should I run ads,' 'ABM,' 'account-based marketing,' 'B2B ads,' 'lead quality,' 'negative keywords,' 'Performance Max,' 'thought leader ads,' 'when should I kill an ad,' 'search terms report,' 'wasted spend,' or 'is this campaign working.' Use this for campaign strategy, audience targeting, bidding, and optimization. For bulk ad creative generation and iteration, see ad-creative. For landing page optimization, see cro. For outbound to target accounts, see cold-email.
精选 coreyhaines31/marketingskills 5.4 万 原文
Claude CodeCodex CLICursor
ai-seo
When the user wants to optimize content for AI search engines, get cited by LLMs, or appear in AI-generated answers. Also use when the user mentions 'AI SEO,' 'AEO,' 'GEO,' 'LLMO,' 'answer engine optimization,' 'generative engine optimization,' 'LLM optimization,' 'AI Overviews,' 'optimize for ChatGPT,' 'optimize for Perplexity,' 'AI citations,' 'AI visibility,' 'zero-click search,' 'how do I show up in AI answers,' 'LLM mentions,' 'optimize for Claude/Gemini,' 'llms.txt,' 'llms-full.txt,' 'OKF,' 'Open Knowledge Format,' 'knowledge bundle,' 'agent-readable site,' 'agent readiness,' 'is my site agent-ready,' 'WebMCP,' 'do listicles still work for AI,' 'ChatGPT stopped citing comparison pages,' 'how do LLMs see our brand,' 'LinkedIn for AEO,' or 'AI citation format shift.' Use this whenever someone wants their content to be cited or surfaced by AI assistants and AI search engines. For traditional technical and on-page SEO audits, see seo-audit. For structured data implementation, see schema.
精选 coreyhaines31/marketingskills 5.4 万 原文
Claude CodeCodex CLICursor
analytics
When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions "set up tracking," "GA4," "Google Analytics," "conversion tracking," "event tracking," "UTM parameters," "tag manager," "GTM," "analytics implementation," "tracking plan," "how do I measure this," "track conversions," "Mixpanel," "Segment," "are my events firing," or "analytics isn't working." Use this whenever someone asks how to know if something is working or wants to measure marketing results. For choosing attribution models, comparing multi-touch/MMM/incrementality, or reconciling conflicting numbers across tools, see attribution. For A/B test measurement, see ab-testing.
精选 coreyhaines31/marketingskills 5.4 万 原文
Claude CodeCodex CLICursor
aso
When the user wants to audit or optimize an App Store or Google Play listing. Also use when the user mentions 'ASO audit,' 'app store optimization,' 'optimize my app listing,' 'improve app visibility,' 'app store ranking,' 'audit my listing,' 'why aren't people downloading my app,' 'improve my app conversion,' 'keyword optimization for app,' or 'compare my app to competitors.' Use when the user shares an App Store or Google Play URL and wants to improve it.
精选 coreyhaines31/marketingskills 5.4 万 原文
Claude CodeCodex CLICursor

相似 Skill

更多「写作」
interview-prep
Prepares the user for a specific interview from their real experience. Builds a story bank in Situation/Task/Action/Result/Reflection form mapped to the competencies the role and company test (such as Amazon's Leadership Principles), writes a cited company and role brief from public sources, predicts questions per round, drafts opener, why-us, weakness and salary answers, prepares questions to ask and a logistics checklist, and runs a post-interview debrief. Use when the user says "help me prepare for my interview", "I have an interview tomorrow" or "in 2 hours", "build my story bank", "STAR stories", "interviewing as a career changer", "what will they ask me", "how do I answer tell me about yourself", "questions to ask the interviewer", "research the company" or "debrief my interview". Uses Reactive Resume MCP tools when connected. For scored role-play practice, mock-interview; for thank-you notes and tracking, job-application-manager; for a salary number, offers or negotiation, offer-negotiation.
精选 reactive-resume/reactive-resume 4.4 万 原文
Claude CodeCodex CLIGemini CLI
job-application-manager
Runs the job-search pipeline. Adds jobs from a link or pasted posting, keeps stages and dates accurate, sets follow-ups, runs a weekly review (stale applications, next actions, funnel stats), records the exact resume version sent, and drafts networking, LinkedIn, referral, recruiter-reply, follow-up, thank-you, status-check, expedite and withdrawal messages without sending them. Use when the user says "add this job to my tracker", "I applied", "log my interview", "I got rejected", "I was ghosted", "log my offer", "track my applications", "do my weekly review", "what should I follow up on", "write a thank-you note", "message this recruiter", "ask for a referral", "withdraw my application", or wants a job-search spreadsheet. Works with a Markdown/CSV tracker or Reactive Resume MCP tools. Not for resume work (resume-tailor, resume-bullet-writer, resume-content-guide), interview prep or practice (interview-prep, mock-interview), or judging, negotiating, accepting or declining an offer (offer-negotiation).
精选 reactive-resume/reactive-resume 4.4 万 原文
Claude CodeCodex CLIGemini CLI
mock-interview
Runs a mock interview for a specific job description. Plays the interviewer in a chosen round (recruiter screen, hiring manager, behavioral, coding, system design, case, product sense, panel), persona and difficulty; asks one question at a time, probes vague answers, and gives quote-backed rubric scores after each answer (coach mode) or at the end (realistic). Model answers use only the user's real experience. Use when the user says "mock interview me", "interview me for this job", "practice interview", "pretend you're the interviewer", "grill me for this role", "run a behavioral round", "quick recruiter screen", "hiring-manager mock", "system design mock" or "case interview practice". With Reactive Resume MCP it reads the application and stories and logs the session. For a story bank, company brief, questions to ask or a real-interview debrief, interview-prep; for scheduling or thank-you notes, job-application-manager; for fixing the resume, resume-tailor; for negotiation practice, offer-negotiation.
精选 reactive-resume/reactive-resume 4.4 万 原文
Claude CodeCodex CLIGemini CLI
offer-negotiation
Evaluates and negotiates job offers. Decodes base, bonus, equity, sign-on, level and terms with unknowns kept unknown and each offer in its own currency, benchmarks against checkable pay data, finds true leverage, drafts one counter as email and call script, role-plays the recruiter, and handles the salary-expectations number, deadlines and extensions, "best and final", competing offers, counteroffers and written acceptance or decline. Country-aware (India CTC, 13th-month pay, public-sector scales). Use when the user says "I got an offer of...", "is this offer good", "should I negotiate", "how do I counter", "compare my offers", "what is my equity worth", "they asked my salary expectations", "they want an answer by Friday", "can I ask for more time", "should I accept" or "practice the negotiation call". Uses Reactive Resume MCP tools when connected. For logging the offer, its deadline and withdrawal notes, job-application-manager; for other interview answers, interview-prep.
精选 reactive-resume/reactive-resume 4.4 万 原文
Claude CodeCodex CLIGemini CLI
resume-builder
Builds a complete resume from scratch as Reactive Resume JSON that conforms to the schema and imports at https://rxresu.me. Asks for each missing detail instead of inventing it, then produces valid JSON (UUIDs, HTML descriptions, template and layout). Use when the user wants to create, build or generate a new resume, turn their work history into Reactive Resume JSON, or asks about the Reactive Resume schema, sections, templates or layout. For what belongs on a resume or a resume audit use resume-content-guide; for rewriting bullets, resume-bullet-writer; for fitting one job posting, resume-tailor; for tracking applications, job-application-manager; for interviews, interview-prep or mock-interview.
精选 reactive-resume/reactive-resume 4.4 万 原文
Claude CodeCodex CLIGemini CLI
resume-bullet-writer
Turns resume duties into truthful impact bullets. Questions the user role by role to dig out achievements, asks for real numbers or honest ranges (never invents them), and writes concise bullets in XYZ, CAR, scope or qualitative form. Use when the user says "rewrite my bullets", "make this bullet stronger", "quantify my resume", "turn my duties into achievements", "improve my experience section", "my resume sounds boring", "I don't have any numbers", pastes resume lines for feedback, or works in a low-number job (nursing, teaching, care, trades, admin, creative). With the Reactive Resume MCP server connected, it edits experience, project, volunteer and education descriptions with apply_resume_patch after the user approves. Use resume-content-guide instead for which sections or details belong and for summaries or headlines, resume-tailor to fit one job posting, interview-prep or mock-interview for interview stories and practice, and resume-builder to build a resume from scratch.
精选 reactive-resume/reactive-resume 4.4 万 原文
Claude CodeCodex CLIGemini CLI