negotiation
Skill10 starsChanged 6 days agoMITView on GitHub
Reach an agreement that serves the important interests of the people involved, or see when no agreement is better. Use when your interests differ from another party's over terms, scope, time, resources or arrangements, or on /negotiation.
9 other projects use a version of this.
Adopted by
Most recently taken up by
- aditya-vermax/skillstheir own version, first seen Nov 8, 2026
- pradyumnasagar/open-research-skillstheir own version, first seen Nov 8, 2026
- joaoguirunas/team-ostheir own version, first seen Oct 21, 2026
- kshyam/opencode-and-claude-skillstheir own version, first seen Aug 30, 2026
- poorvith-mp/skills-businesstheir own version, first seen Aug 19, 2026
- Adhamxon/claude-code-skillstheir own version, first seen Jul 30, 2026
Other versions9 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 9
- wondelai/skills★ 2.6ksame name
- pradyumnasagar/open-research-skills★ 8same name
- joaoguirunas/team-os★ 6same name
- Adhamxon/claude-code-skills★ 2same name
- aditya-vermax/skills★ 1same name
- Bappoz/My-Claude-Skills★ 1same name
- poorvith-mp/skills-business★ 1same name
- kshyam/opencode-and-claude-skills★ 0same name
- walternate/skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository35 other files it gives its agents.
- AGENTS.mdAGENTS.md
- design-principlesSkill
- experimentationSkill
- groupingSkill
- idea-qualitySkill
- info-foragingSkill
- investingSkill
- listeningSkill
- misfitsSkill
- motivationSkill
- needs-to-signalsSkill
- optionalitySkill
- perspectiveSkill
- purposeSkill
- testingSkill
- verify-before-shipSkill
- resume-deep-diveSkill
- review-resumeSkill
- inspiring-ideaSkill
- next-goalSkill
- side-quest-recommendSkill
- still-want-itSkill
- find-the-argumentSkill
- make-presentation-slideSkill
- agent-evalsSkill
- behavior-viewSkill
- black-boxSkill
- clean-arch-domainSkill
- mutation-testingSkill
- structure-viewSkill
- test-oracleSkill
- unit-testsSkill
- user-storiesSkill
- white-boxSkill
- readableSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 2 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 8 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 22
The aim is alignment: Look for terms that serve both sides' important interests better than what each could do without a deal.
- Very specific: line 35
Define your interests: Use /purpose to state the outcome you want.
- Very specific: line 38
Understand the other party: Use /perspective to learn what they want, what they answer for, their limits and incentives, and who can decide.
- Distinctive: line 41
Ask before you propose, and list what you still assume.
- Very specific: line 42
Know the alternatives: Use /optionality to judge what happens with no deal, your best alternative and how strong it is, and theirs.
“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/negotiation
Reach an agreement that serves the important interests of the people involved, or see when no agreement is better.
Principles
- Interests, not positions. Each side states a position, but what it needs is the interests behind it. A position is one way to meet them; there are usually others.
- The aim is alignment. Look for terms that serve both sides' important interests better than what each could do without a deal. If no such terms exist, no deal is the right result.
- Differences make trades. Sides weigh issues, risk and timing differently. Those gaps let each give what costs it little and gain what matters to it.
- Honest, not open. Protecting information is fine; deceiving is not. Do not bluff about alternatives or invent someone you must consult.
- A deal is what both will keep. Agreed terms count only as commitments each side can realistically honor.
How to negotiate
- Define your interests. Use
/purposeto state the outcome you want. Sort what you want into essential, important and tradeable, and set a first minimum. - Understand the other party. Use
/perspectiveto learn what they want, what they answer for, their limits and incentives, and who can decide. Ask before you propose, and list what you still assume. - Know the alternatives. Use
/optionalityto judge what happens with no deal, your best alternative and how strong it is, and theirs. Revise your minimum to match. If your alternative is weak, improve it or buy time before you commit. Then decide whether it is worth negotiating at all: weigh what is at stake against the cost to the relationship and the risk of asking. - Create options. Find several ways to meet both sets of interests, trading across issues and testing them against fair outside standards. A proposal may be a package, or a different deal, such as smaller scope or a first step that lowers their risk.
- Evaluate and negotiate. Compare each proposal with your interests and
alternatives. Know what a concession costs you and what it gives them. Ask
the reasons behind an objection, and give a true reason with each request.
Share your interests and reasons; keep your minimum and alternatives to
yourself unless sharing them helps. Agree when each side will decide,
leaving time to judge the whole before you accept or refuse. Where future
results are uncertain, use
/experimentationfor a limited pilot, milestones or conditional terms. - Commit or walk away. Confirm the terms in writing, with the assumptions left. Name responsibilities, deliverables, dates and who decides. Set review points and what reopens the deal. If the terms miss your minimum, decline and turn to your best alternative.
Output
- Your interests, minimum and best alternative, and whether negotiating was worth it.
- Their interests, limits, who decides, and unchecked assumptions.
- The options weighed and the terms agreed, in writing.
- Responsibilities, deliverables, dates, decision rights and review points.
- The decision: agree, or no deal, and the next message.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

