agentsclimarketplace

Contract analyzer

Skill bg-szy/TOP-SKILLS/skills/claude-skills/contract-analyzer

Review contracts for concerning clauses, extract key terms, compare to standard terms, and flag unusual provisions. Use when user needs contract review, legal document analysis, or agreement evaluation.From its SKILL.md

Install
npx -y skills add bg-szy/TOP-SKILLS --skill contract-analyzer

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

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.9 KB, 333 tokens by cl100k_base, as published. Nobody here has run it

Contract Analyzer

Review contracts to surface risks, key terms, and unusual provisions, then recommend negotiation actions.

Contents

  • references/key-terms.md -- full checklist of terms to extract by category
  • references/risk-flags.md -- red/yellow flags, standards comparison, commonly missing clauses
  • references/output-template.md -- the full analysis report format
  • references/examples.md -- worked examples and best practices

Workflow

  1. Include this disclaimer in every output: "Legal Disclaimer: This is informational analysis only, not legal advice. Always consult with a qualified attorney for legal matters. Contract interpretation can be complex and jurisdiction-specific."
  2. Identify the contract type (employment, independent contractor/freelance, NDA, service, partnership, software license, real estate, purchase).
  3. Extract key terms across financial, duration/termination, intellectual property, liability/indemnification, and other critical categories. See references/key-terms.md.
  4. Flag concerning clauses as red flags (high risk) or yellow flags (review carefully). See references/risk-flags.md.
  5. Compare terms to industry standards: note deviations, one-sided provisions, and missing standard protections. See references/risk-flags.md.
  6. Assess balance: determine whether obligations, penalties, and protections are reciprocal or favor one party.
  7. Provide actionable recommendations: specific clauses to negotiate, alternative language, questions to ask, terms to add, and deal-breakers.
  8. Format the report per references/output-template.md. For worked examples and best practices, see references/examples.md.

What ships with it

Read from the repository

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

Gives 0 of the 12 instructions most legal skills give in 333 tokens

Counted across 234 of the 234 authors here whose files we hold, read 2026-08-07

  • Use text operators for text fieldsin 11 of 234, across 6 files
  • Consult qualified counsel before usein 11 of 234, across 3 files
  • Use PatentSearch API for patent searchesin 10 of 234, across 5 files
  • Confirm jurisdiction, employment type, and required clausesin 9 of 234, across 2 files
  • Choose a document template and tailor role-specific termsin 9 of 234, across 2 files
  • Validate compensation, benefits, and compliance requirementsin 9 of 234, across 2 files
  • Add signature, confidentiality, and IP assignment terms as neededin 9 of 234, across 2 files
  • Open the implementation playbook for detailed templatesin 9 of 234, across 2 files
  • Use TSDR for trademark data retrievalin 9 of 234, across 4 files
  • Ask for clarification if required inputs are missingin 8 of 234, across 2 files
  • Set the USPTO_API_KEY environment variablein 8 of 234, across 3 files
  • Use the uspto-opendata-python library for PEDSin 8 of 234, across 3 files

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.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.