Review contract

Skill nota-america/forgecat-agent-profiles/profiles/anthropics/knowledge-work-plugins/anthropics_knowledge-work-plugins_small-business/for-forgecat/skills/review-contract

Reviews a contract in plain English, surfaces red flags with severity ratings, and produces a marked-up docx/PDF with suggested redlines. Accepts optional file path or DocuSign envelope ID.From its SKILL.md

Install

npx -y skills add nota-america/forgecat-agent-profiles --skill review-contract

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

SKILL.md

2.8 KB, 603 tokens by cl100k_base, as published. Nobody here has run it

Run the contract review. Read the document, explain what it says, flag anything risky, and produce marked-up redlines for the owner to use in negotiations.

Parse arguments:

FILE_PATH_OR_DOCUSIGN_ENVELOPE_ID — path to a local PDF/docx file, or a DocuSign envelope ID; if omitted, check the most recent envelope awaiting signature in DocuSign

Step 1 — Load the contract

Using the contract-review skill workflow:

If a file path is given: read the document from Files or Desktop.
If a DocuSign envelope ID is given: pull the document from DocuSign.
If neither: check DocuSign for the most recent envelope with status waiting for signature and confirm with the owner before proceeding.

Step 2 — Plain-English summary

Produce a 3-paragraph summary:

What this contract does — the deal in plain terms (who, what, how much, how long)
Key obligations — what the owner must do and when
Key rights — what the owner gets and any termination or exit paths

Step 3 — Red-flag list

For each risk, rate severity: 🔴 High / 🟡 Medium / 🟢 Low

Flag at minimum:

Auto-renewal clauses with short cancellation windows
Unilateral price change rights
Broad IP ownership transfers
Unlimited liability or missing liability cap
Exclusivity clauses
Non-compete or non-solicit provisions
Ambiguous payment or deliverable terms

Format each flag as:

{Severity} {Clause name} — {what it says in plain English} — Suggested redline: {fix}

Step 4 — Marked-up redlines

Generate a list of specific redline suggestions in legal markup format:

§{section}: DELETE "[original language]" / INSERT "[suggested replacement]"
Reason: {one sentence}

Offer to export this as a marked-up docx or PDF to Files or Desktop.

Connector failures

If DocuSign is not connected and no file path was given, ask the owner to upload the contract as a PDF or docx. If DocuSign is connected but the envelope ID is invalid, report the error and ask the owner to check the ID. This command works fully offline with a local file — connectors are optional.

Approval gates

Never sign, send, or modify the actual DocuSign envelope. Present the review and wait for the owner to act.
Always caveat: "This is not legal advice. Review with your attorney before signing."
Never delete or overwrite the original document.

Output

Present the plain-English summary, red-flag list, and redline suggestions. Ask the owner whether to export a marked-up copy and where to save it.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most review quality skills give in 603 tokens

Counted across 1,273 of the 2,403 authors here whose files we hold, read 2026-09-06

Ask one question at a timein 63 of 1273, across 62 files
Provide a recommended answer for each questionin 47 of 1273, across 45 files
Rank findings by severityin 44 of 1273
Use parameterized queries for database accessin 38 of 1273, across 20 files
Validate all user input with schemasin 33 of 1273, across 15 files
Store secrets in environment variablesin 32 of 1273, across 14 files
Explore the codebase to answer questionsin 31 of 1273, across 29 files
Store tokens in httpOnly cookiesin 30 of 1273, across 12 files
Implement rate limiting on API endpointsin 30 of 1273, across 12 files
Sanitize user-provided HTMLin 29 of 1273, across 11 files
Return generic error messages to usersin 28 of 1273, across 10 files
Cite file and line for every findingin 28 of 1273, across 25 files

Said here and by no other author read

Summarize the contract in three paragraphs
Suggest specific redline language for risks
Include a legal disclaimer with the review
Ask the owner to export the marked-up document

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.