Agent skill · Data & Analytics

tech-contract-negotiation-patrick-munro

Systematic contract negotiation strategies for technology services agreements with German/EU law specificity. Provides three-position framework (provider-favorable, balanced, client-favorable), deal-size calibration (€100K to €10M+), five-tier objection handling with regulatory leverage (GDPR, DORA, NIS2, BGB), concession packaging, and position matrices for liability, IP, payment, SLA, data protection, and termination. Use when: (1) Developing negotiation strategies for SaaS, cloud, or managed services agreements, (2) Preparing position papers and fallback positions, (3) Responding to counter

lawve-aigithub.com/lawve-aiGitHub ↗
claude-codeNOASSERTION
Install
npx skills add lawve-ai/awesome-legal-skills --skill tech-contract-negotiator-patrick-munro --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 3
SKILL.md size: 19 KB
Bundled scripts: none
Version: 2026-04-25
Declared author: Patrick Munro
Path: skills/tech-contract-negotiator-patrick-munro/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 618
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

Review
written from the skill's own SKILL.md · Aug 5, 2026

What it does

Provides systematic negotiation guidance for technology services agreements with German/EU law specificity, including a three-position framework (provider-favorable, balanced, client-favorable), deal-size calibration, a five-tier objection approach leveraging GDPR, DORA, NIS2, and BGB, concession packaging, and position matrices for liability, IP, payment, SLA, data protection, and termination. Also includes regulatory leverage scripts and a concession roadmap.

How it works

For each major clause, it prescribes three positions (provider-favorable opening, balanced target, client-favorable fallback) and offers deal-size specific package strategies (Small, Mid-Market, Enterprise, Strategic/Transformation). It provides five-tier objection handling, with tier-specific language and regulatory backing, plus matrices (Liability, IP, Payment Terms, Service Levels, Data Protection, Term/Termination) showing terms across the three positions. It includes example scripts referencing GDPR, NIS2, DORA, and BGB provisions to justify negotiation stances. It also outlines concession sequencing (early, middle, late rounds) and a governance-guided concession roadmap.

When to use it

Use when developing negotiation strategies for SaaS, cloud, or managed services agreements; preparing three-position papers; generating responses to counterparty objections using regulatory leverage; building concession packages; calibrating tactics to deal size; applying German and EU law constraints.

What it can touch

Contains references to regulatory provisions, contracts, and standard terms; relies on prescribed terms and regulatory-backed justification scripts. It does not specify automation tools beyond noting claude-code as a declared tool.

Caveats

Regulatory references and templates are stated as guidance for educational purposes and should be validated with qualified counsel before binding terms; does not constitute legal advice. Licensing is AGPL-3.0 as declared in metadata.

From the SKILL.md

# Tech Contract Negotiation Playbook ## Overview Systematic negotiation strategies for technology services agreements, professional services contracts, and commercial B2B transactions. Provides three-position frameworks, deal-size calibration, five-tier objection handling with regulatory leverage (GDPR, DORA, NIS2, BGB), numeric position matrices for every major clause, and concession packaging keyed to negotiation phase. ## LEGAL DISCLAIMER This skill provides negotiation frameworks for educational purposes only. It does not constitute legal advice. Users should: - Consult qualified legal counsel before entering binding agreements; - Have contracts reviewed by attorneys licensed in the relevant jurisdiction; - Verify that proposed terms comply with local contract law (German BGB AGB controls, for example, invalidate many provider-favourable clauses that would be enforceable elsewhere); - Not treat this skill as a substitute for professional legal representation. The frameworks are templates. Actual negotiations require legal expertise and business judgment. Neither the skill creator nor Claude/Anthropic assumes liability for contract terms, negotiation outcomes, or legal disputes

What's inside
Steps it walks through
  1. Overview
  2. LEGAL DISCLAIMER
  3. When to Use This Skill
  4. Core Capabilities
  5. 1. Three-Position Framework
  6. 2. Deal-Size Calibration
  7. 3. Five-Tier Objection Handling
  8. 4. Position Matrices for Key Clauses
  9. 5. Regulatory Leverage
  10. 6. Concession Sequencing
  11. 7. Concession Roadmap by Risk
  12. Best Practices
  13. Common Mistakes
  14. Industry Considerations
Ships with 2 files
  • LICENSE.txt
  • README.md
More from awesome-legal-skills
All skills →
About this skill
What does the tech-contract-negotiation-patrick-munro skill do?

Systematic contract negotiation strategies for technology services agreements with German/EU law specificity. Provides three-position framework (provider-favorable, balanced, client-favorable), deal-size calibration (€100K to €10M+), five-tier objection handling with regulatory leverage (GDPR, DORA, NIS2, BGB), concession packaging, and position matrices for liability, IP, payment, SLA, data protection, and termination. Use when: (1) Developing negotiation strategies for SaaS, cloud, or managed services agreements, (2) Preparing position papers and fallback positions, (3) Responding to counter

How do I install it?

Run `npx skills add lawve-ai/awesome-legal-skills --skill tech-contract-negotiator-patrick-munro --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From lawve-ai/awesome-legal-skills, a repository with 618 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going