Negotiation
v1.0.0Negotiate on behalf of your principal with hard limits, graduated autonomy, and mandatory human approval for commitments.
⭐ 2· 661·0 current·0 all-time
byIván@ivangdavila
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
Name, description, and included docs (buying.md, selling.md, p2p.md, professional.md) all align with a negotiation assistant. The skill requests no environment variables, binaries, or other resources that would be unrelated to negotiation functionality.
Instruction Scope
Runtime instructions are specific about required negotiation parameters, autonomy levels, and escalation triggers. They instruct the agent to 'Log everything' and to 'Build' a negotiation profile over time but do not specify where or how to store these logs/profiles or what retention/permission model to use—this is a deliberate design choice but leaves an operational decision to the agent environment.
Install Mechanism
Instruction-only skill with no install spec and no code files to execute. Low risk from install mechanism because nothing is downloaded or written by the skill itself.
Credentials
The skill declares no required environment variables, credentials, or config paths. It does not ask for unrelated secrets or system access in its instructions.
Persistence & Privilege
always:false and autonomous invocation allowed (default) are appropriate. The only persistence-related concern is that the instructions encourage building and storing a negotiation profile and 'logging everything'—those are reasonable for this purpose but the skill does not define storage boundaries, access controls, or data retention, which are left to the host environment.
Assessment
This skill appears to do what it claims (a negotiation assistant) and doesn't request extra credentials or install anything. Before installing, decide and document: (1) where logs and the negotiation profile will be stored, who can access them, and how long they're retained; (2) the exact mechanism by which the agent will send messages or make commitments (ensure human approval gates are enforced); and (3) policy for handling sensitive inputs (current salary, bank/payment details) so the agent doesn't accidentally record or transmit them. If you will let the agent act autonomously at higher levels, explicitly record per-category autonomy grants and review them periodically.Like a lobster shell, security has layers — review code before you run it.
latestvk974yk8rydeqzm352yeapcahks810zjv
License
MIT-0
Free to use, modify, and redistribute. No attribution required.