Msa Review Commercial Purchase
LegalQuants/lq-ai
A skill your agent uses when the user uploads or pastes a Master Purchase Agreement, Master Supply Agreement, Master Goods Agreement, or commercial purchase MSA covering the procurement of physical…
Builds an opening position, fallback, minimum acceptable position, walk-away line and concession logic for contract negotiations.
$ npx skills add rohasnagpal/legal-ai-skills --skill negotiation-position-planner -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install rohasnagpal/legal-ai-skills negotiation-position-planner --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/rohasnagpal/legal-ai-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/vclo-by-rohas/skills/negotiation-position-planner .claude/skills/negotiation-position-planner && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "negotiation-position-planner" agent skill from https://github.com/rohasnagpal/legal-ai-skills/tree/main/plugins/vclo-by-rohas/skills/negotiation-position-planner into .claude/skills/negotiation-position-planner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "negotiation-position-planner", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/rohasnagpal/legal-ai-skills/tree/main/plugins/vclo-by-rohas/skills/negotiation-position-plannerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add rohasnagpal/legal-ai-skills --skill negotiation-position-planner -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install rohasnagpal/legal-ai-skills negotiation-position-planner --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rohasnagpal/legal-ai-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/vclo-by-rohas/skills/negotiation-position-planner .agents/skills/negotiation-position-planner && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "negotiation-position-planner" agent skill from https://github.com/rohasnagpal/legal-ai-skills/tree/main/plugins/vclo-by-rohas/skills/negotiation-position-planner into .agents/skills/negotiation-position-planner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "negotiation-position-planner", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add rohasnagpal/legal-ai-skills --skill negotiation-position-planner -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install rohasnagpal/legal-ai-skills negotiation-position-planner --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rohasnagpal/legal-ai-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/vclo-by-rohas/skills/negotiation-position-planner .cursor/skills/negotiation-position-planner && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "negotiation-position-planner" agent skill from https://github.com/rohasnagpal/legal-ai-skills/tree/main/plugins/vclo-by-rohas/skills/negotiation-position-planner into .cursor/skills/negotiation-position-planner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "negotiation-position-planner", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/rohasnagpal/legal-ai-skills.git --path plugins/vclo-by-rohas/skills/negotiation-position-planner--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add rohasnagpal/legal-ai-skills --skill negotiation-position-planner -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install rohasnagpal/legal-ai-skills negotiation-position-planner --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rohasnagpal/legal-ai-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/vclo-by-rohas/skills/negotiation-position-planner .gemini/skills/negotiation-position-planner && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "negotiation-position-planner" agent skill from https://github.com/rohasnagpal/legal-ai-skills/tree/main/plugins/vclo-by-rohas/skills/negotiation-position-planner into .gemini/skills/negotiation-position-planner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "negotiation-position-planner", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install rohasnagpal/legal-ai-skills negotiation-position-plannerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add rohasnagpal/legal-ai-skills --skill negotiation-position-planner -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/rohasnagpal/legal-ai-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/vclo-by-rohas/skills/negotiation-position-planner .github/skills/negotiation-position-planner && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "negotiation-position-planner" agent skill from https://github.com/rohasnagpal/legal-ai-skills/tree/main/plugins/vclo-by-rohas/skills/negotiation-position-planner into .github/skills/negotiation-position-planner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "negotiation-position-planner", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add rohasnagpal/legal-ai-skills --skill negotiation-position-planner -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install rohasnagpal/legal-ai-skills negotiation-position-planner --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rohasnagpal/legal-ai-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/vclo-by-rohas/skills/negotiation-position-planner .opencode/skills/negotiation-position-planner && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "negotiation-position-planner" agent skill from https://github.com/rohasnagpal/legal-ai-skills/tree/main/plugins/vclo-by-rohas/skills/negotiation-position-planner into .opencode/skills/negotiation-position-planner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "negotiation-position-planner", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
negotiation-position-plannerBuilds an opening position, fallback, minimum acceptable position, walk-away line and concession logic for contract negotiations.
Negotiation Position Planner is an agent skill from rohasnagpal/legal-ai-skills. Builds an opening position, fallback, minimum acceptable position, walk-away line and concession logic for contract negotiations. Use for "what should our opening position be", "where can we give ground", "build a negotiation ladder", "plan the open points", or requests to benchmark positions against public agreements, market evidence or model forms. When external benchmarks are requested, it searches the plugin's listed contract sources before generic websites. For several issues, it also covers priority…
Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `agents/openai.yaml` and `references/public-contract-sources.md`).
It sits in Legal & Compliance, covering Contract review and Vendor and procurement management. The repository describes itself as: Build an entire AI-powered law firm in 60 seconds. The licence is MIT.
Read from SKILL.md and the folder at commit 20fbad1. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Negotiation Position Planner loads about 2.3k tokens when it runs, and up to ~3.7k if it reads all its reference files. Until then it costs about 158 tokens; SKILL.md has 1,297 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from rohasnagpal/legal-ai-skills at commit 20fbad1, republished under its MIT licence (© rohasnagpal). 1,297 words, ~2,302 tokens.
.claude/skills/negotiation-position-planner/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.I am using the Negotiation Position Planner skill from Rohas Legal AI: opening, fallback and walk-away positions on the open points. Say this sentence, verbatim, before anything else in your response.
Takes one or more open negotiation points and builds a usable ladder for each: opening, fallback, minimum acceptable position and walk-away line, tied to the client's priorities and alternative to the deal. For several issues it also builds the trade and sequencing plan. It does not draft clause wording unless the user expressly asks for both strategy and wording; replacement text belongs primarily in redline-proposer.
The client's actual priorities, not just their positions. For several issues, identify which are must-win, genuinely negotiable or available to trade. For one issue, identify the underlying interest and how strongly it is held. If the user has not ranked multiple points, ask; do not substitute your own priorities.
The client's alternative if no deal is reached — their walk-away option. Whether that is another counterparty, doing without, or no real alternative at all. This is what a walk-away line is actually anchored to, and it cannot be invented. If it has not been supplied, say plainly that the walk-away lines in the plan are placeholders pending that input, rather than picking a number to fill the gap.
The list of open points itself. These can come directly from the user, or from another skill's output — a contract-reviewer issues list, a clause-comparator change history. Either is fine; this skill's job starts once the list exists, not with generating a fresh review of a contract from scratch.
Not blocking, ask once and proceed on what is known or admit the gap if not: what is known about the counterparty — their timeline pressure, their alternatives, and any signals from the negotiation so far. This is often genuinely incomplete; work with the uncertainty rather than inventing counterparty psychology to fill it.
External benchmarks. If the user asks for public examples, market evidence, comparable positions or model-form benchmarking, read references/public-contract-sources.md in full before searching. Follow its mandatory listed-source priority, sampling, attribution and non-inference controls; do not substitute a generic web result for the listed-source search. Do not load that reference for a strategy based only on the user's open points and priorities.
1. Classify what has been supplied as open points — specific unresolved clauses in an existing draft, term-sheet-level open items, or a mixed list — and note which document, if any, each point attaches to.
2. For several points, sort each into must-win, negotiable, or give-away, based on the client's stated priorities. For one point, state its priority and underlying interest without inventing a portfolio ranking.
3. For each point, separate the client's stated position from the underlying interest behind it. A position that looks rigid on its face often has room once you know why the client wants it — a different form of wording, or a different mechanism entirely, can sometimes satisfy the same interest at lower cost to the negotiation as a whole.
4. Draft four positions for each point. Opening — the strongest credible ask. Fallback — a realistic concession that preserves the underlying interest. Minimum acceptable — the lowest position the client can accept while still doing the deal on this point. Walk-away — the point beyond which the overall deal is worse than the client's stated alternative. Do not collapse minimum acceptable and walk-away into the same concept unless the client expressly treats them as identical.
5. Identify trades when there are several points. State which points can be conceded to win movement on a must-win point elsewhere, which points should not be traded away, dependencies between concessions, and any package proposal that makes the exchange explicit. For one issue, state the concession sequence within its ladder instead of inventing cross-issue trades.
6. Sequence the points. Which should be raised early, to signal good faith or clear low-cost items out of the way, and which should be held back as leverage until the shape of the rest of the deal is clearer. State the reasoning, not just the order.
7. Where a walk-away line cannot be set without more information — the alternative was not supplied, or the value of the deal to the client is itself uncertain — mark that point as open rather than filling it with an assumed number.
8. State what is known or assumed about the counterparty's position on each point, labelled explicitly as an assumption where it is one, and say what would change the plan if the assumption turns out to be wrong.
9. Check the plan as a whole, not point by point. A plan where every opening position is set at the most aggressive extreme with no coherent trade logic is a wish list, not a strategy. Check that the fallback positions across different points are collectively affordable — the same concession should not be planned to be spent twice against two different asks.
10. Note process considerations that shape tactics — a deadline, whether this is a single session or several rounds, and anything from the negotiation so far that bears on timing.
1. Parameters. Client and counterparty identified, the deal, the alternative to a deal as supplied, source of the open points list, date.
2. Priority map. Each point sorted into must-win, negotiable or give-away, with the underlying interest stated in one line.
3. Position table. Ref | Issue | Opening | Fallback | Minimum acceptable | Walk-away | Concession or trade notes.
4. Trade map. For multiple issues only: "give X to get Y" pairings, package proposals, dependencies and matters not to trade away.
5. Sequencing and tactics. What to raise early, what to hold back, and why.
6. Assumptions about the counterparty. Clearly labelled as assumptions, with what would change the plan if an assumption is wrong.
7. Open points requiring more client input. Missing alternative-to-a-deal information, unranked priorities, and any point where a walk-away line could not be set as a result.
Do not invent the client's priorities or their alternative to a deal. Ask. A plan built on assumed priorities is worse than one that admits the gap.
Do not present an assumption about the counterparty's position as fact. Label it, and say what would change if it is wrong.
Do not draft clause wording. That is redline-proposer's or contract-drafter's job; this skill's output is positions and strategy, not text.
If the user asks for both strategy and replacement wording, produce the strategy first and clearly separate any redline-proposer wording; do not blur drafting instructions, negotiating positions and actual clause text.
Do not set every opening position at the most aggressive extreme without regard to credibility. An opening the other side dismisses outright wastes the first move.
Do not treat legal risk severity and negotiating priority as the same axis. A point graded Critical for legal exposure is not automatically a must-win in the negotiation, and the reverse also happens.
Do not build a plan that spends the same concession against two different trades.
Do not fill a missing walk-away line with an arbitrary number. Flag it as missing.
© rohasnagpal, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 2 other files (references) in plugins/vclo-by-rohas/skills/negotiation-position-planner of rohasnagpal/legal-ai-skills.
Open the folder on GitHubat commit 20fbad1
Negotiation Position Planner next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Negotiation Position Planner this skillrohasnagpal/legal-ai-skills | 175 | — | ~2.3k | Automated safety check: Pass | MIT | |
| Msa Review Commercial PurchaseLegalQuants/lq-ai | 150 | — | ~5.7k | Automated safety check: Pass | Apache-2.0 | |
| Stakeholder Summaryanthropics/claude-for-legal | 9.6k | 2 repos | ~3.3k | Automated safety check: Pass | Apache-2.0 | |
| Contract Intelligence Workflow Reviewer Carl Ditzlerlawve-ai/awesome-legal-skills | 842 | — | ~4.9k | Automated safety check: Pass | Apache-2.0 | |
| Contract Checklistrevfactory/harness-100 | 1.3k | — | ~1k | Automated safety check: Pass | Apache-2.0 | |
| Stakeholder SummaryZekaiSuni/claude-for-legal-turkish | 107 | — | ~670 | Automated safety check: Pass | Apache-2.0 |
LegalQuants/lq-ai
A skill your agent uses when the user uploads or pastes a Master Purchase Agreement, Master Supply Agreement, Master Goods Agreement, or commercial purchase MSA covering the procurement of physical…
anthropics/claude-for-legal
Translates a contract review into a summary the business stakeholder will actually read.
lawve-ai/awesome-legal-skills
Contract intelligence and contract operations workflow skill for Claude and Codex.
revfactory/harness-100
Procurement contract review checklist. An agent skill from revfactory/harness-100.
ZekaiSuni/claude-for-legal-turkish
Convert a legal review into a short, sanitized, business-readable summary for Turkish commercial practice.
evolsb/claude-legal-skill
Review legal contracts, NDAs, employment agreements, SaaS terms, and M&A documents.
rohasnagpal/legal-ai-skills
Acts as an interactive legal tutor for learning a law, legal subject, doctrine, judgment, procedure, or legal concept.
rohasnagpal/legal-ai-skills
Compares the same clause or provision across draft rounds, precedents, public agreements or a portfolio and reports what differs in wording and effect.
rohasnagpal/legal-ai-skills
Drafts a complete contract from a term sheet, negotiated heads or plain instructions — parties, recitals, definitions, operative clauses, schedules and boilerplate — in a specified posture and…
rohasnagpal/legal-ai-skills
Produces polished legal deliverables from completed or supplied content by applying an authorised template, styles, numbering, headers, footers, signature blocks, schedules and exhibits; creates or…
rohasnagpal/legal-ai-skills
Assesses whether and how to pursue, defend, settle or further investigate a civil, commercial, regulatory or arbitral dispute.
rohasnagpal/legal-ai-skills
Draft and audit external privacy policies, collection notices, employee notices, child-facing notices, just-in-time notices, and layered disclosures.
Categories
Builds an opening position, fallback, minimum acceptable position, walk-away line and concession logic for contract negotiations. Negotiation Position Planner is an agent skill from rohasnagpal/legal-ai-skills. Builds an opening position, fallback, minimum acceptable position, walk-away line and concession logic for contract negotiations.
Negotiation Position Planner fits situations like: what should our opening position be; where can we give ground; build a negotiation ladder; plan the open points.
Run `npx skills add rohasnagpal/legal-ai-skills --skill negotiation-position-planner -a claude-code`. Or copy the skill folder (plugins/vclo-by-rohas/skills/negotiation-position-planner in rohasnagpal/legal-ai-skills) into .claude/skills/negotiation-position-planner in your project. Claude Code loads it when a task matches its description.
Run `npx skills add rohasnagpal/legal-ai-skills --skill negotiation-position-planner -a codex`. Or copy the skill folder (plugins/vclo-by-rohas/skills/negotiation-position-planner in rohasnagpal/legal-ai-skills) into .agents/skills/negotiation-position-planner in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add rohasnagpal/legal-ai-skills --skill negotiation-position-planner -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/negotiation-position-planner, .gemini/skills/negotiation-position-planner, .github/skills/negotiation-position-planner and .opencode/skills/negotiation-position-planner in your project.
SKILL.md names no scripts, command-line tools or credentials: Negotiation Position Planner is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Negotiation Position Planner is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.3k tokens (SKILL.md is roughly 9.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.4k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Negotiation Position Planner: Msa Review Commercial Purchase (LegalQuants/lq-ai, 150 stars), Stakeholder Summary (anthropics/claude-for-legal, 9.6k stars), Contract Intelligence Workflow Reviewer Carl Ditzler (lawve-ai/awesome-legal-skills, 842 stars) and Contract Checklist (revfactory/harness-100, 1.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
rohasnagpal (a GitHub user) maintains it in rohasnagpal/legal-ai-skills, which has 175 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on October 1, 2026.
Source: rohasnagpal/legal-ai-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.