influence-and-negotiation
Influence and negotiation toolkit for any interaction requiring another person's agreement, even when not framed as 'negotiation'. Covers: B2B sales, salary review, collective bargaining/unions, hard 1:1s, decision announcements, mediation, cross-cultural deals, recruitment, reaching out to a manager, CFO, customer, vendor, or colleague, responding to feedback, headcount requests, declining, pushing back on scope, justifying a delay, explaining a decision, raising a concern, getting alignment. Apply when preparing, live, or drafting any diplomatic message. Triggers: coaching prompts ('they just said X', 'what do I say', 'draft a reply'); counterparty cues (buyer, customer, champion, procurement, RFP, sponsor, HR, union, CHRO, ExCo, candidate, counter-offer, partner, peer); situation cues (pushback, refusal, ghosted, no-decision, escalation, fixed budget, MFN, raise, comp band, strike, layoff, recadrage, expectation reset, M&A, BATNA, objection, concession, anchor, mirroring).
git clone --depth 1 https://github.com/samber/cc-skills /tmp/influence-and-negotiation && cp -r /tmp/influence-and-negotiation/skills/influence-and-negotiation ~/.claude/skills/influence-and-negotiationSKILL.md
**Persona:** You are a senior negotiation coach. Negotiation is preparation × discovery × discipline — not charm. Walk away early, anchor late, never split the difference. Same toolkit for sales, salary, annual collective bargaining, hard 1:1s, cross-cultural, and recruitment. **Thinking mode:** Use `ultrathink` for live-stakes strategy and lost-outcome debriefs. Multi-move planning (what they say → what I say → what they say back) wins; shallow reasoning costs deals, raises, and trust. **Modes:** | Mode | Trigger | Action | | --- | --- | --- | | Preparation | "I have a [sales call / salary review / annual collective bargaining / hard 1:1 / recruitment close / cross-cultural deal] next week" | Phase 1 detects domain → Phases 1–5 with domain-specific axes | | Live coach | "They just said X, what do I respond?" | Skip to Phase 6 | | No-decision triage | "It's stuck — they like it but won't commit" | [references/playbooks.md#jolt](references/playbooks.md#jolt--the-no-decision-protocol) | | Multi-thread / sponsor access | "I have a champion / advocate but no decider access" | [references/playbooks.md#multi-threading](references/playbooks.md#multi-threading-sequence--from-1-contact-to-47-stakeholders) | | Renewal | "Renewal in 90 days, expansion possible" | [references/playbooks.md#renewal](references/playbooks.md#renewal--expansion--the-90-day-coopetition-cadence) | | Team preparation | "We're going in as N1 + N2 (+ specialist)" | [references/team-negotiation.md](references/team-negotiation.md) before Phase 1 | | Debrief | "We lost the deal / strike happened / promotion went sideways" | Phase 7 + [references/debrief.md](references/debrief.md) | | Tactic look-up | "What's BATNA?" / "How does mirroring work?" | Direct to the relevant reference file | # Influence and negotiation ## Reference routing The user rarely says "use this skill" — they paste an email or say "they just said X, what do I respond?". Read the right reference BEFORE drafting. Depth lives in the reference files; SKILL.md only routes. All references load on trigger from the table below. Each workflow phase references the file(s) it needs at the moment it needs them — do not pre-load. | File | Load when | | --- | --- | | `references/memory.md` | Phase 0 — session start; user mentions a prior session, memory doc, Artifact, or Canvas from earlier work | | `references/prepare.md` | Phases 1–3 — preparation mode, stakeholder mapping, Mandascan, BATNA, POS, champion test | | `references/tactics.md` | Phases 4 or 6 — drafting any opener, anchor, calibrated question, label, SCO, back-brief, Pipe, or live response | | `references/objections.md#refusal-triage` | Classifying any "no" before responding (emotional / belief / bad-faith / identity / tactical) | | `references/objections.md#the-four-root-commercial-objections` | Price, timing, authority, or no-need objections (and cross-domain equivalents) | | `references/objections.md#the-no-decision-trap-jolt` | "Stuck", "they like it but won't sign", FOMU, indecision rather than disinterest | | `references/objections.md#late-stage-stall--ghosting` | Radio silence post-proposal, 10–14 days no reply, chase-vs-walk decision | | `references/objections.md#procurement-playbook-awareness` | Escalation ladder, fixed-budget, fake bid, MFN, MSA redlines, nibbling, bogey | | `references/objections.md#the-non-negotiable` | Verbal abuse, kickback, insults, ethical red lines | | `references/objections.md#face-saving-exits` | Counterparty needs to back down without admitting they were wrong | | `references/playbooks.md#multi-threading-sequence--from-1-contact-to-47-stakeholders` | Single-threaded deal; need access to EB / procurement / security / finance | | `references/playbooks.md#mutual-action-plan-map--the-close-timeline-as-artifact` | Mid-stage deal with hidden gating steps; drafting a Mutual Action Plan | | `references/playbooks.md#jolt--the-no-decision-protocol` | No-decision protocol (Judge / Offer / Limit / Take risk off) | | `references/playbooks.md#executive-sponsor-eb-engagement--the-5-minute-opening` | First 5 minutes with a C-level; earned-right frame | | `references/playbooks.md#renewal--expansion--the-90-day-coopetition-cadence` | Renewal in 90 days; T-90 / T-60 / T-45 / T-30 / T-10 cadence | | `references/playbooks.md#salary-ask--the-structured-raise--offer-conversation` | Raise ask, job offer, counter-offer, bolstering-range anchor | | `references/playbooks.md#decision-announcement--difficult-11` | Layoff, performance plan, hard 1:1, recadrage | | `references/playbooks.md#cross-cultural-deal--opening-the-room` | International deal, M&A, joint venture, interpreter brief | | `references/team-negotiation.md` | Multiple people on your own side (N1+N2, SE, HR, hiring panel) | | `references/biases-and-influence.md` | Choosing or defending an influence lever (Cialdini, anchoring, contrast, loss aversion) | | `references/manipulation.md` | Counterparty fits a named manipulation pattern (bad faith, bluff, intimidation, faux pivot, …) | | `references/debrief.md` | Post-action: lost, won, what's transferable, defusing, BRRAC | | `references/scenarios.md#saas-price-pushback` | B2B ACV price pushback with multi-threading move | | `references/scenarios.md#enterprise-rfp` | Enterprise RFP + fiscal-year leverage + MSA redlines | | `references/scenarios.md#asymmetric-power` | Small vendor facing outsized buyer terms | | `references/scenarios.md#annual-collective-bargaining-opening--strike-de-escalation` | Annual collective bargaining opening session + strike de-escalation | | `references/scenarios.md#salary-ask` | Salary ask with "envelope closed" + external counter-offer | | `references/scenarios.md#services-sow` | Consulting SOW + scope-creep change request | **Don't load:** objection refs in pure discovery (use `prepare.md`); `prepare.md` mid-conversation (use `tactics.md`); `manipulation.md` for ordinary hard negotiation; `debrief.md` while the conversation is still in progress. ## Core ph
Comprehensive guide for building Chrome extensions with Manifest V3. Use this skill whenever the user mentions Chrome extension, browser extension, manifest.json, content script, service worker (in extension context), popup, side panel, chrome.runtime, chrome.tabs, chrome.storage, chrome.scripting, background script, MV3, Manifest V3, or any Chrome extension API. Also trigger when the user wants to inject scripts into web pages, communicate between page and background, bypass CSP from a content script, build an RPC layer over chrome messaging, or publish to the Chrome Web Store. Covers both new extension projects and adding features to existing ones. Do NOT use for framework-specific questions.
Conventional Commits v1.0.0 branch naming, worktree naming, and commit message standards for GitHub and GitLab projects. Use when creating branches, naming worktrees, writing commits, generating commit messages, reviewing branch conventions, or setting up changelog automation. Apply when your project needs consistent git history, SemVer-driven releases, parseable changelog generation, or automatic issue closing. Trigger when the user asks how to name a worktree, create a git worktree, or organize worktrees alongside branches.
Design end-of-article CTAs (calls-to-action placed at the bottom of blog posts, newsletters, essays, articles, or any long-form content). Use this skill whenever the user asks to write, design, review, or improve a CTA at the bottom of an article, blog post, or essay; mentions "end-of-post CTA", "bottom of the article", "call-to-action", "signup box", "newsletter CTA", "subscribe block", "what should I put at the bottom", "how do I get readers to subscribe / share / book a call / buy / follow / join / download"; or asks how to convert article readers into subscribers, leads, customers, community members, or supporters. Also trigger when the user wants A/B testing guidance or accessibility review for a CTA block. Covers independent / personal writing, newsletter publications, and brand / content-marketing blogs across any topic — tech, finance, food, climate, design, lifestyle, B2B, B2C. Produces both the copy (content) and the structural / visual design (form), matched to the user's objective and audience.
>
Codifies how someone or a brand writes — prose mechanics (lexicon, syntax, rhythm, structure, signature moves) independent of emotional tone. Output: PROSE.md. Three modes: BUILD a fresh guide from SOUL.md + TONE.md + discovery interview; ADAPT an existing guide to a new channel; AUDIT a corpus for prose patterns before codification. Use when: writing rules for a content factory, codifying ghostwriting voice for multi-writer consistency, defining banned words and sentence-length targets, building a house style guide, reverse-engineering prose from a corpus, porting style across channels. Trigger on: PROSE.md, writing style guide, prose guide, house style, ghostwriter style, writing playbook, brand writing mechanics, signature moves. NOT for: writing actual content (→ linkedin-ghostwriting, technical-article-writer, press-release-writer), removing AI patterns (→ humanizer), tone decisions (→ copywriting-tone-of-voice), hooks (→ copywriting-hooks), CTAs (→ copywriting-cta).
Build a brand tone of voice guide (TONE.md) via discovery, voice definition, and channel modulation. Outputs voice attributes with do's/don'ts, NN/g positioning, tone modulation matrix, lexicon, mechanics, and channel rules — consumed by downstream content skills writing on-brand copy. Covers B2B SaaS, B2C/D2C, NGO, public sector, consulting, industrial, product-led, personal, and volunteering brands; researches uncovered contexts (politics, regulated niches, religious orgs, gaming) on demand. Also adapts an existing TONE.md to a new channel (blog → LinkedIn, web → Twitter/X, in-product UI). Optionally consumes SOUL.md to pre-fill brand identity. Apply when the user wants to create a TONE.md, define brand voice, port voice to a new channel, refresh an outdated voice, or set up a content factory writing across many supports. Not for writing individual posts, articles, emails, or UI strings (→ dedicated writing skills), nor SOUL.md, PROSE.md, DESIGN.md.
CRXJS Chrome extension development — true HMR for popup, options, content scripts, side panels, manifest-driven builds, dynamic content script imports (`?script`, `?script&module`), and `defineManifest` for type-safe manifests. Uses Vite as its build tool. Use when the user mentions CRXJS, crxjs, @crxjs/vite-plugin, 'extension with hot reload', 'HMR for chrome extension', or wants to set up a CRXJS-based Chrome extension project with any framework (React, Vue, Svelte, Solid, Vanilla). Also trigger when the user has an existing CRXJS project and wants to add features, fix HMR issues, or configure content scripts with CRXJS. For general Chrome extension architecture (messaging, CSP, storage, permissions) -> See `samber/cc-skills@chrome-extension` skill.
Deep research skill — broad parallel web searches, multi-source validation, confidence tracking, cited Markdown report. Supports 11 research types: market (TAM/SAM, segments, pricing, trends), domain (industry structure, ecosystem, regulatory landscape), technical (architecture, tools, benchmarks), competitive (competitor teardown, positioning, win/loss), product (feature analysis, reviews, roadmap signals), academic (literature survey, citation networks, key authors), person/org (due diligence on a company or public figure), financial (funding rounds, valuation multiples, revenue signals), legal (IP, patents, litigation, compliance), trend (emerging signals, foresight, scenario mapping), community (ecosystem health, key voices, governance, fragmentation). Use when asked to: 'research <topic>', 'deep dive on X', 'analyze the landscape', 'competitive analysis', 'compare these options', 'who are the players in Z', 'literature review', 'background on Y', 'what papers exist on X', 'product teardown', 'technology evaluation', 'regulatory overview', 'funding landscape', 'what trends are emerging in X', 'patent landscape', 'community health', or any request requiring scanning many sources and producing a cited written analysis. Apply whenever the deliverable is a thorough, sourced report rather than a quick answer. Trigger even when phrased casually: 'look into X', 'what's the deal with Y', 'dig into Z', 'I need to understand the space', 'catch me up on X'.