Negotiation
v0.1.0Navigate negotiations as a solopreneur — pricing, scope, terms, and contracts. Use when a prospect pushes back on price, wants to change scope, disputes term...
⭐ 0· 504·1 current·1 all-time
byJatin Khatri@jk-0001
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name and description (negotiation for solopreneurs) align with the SKILL.md content: frameworks, scripts, objection responses, BATNA, anchoring, and role-specific scenarios. The skill requests no environment variables, binaries, or installs, which is proportionate for a text-based coaching/playbook skill.
Instruction Scope
SKILL.md contains only negotiation frameworks, sample scripts, and step-by-step guidance. It does not instruct the agent to read local files, access environment variables, call external endpoints, transmit data to third parties, or modify system state. It does reference other topics (e.g., outreach-and-prospecting) but only as contextual reading, not as actionable access to other skills or credentials.
Install Mechanism
No install spec and no code files — this is instruction-only. Nothing will be downloaded or written to disk by the skill itself, which minimizes installation risk.
Credentials
The skill declares no required environment variables, no primary credential, and no config paths. That is proportional to a text-based negotiation playbook.
Persistence & Privilege
always is false and the skill does not request persistent system privileges or to modify other skills' configurations. Autonomous invocation is allowed (platform default) but that is appropriate for a helper skill that responds to user prompts.
Assessment
This skill is an instruction-only negotiation playbook and appears internally consistent and low-risk: it won't install code or ask for credentials. Before installing, keep in mind: (1) this is guidance, not legal or financial advice—use a lawyer for contract language and a financial advisor for pricing strategy if needed; (2) avoid pasting sensitive client data or full contracts into the skill prompts if you have privacy concerns; (3) if the agent invoking the skill is integrated with other services (email, calendars, CRMs), review those integrations separately since this skill itself does not request access but the agent platform might; and (4) test the skill with non-sensitive example scenarios first to ensure responses meet your expectations.Like a lobster shell, security has layers — review code before you run it.
latestvk975bf9qw2e03jw3g32y6ac1c181d507
License
MIT-0
Free to use, modify, and redistribute. No attribution required.