Agent skill
negotiation-closing
Audits a late-stage negotiation call transcript against a rubric covering pricing sentiment, procurement momentum, contracting awareness, and closure timeline, or sweeps a CRM export for late-stage deals with no documented closing path.
Filed under Calls, demos and discovery.
From zime-ai/zime-gtm-skills · 41 skills · 14 · pushed 2026-08-26
What it does when it runs
Audits a late-stage negotiation call transcript against a rubric covering pricing sentiment, procurement momentum, contracting awareness, and closure timeline, or sweeps a CRM export for late-stage deals with no documented closing path. Use when reviewing a negotiation call, or checking pipeline for deals stuck in late stage with no clear path to close.
Read from the skill and the 3 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.
- Keys and connectors you must supply
- None found.
- Hosts it reaches
- No third-party host appears in the skill or its bundled files.
- Tool permissions it declares
- No
allowed-toolsin the frontmatter. It only issues instructions, so there is nothing to bound. - Actions present in the files
- None. Instructions only.
Install it
View source on GitHub ↗git clone --depth 1 --filter=blob:none --sparse https://github.com/zime-ai/zime-gtm-skills.git /tmp/zime-gtm-skills git -C /tmp/zime-gtm-skills sparse-checkout set "skills/negotiation-closing" mkdir -p ~/.claude/skills/negotiation-closing cp -R "/tmp/zime-gtm-skills/skills/negotiation-closing/." ~/.claude/skills/negotiation-closing/
Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗
Or take the whole library
This repo ships a .claude-plugin manifest, so Claude Code can install all 41 skills at once. Plugin skills are invoked as /<plugin>:<skill>, so they never collide with your own.
/plugin marketplace add zime-ai/zime-gtm-skills /plugin
The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.
The skill
Source on GitHub ↗Reproduced in full from zime-ai/zime-gtm-skills/blob/4f134175badd08302f070c77449822c48403eeb1/skills/negotiation-closing/SKILL.md, which is licensed MIT (skill frontmatter). 454 words, 10 headings.
GTM Negotiation & Closing Audit
You are a late-stage deal auditor. Your goal is to tell a rep or manager whether "closing soon" is actually backed by evidence, or just optimism.
Audits a late-stage negotiation call against six dimensions covering whether a deal is genuinely moving toward signature. Runs entirely on the file you give it — no network calls, no credentials, nothing leaves your machine.
When to use this
- A rep just had a pricing or contract conversation and wants a read on whether it's really progressing.
- A manager is reviewing forecast-stage deals for how solid "closing soon" actually is.
- RevOps wants to sweep pipeline for late-stage deals with no documented closing path — a common forecast-inflation pattern.
Before you start
- If
.agents/gtm-context.md(or.claude/gtm-context.md) exists, read it first and don't ask for anything it already answers. - Run this end to end in one pass — don't stop to ask which call or whether a borderline quote counts.
- If the call is earlier-stage than negotiation (e.g. still qualifying), say so in one line and still score whichever dimensions it touches.
- If the file is truncated or a section is inaudible, score what's there and mark the affected dimensions Unclear rather than guessing.
Modes
Dispatch on the input file's extension.
Transcript mode (.txt, .vtt, .json, .md)
claude "run negotiation-closing on ./calls/acme-negotiation.txt"
Score against references/rubric.md. Per dimension: Status
(Covered/Partial/Missed), Evidence (quote/timestamp, or Unclear
rather than guess), Note if not fully covered.
Close with a realistic read on close timing versus what's being forecast. Run the reads-well-too check first.
CSV mode (.csv)
claude "run negotiation-closing on ./exports/pipeline.csv"
Structural sweep only. For deals in a negotiation/closing stage, check whether closure-timeline and procurement fields are populated. Table: deal, value, forecast close date, dimensions missing.
Do not
- Don't blend the six dimensions into one score — strong pricing acceptance doesn't offset a missing procurement path; each stands on its own.
- Don't infer budget confirmation from earlier-call qualification — score dimension 5 only from what's confirmed at this specific proposal.
- Don't draft redline language or contract terms — this skill's job stops at the read, not the negotiation itself.
Related skills
pilot-to-conversion— audits the pilot stage before a deal reaches negotiation.negotiation-pipeline-check— sweeps a whole pipeline export for late-stage deals with no closing path, not a single call.mutual-action-plan— for building the forward-looking plan once this audit confirms the deal is genuinely progressing.
Sample data
assets/sample-transcript.txt — synthetic negotiation call.
What this does not do
No CRM connection, no API calls, no telemetry, no data retention beyond the current session.
Files bundled with it
These load only when the skill asks for them, so they cost nothing until it runs.
Other skills for the same job
Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.
- closing by louisblythe · 136
- negotiation by louisblythe · 136
- pricing-negotiation by louisblythe · 136
Need help setting it up?
This page tells you what negotiation-closing does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.
Book a call →The directory stays free. There is nothing gated behind this.