Skip to content

Guide · Agent skill

How to use the GC Review Contract Checklist agent skill

Updated · written with AI from the project's own documentation and checked against our catalogue data

The gc-review skill is a checklist and report template that makes your Claude agent review a contract, term sheet, equity grant or similar document through six General Counsel style questions. It is built for founders and small teams who want to arrive at a lawyer's office with a structured list of issues rather than a stack of unread pages. After this guide you will know how to install it, how to ask for a review in plain language, what the report contains, and where the skill's limits are.

GC Review Contract Checklistalirezarezvani/claude-skills · MIT

Quick start

  1. 1Get the skill files. Download the gc-review ZIP from this page and unzip it on your machine.
  2. 2Place the skill folder. Move it into ~/.claude/skills/ for all projects, or into the project's .claude/skills/ folder for one project.
  3. 3Or upload in the Claude apps. In the Claude apps, open Settings → Capabilities → Skills and upload the ZIP.
  4. 4Make sure the plugin is available. The source says the command requires a Claude Code environment with the c-level-agents plugin installed.
  5. 5Ask for a review. Describe the document, counterparty and what you are worried about, or run /c-level-agents:gc-review with a plan name.
  6. 6Read the risk table. Check each issue's risk rating and recommendation, starting with HIGH items.
  7. 7Take the action items to counsel. Bring the outside counsel checklist to a qualified lawyer before any binding decision.

What the gc-review skill makes the agent do

When the skill is active, the agent works through six questions before anything is signed: who owns the IP, what the liability cap and carve-outs are, whether personal data needs a data processing agreement, how termination and auto-renewal work, whether new regulations apply, and how employment and equity are handled.

The output is a structured report with a risk table, a list of items for outside counsel, and a verdict of red, yellow or green. The skill is explicit that it is not legal advice; its purpose is to surface the right questions to ask before you talk to a qualified lawyer.

  • Document type, counterparty and value or scope are recorded at the top of the report.
  • Each issue gets a risk rating and a recommendation in a table.
  • A regulatory trigger section says whether a new regime applies and names frameworks such as HIPAA, GDPR or CCPA where relevant.
  • Verdicts are SIGN AS-IS (rare), NEGOTIATE (counter on the top three issues) or DO NOT SIGN (material risk).

Install the gc-review skill

Download the ZIP from this page and unzip it. To make the skill available to every project on your machine, unzip it into ~/.claude/skills/. To limit it to one project, unzip it into that project's .claude/skills/ folder.

If you use the Claude apps instead of Claude Code, you can upload the skill under Settings → Capabilities → Skills. The skill package contains a single file, SKILL.md, which holds the instructions the agent follows.

The source notes that the command runs inside a Claude Code environment with the c-level-agents plugin installed.

  • Personal install: ~/.claude/skills/
  • Project install: .claude/skills/ inside the project folder
  • Claude apps: Settings → Capabilities → Skills, then upload the ZIP

Trigger the skill with natural requests

The skill description says to use it when reviewing a term sheet before signing, redlining a customer MSA, or checking IP assignment and regulatory exposure on a new product. You can also invoke it directly with the command /c-level-agents:gc-review followed by a plan or document name.

Be specific about the document and what you want. Naming the counterparty, the deal value and the term length helps the agent fill in the report's document section accurately.

  • "Review this term sheet before I sign. Run the GC checklist and tell me the top three issues for my lawyer."
  • "Redline check on this customer MSA: liability cap, carve-outs, auto-renewal and data processing."
  • "We are launching a new product that stores patient data. Check regulatory exposure and list questions for outside counsel."
/c-level-agents:gc-review <plan>

What to give the agent as input

The skill works on the contract or term sheet you provide. The source says the optional Python scripts take a contract as a text file or a term sheet as a JSON file. The rest of the review is done by the agent reading the document.

The source's "when to run" list includes contracts over $100K or over one year, equity grants, term sheet responses, entry into regulated markets, open-source licence decisions in core IP, and M&A letters of intent.

  • Read the full document, not just the summary page, before running the review.
  • Include any linked order forms or data processing terms if they affect the answers.

Optional scripts: what they do and what they need

The source describes two optional Python tools inside the general-counsel-advisor skill: an automated contract scan that checks for 12 founder-risk patterns, and a term sheet analyzer that scores founder-friendliness from 0 to 100. Both are run with Python against your files.

The gc-review skill itself is listed as running no scripts and making no network calls. Only the optional scripts need Python and the contract or term sheet files.

  • Scripts run: no for the gc-review skill itself
  • Network use: no
  • Optional scripts need Python and your contract or term sheet files as input
python ${CLAUDE_PLUGIN_ROOT}/vendor/c-level-advisor/general-counsel-advisor/scripts/contract_risk_scanner.py path/to/contract.txt

Read the report and act on it

Work through the report top to bottom. Start with the HIGH rated issues in the risk table, then the outside counsel action items, which are written as a checklist you can bring to a lawyer. The regulatory trigger section tells you which frameworks to ask about.

Treat the verdict as a negotiating position, not a decision. The skill suggests logging the verdict with /c-level-agents:decide after outside counsel review.

  • Take the top three issues into the negotiation.
  • Give the action items to your lawyer as the scope of a paid review.
  • Record the final decision after counsel has responded.

What people use it for

  • Reviewing a term sheet before a founder responds to investors.
  • Redlining a customer master services agreement and flagging an uncapped indemnity or a 5-year auto-renew clause.
  • Checking IP assignment in place for employees and contractors before launching a product.
  • Checking whether a new product that handles personal data needs a data processing agreement.
  • Preparing a list of specific questions for a paid legal review.

Frequently asked questions

Is the gc-review skill free to use?

The source does not state a price or licence terms for the Claude apps or Claude Code. The skill's own listing shows an MIT licence for the repository. Check the repository's licence file and your Claude plan for any costs.

What do I need to install gc-review?

The source says you need a Claude Code environment with the c-level-agents plugin installed. You also need to unzip the skill into ~/.claude/skills/ or a project's .claude/skills/ folder, or upload it in the Claude apps. Python and your contract files are needed only for the optional scripts.

Does gc-review give legal advice?

No. The skill states it is not legal advice and is meant to surface questions to ask before talking to outside counsel. It says to engage a qualified lawyer for binding decisions.

Can gc-review replace a lawyer?

No. The source says the verdicts can miss jurisdiction-specific issues and that regulated industries such as healthcare, fintech and medical devices need expert interpretation of frameworks like HIPAA, FDA and BSA/AML.

Does gc-review use the internet or run scripts?

The source lists the skill as running no scripts and using no network. Only the optional contract_risk_scanner and term_sheet_analyzer Python tools need Python and your files.

Why does gc-review flag a 12-month liability cap if that is a common number?

The skill lists a 12-month cap as a standard reference point, but the source warns against treating default numbers like a 12-month cap or 4-year vesting as market standard without checking the actual deal. Use the review to test the real terms against your situation.

New agent skills, repos and AI tools — every week

The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.

Our verdict

The gc-review skill suits founders and teams who want a consistent, structured checklist before a term sheet or customer contract goes to a lawyer. It is less suitable for anyone who expects a final legal decision, or for regulated businesses in healthcare, fintech or medical devices that need expert interpretation of the frameworks it names.

Download the skill