Contract Review
evolsb/claude-legal-skill
Review legal contracts, NDAs, employment agreements, SaaS terms, and M&A documents.
Review a vendor/SaaS contract against a practical checklist before you sign.
Install Vendor Contract Checklist
$ npx skills add mohitagw15856/pm-claude-skills --skill vendor-contract-checklist -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills vendor-contract-checklist --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/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/vendor-contract-checklist .claude/skills/vendor-contract-checklist && 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 "vendor-contract-checklist" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/vendor-contract-checklist into .claude/skills/vendor-contract-checklist/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vendor-contract-checklist", 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/mohitagw15856/pm-claude-skills/tree/main/skills/vendor-contract-checklistType 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 mohitagw15856/pm-claude-skills --skill vendor-contract-checklist -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills vendor-contract-checklist --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/vendor-contract-checklist .agents/skills/vendor-contract-checklist && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "vendor-contract-checklist" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/vendor-contract-checklist into .agents/skills/vendor-contract-checklist/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vendor-contract-checklist", 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 mohitagw15856/pm-claude-skills --skill vendor-contract-checklist -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills vendor-contract-checklist --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/vendor-contract-checklist .cursor/skills/vendor-contract-checklist && 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 "vendor-contract-checklist" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/vendor-contract-checklist into .cursor/skills/vendor-contract-checklist/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vendor-contract-checklist", 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/mohitagw15856/pm-claude-skills.git --path skills/vendor-contract-checklist--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 mohitagw15856/pm-claude-skills --skill vendor-contract-checklist -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills vendor-contract-checklist --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/vendor-contract-checklist .gemini/skills/vendor-contract-checklist && 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 "vendor-contract-checklist" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/vendor-contract-checklist into .gemini/skills/vendor-contract-checklist/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vendor-contract-checklist", 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 mohitagw15856/pm-claude-skills vendor-contract-checklistInstalls 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 mohitagw15856/pm-claude-skills --skill vendor-contract-checklist -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/vendor-contract-checklist .github/skills/vendor-contract-checklist && 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 "vendor-contract-checklist" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/vendor-contract-checklist into .github/skills/vendor-contract-checklist/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vendor-contract-checklist", 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 mohitagw15856/pm-claude-skills --skill vendor-contract-checklist -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mohitagw15856/pm-claude-skills vendor-contract-checklist --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/vendor-contract-checklist .opencode/skills/vendor-contract-checklist && 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 "vendor-contract-checklist" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/vendor-contract-checklist into .opencode/skills/vendor-contract-checklist/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vendor-contract-checklist", 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.
Facts
- Skill name
vendor-contract-checklist- GitHub stars
- 1.4k
- Token cost
- ~1k tokens
- SKILL.md length
- 510 words
- Files
- 1
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
Review a vendor/SaaS contract against a practical checklist before you sign.
- Asked to review a vendor contract
- SKILL.md covers Working from a brief, Required Inputs, Output Format and Quality Checks, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Check a SaaS/MSA/subscription agreement
What it does
Vendor Contract Checklist is an agent skill from mohitagw15856/pm-claude-skills. Review a vendor/SaaS contract against a practical checklist before you sign. Use when asked to review a vendor contract, check a SaaS/MSA/subscription agreement, flag risky terms, or prepare negotiation points before signing. Produces a structured review — key terms extracted, a risk-flagged checklist (commercial, legal, security, exit), questions to ask, and prioritised negotiation points. Not legal advice.
Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Legal & Compliance, covering Contract review. The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.
When your agent uses it
- Asked to review a vendor contract
- Check a SaaS/MSA/subscription agreement
- Flag risky terms
- Prepare negotiation points before signing
Example prompts
- “/vendor-contract-checklist”
What it can do on your machine
Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.
Tool permissions
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.
Runs code
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.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Vendor Contract Checklist loads about 1k tokens when it runs. Until then it costs about 109 tokens; SKILL.md has 510 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.
Safety
Auto-check passed
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.
SKILL.md
The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 510 words, ~1,046 tokens.
Download SKILL.mdSave it as
.claude/skills/vendor-contract-checklist/SKILL.md (or your agent's skills folder).- name
- vendor-contract-checklist
- description
- Review a vendor/SaaS contract against a practical checklist before you sign. Use when asked to review a vendor contract, check a SaaS/MSA/subscription agreement, flag risky terms, or prepare negotiation points before signing. Produces a structured review — key terms extracted, a risk-flagged checklist (commercial, legal, security, exit), questions to ask, and prioritised negotiation points. Not legal advice.
Vendor Contract Checklist Skill
Most bad vendor deals are lost in the terms nobody read: auto-renewal, price escalators, weak SLAs, no exit, vague data rights. This skill reviews a contract against a practical checklist, extracts the terms that actually bite, flags the risks, and turns them into specific questions and negotiation points — so you sign with your eyes open.
Note: this is a practical review aid, not legal advice. For material commitments, high spend, or anything regulated, have it reviewed by qualified counsel. Flag, don't rule on, legal questions.
Working from a brief
Given a contract (or a description of one), produce the full review anyway — extract what's present, and for standard terms that are missing or unstated, flag them as gaps to confirm rather than assuming they're fine. Never withhold the review for an incomplete document; mark what couldn't be assessed.
Required Inputs
Ask for these only if they aren't already provided (else mark as "not found — confirm"):
- The contract — the agreement text (MSA, order form, SaaS terms, DPA), or its key terms.
- The deal — what you're buying, the spend, and the term length.
- What matters to you — must-haves (uptime, data residency, exit), and any internal/legal/security requirements.
Output Format
Vendor Contract Review: [vendor]
1. Key terms at a glance — extracted: parties, term & renewal, total cost & escalators, payment terms, SLA, liability cap, termination, data/IP, governing law.
2. Risk-flagged checklist — by area, each marked ✅ ok / ⚠️ review / ❌ problem / ❓ not found:
| Area | Item | Status | Note |
|---|---|---|---|
| Commercial | auto-renewal & notice period | ⚠️ | 60-day notice, auto-renews 12 mo — calendar it |
| Commercial | price increase cap | ❓ | not capped — negotiate a cap |
| Legal | liability cap vs. fees | ⚠️ | capped at 3 months' fees — low for the risk |
| Security/data | data deletion & portability on exit | ❌ | not addressed — add |
| SLA | uptime + remedy (credits) | ⚠️ | 99.5%, credits only — check fit |
| Exit | termination for convenience | ❓ | not present — request |
3. Questions to ask the vendor — the specific clarifications before signing.
4. Negotiation points — prioritised, with a suggested ask for each (what "good" looks like): the few terms worth pushing on, and the rationale.
5. Sign-off note — what's fine, what needs negotiation, and what to send to legal.
Show full SKILL.md (161 more words)Show less
Quality Checks
- Auto-renewal, notice period, and price-escalation terms are surfaced explicitly (the usual traps)
- SLA is assessed with its remedy, not just the uptime number
- Data handling on exit (deletion, portability) and liability cap vs. spend are checked
- Missing standard protections are flagged as gaps, not assumed present
- Negotiation points are prioritised with a concrete suggested ask each
- It flags legal questions for counsel rather than ruling on them
Anti-Patterns
- Do not skim only the order form — the MSA/terms is where the risk lives
- Do not ignore auto-renewal and notice windows — they quietly lock you in
- Do not accept an SLA without checking the remedy (credits ≠ reliability)
- Do not present this as legal advice — flag material/legal items for counsel
- Do not produce a flat list — prioritise what's actually worth negotiating
Based On
Procurement and vendor-risk practice — key-term extraction, risk-flagged review across commercial/legal/security/exit, and prioritised negotiation.
Example Trigger Phrases
- "Review a vendor contract."
- "Check a SaaS/MSA/subscription agreement."
- "Prepare negotiation points before signing."
© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/vendor-contract-checklist of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Vendor Contract Checklist 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 |
|---|---|---|---|---|---|---|
| Vendor Contract Checklist this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~1k | Automated safety check: Pass | MIT | |
| Contract Reviewevolsb/claude-legal-skill | 464 | 1 repos | ~3.6k | Automated safety check: Pass | MIT | |
| Commercial Legal Plapiotrowski-afk/commercial-legal-pl | 176 | 1 repos | ~4.1k | Automated safety check: Pass | Apache-2.0 | |
| Hand Drawnthreerocks/hand-drawn-styles | 2.2k | — | ~398 | Automated safety check: Pass | MIT | |
| Tabular Document Reviewanthropics/claude-for-legal | 9.6k | 3 repos | ~4.3k | Automated safety check: Pass | Apache-2.0 | |
| Tw Formal WritingImbad0202/tw-formal-writing | 179 | — | ~1k | Automated safety check: Pass | MIT |
Similar skills
Commercial Legal Pl
apiotrowski-afk/commercial-legal-pl
Skill do analizy i tworzenia umów według polskiego prawa, ze szczególnym uwzględnieniem umów B2B, IP i IT (body leasing, NDA, wdrożenia, SaaS, przeniesienie praw autorskich, ugody).
Hand Drawn
threerocks/hand-drawn-styles
A skill your agent uses when users ask for a hand-drawn or illustrated image prompt, name one of the repository's 20 numbered styles or the 3.1 stable variant, or mention triggers such as…
- Official
Tabular Document Review
anthropics/claude-for-legal
Builds a review grid with one row per document and one column per data point, each cell cited to a verbatim quote, built for M&A diligence and other batch reviews.
Tw Formal Writing
Imbad0202/tw-formal-writing
台灣正式文件撰寫助手 — 涵蓋政府公文、政府機關其他文件、法律文件、人民對政府文書四類中文正式文件的撰寫（不含學術論文、商業文書、私人書信等，見下方排除清單）。
Contract Review Pro
CSlawyer1985/contract-review-pro
专业合同审核 Skill：7步工作流（含立场声明、框架审阅、类型路由）、5类通用门禁+16个专项门禁、终稿三件套+HTML可视化报告、8维度风险评分、修订5分类路由。完全自包含，零外部依赖。
More from mohitagw15856/pm-claude-skills
All 1,348 skills in this repoCar Tco
mohitagw15856/pm-claude-skills
Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…
Cs Health Scorecard
mohitagw15856/pm-claude-skills
Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.
Exit Waterfall
mohitagw15856/pm-claude-skills
Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.
Feature Prioritisation
mohitagw15856/pm-claude-skills
Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.
Fire Number
mohitagw15856/pm-claude-skills
Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.
Freelance Rate
mohitagw15856/pm-claude-skills
Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.
Related
Categories
Questions about Vendor Contract Checklist
What does Vendor Contract Checklist do?
Review a vendor/SaaS contract against a practical checklist before you sign. Vendor Contract Checklist is an agent skill from mohitagw15856/pm-claude-skills. Review a vendor/SaaS contract against a practical checklist before you sign.
When should I use Vendor Contract Checklist?
Vendor Contract Checklist fits situations like: asked to review a vendor contract; check a SaaS/MSA/subscription agreement; flag risky terms; prepare negotiation points before signing.
How do I install Vendor Contract Checklist in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill vendor-contract-checklist -a claude-code`. Or copy the skill folder (skills/vendor-contract-checklist in mohitagw15856/pm-claude-skills) into .claude/skills/vendor-contract-checklist in your project. Claude Code loads it when a task matches its description.
How do I install Vendor Contract Checklist in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill vendor-contract-checklist -a codex`. Or copy the skill folder (skills/vendor-contract-checklist in mohitagw15856/pm-claude-skills) into .agents/skills/vendor-contract-checklist in your project. Codex loads it when a task matches its description.
Can I use Vendor Contract Checklist in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill vendor-contract-checklist -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/vendor-contract-checklist, .gemini/skills/vendor-contract-checklist, .github/skills/vendor-contract-checklist and .opencode/skills/vendor-contract-checklist in your project.
What does Vendor Contract Checklist need to run?
SKILL.md names no scripts, command-line tools or credentials: Vendor Contract Checklist is instructions for the agent only.
Does Vendor Contract Checklist access the network?
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.
Is Vendor Contract Checklist safe to install?
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.
What licence does Vendor Contract Checklist use?
Vendor Contract Checklist is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Vendor Contract Checklist use?
About 1k tokens (SKILL.md is roughly 4.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Vendor Contract Checklist?
Skills that share tags, products or a category with Vendor Contract Checklist: Contract Review (evolsb/claude-legal-skill, 464 stars), Commercial Legal Pl (apiotrowski-afk/commercial-legal-pl, 176 stars), Hand Drawn (threerocks/hand-drawn-styles, 2.2k stars) and Tabular Document Review (anthropics/claude-for-legal, 9.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Vendor Contract Checklist?
mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.
Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.