SKILLEMALL.ai
GitHub ↗ RU Sign in

BC 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 counterparty objections, (4) Structuring concession packages that protect core economics, (5) Calibrating tactics to deal size and leverage, or (6) Applying German contract law constraints (BGB §§ 305-310 AGB, § 309 Nr. 7 liability limits, § 288 statutory interest).

lawve-ai/awesome-legal-skills Agent Skills author: lawve-ai 3 files body ≈ 4 606 tokens Open the sourcegithub.com↗ analyzed 29 h ago

Systematic contract negotiation strategies for technology services agreements with German/EU law specificity.

As a process C 57/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

ProcedureSales and CRMLegaltype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
B
93/100
safety, quality, tests
Safety 60%
100
Quality 40%
82
Run on models
none yet
Process rating
C
57/100
Has gaps
Inputs and preconditions w 11
0
Progress reporting w 2
0
When it triggers w 12
20
the three weakest of ten parameters · all ten

How to improve

    For the model run — optional
    • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
    • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

    Guard findings · 0

    ✓ No critical or high findings

    Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 57/100

    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Progress reporting. Says nothing while it works
    • 20When it triggers. No condition that starts the skill
    • 30Running it twice. 11 mutating operations with no state check
    • 40Result and completion. Does not say what the result is
    • 40Consistency. Frontmatter name (tech-contract-negotiation-patrick-munro) differs from the folder (tech-contract-negotiator-patrick-munro)
    • 70Execution cost. Instruction body is 4606 tokens
    • 85Steps. 45 steps, 1 vague phrases
    • 100Tools and files. No external tools needed
    • 100Failures and branches. 1 branches, has a failure section
    • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing

    Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

    Quality signals

    • +5Description has no quoted example phrases that should trigger the skill
    • +4Description does not say when NOT to use the skill (false activations)
    • +3Description length 859: 120–800 characters recommended
    • +3Output format is not stated: the model decides each time
    • +2Single-language instructions
    • +4Structure: 23 headings
    • +3Step-by-step instructions: 45 items
    • +4Has examples (0 code blocks)
    • +1License stated

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 82.