Reef Negotiation
Skill by staybased
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/staybased/reef-negotiationNegotiation — Close Deals and Protect Your Value
Negotiate rates, scope, and terms using Chris Voss's FBI-proven frameworks adapted for freelance and consulting deals.
Sources: Chris Voss (Never Split the Difference), Gong.io, NAHC, Klenty, Aviso.
All outputs go to workspace/artifacts/.
Use when
- Negotiating rates with a client (Upwork, direct, retainer)
- Client pushes back on pricing after proposal
- Scope creep discussion — client wants more without paying more
- Contract terms negotiation (payment schedules, milestones, IP)
- Equity/revenue share deals (like Alfred)
- Any conversation where money or terms are on the table
Don't use when
- Initial discovery (use client-discovery skill — negotiate AFTER you understand their needs)
- Writing the proposal itself (use proposal-writing skill)
- Handling generic objections before the money talk (use objection-handling skill)
- Internal team disagreements (different dynamic entirely)
Negative examples
- "Help me find clients" → No. This is for deal-closing, not lead gen.
- "Write my Upwork proposal" → No. Use proposal-writing skill.
- "A client is unhappy with the work" → No. That's service recovery, not negotiation.
Edge cases
- Upwork client asks for lower rate → YES. Price defense framework applies.
- Client wants to add scope without budget increase → YES. Scope protection.
- Revenue share structure (Alfred) → YES. Partnership term negotiation.
- Negotiating with yourself (pricing confidence) → Borderline but useful — the inner game section helps.
Chris Voss's Core Principles
1. Tactical Empathy
Understand their perspective BEFORE pushing yours. Not fake empathy — genuine curiosity about their constraints.
In practice:
- "It sounds like budget is tight this quarter." (labeling)
- "How can we structure this so it works for both of us?" (calibrated question)
- "What would make you feel confident moving forward?" (their terms, not yours)
2. Go for "No"
Stop chasing "yes." People feel trapped by yes. When they say "no," they feel safe and in control — then they'll actually listen.
In practice:
- Instead of "Would you like to move forward?" → "Would it be a terrible idea to start with a pilot?"
- Instead of "Can we agree on $500?" → "Is $500 unreasonable for this scope?"
- After their "no": "What would you need to change to make this work?"
3. Get to "That's Right"
"That's right" = genuine alignment. "You're right" = they're dismissing you. Know the difference.
How to trigger it: Summarize their situation so accurately they say "that's right": "So if I understand correctly — you need this done by March, your budget is around $300, and your main concern is that the last developer left the project half-done. That's a lot of risk to take on again."
When they say "that's right," you own the conversation.
4. Mirroring
Repeat the last 1-3 words they said. It feels like magic — they'll elaborate, reveal more information, and feel heard.
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-staybased-reef-negotiation": {
"enabled": true,
"auto_update": true
}
}
}Related Skills
Proposal Writing
Skill by staybased
ops-hygiene
Standard operating procedures for agent maintenance, security hygiene, and system health. Use when performing periodic checks, security audits, memory maintenance, secret rotation, dependency updates, or any recurring "housekeeping" tasks. Also use when setting up automated maintenance schedules or when asked about agent security posture.
Lead Magnets
Skill by staybased
Pricing Psychology
Skill by staybased
trade-validation
10-dimension weighted scoring framework for prediction market trade evaluation. Enforces disciplined position sizing, circuit breakers, and mandatory counter-arguments. Use when: evaluating prediction market trades, scoring opportunities, deciding position sizes, comparing Polymarket/Kalshi opportunities, running pre-trade checklists. Don't use when: general crypto analysis, DeFi yield farming, non-prediction-market investments, stock/equity analysis, sports betting (different framework needed). Negative examples: - "Should I buy ETH?" → No. This is for prediction markets with binary/discrete outcomes. - "What's the best DeFi yield?" → No. Wrong domain entirely. - "Score this sports bet" → No. Sports betting has different dimensions (injuries, matchups). Edge cases: - Crypto prediction markets (e.g., "Will BTC hit $X?") → YES, use this if on Polymarket/Kalshi. - Multi-outcome markets → Score each outcome separately. - Markets with <$25 liquidity → Auto-fail on Liquidity dimension.