General Counsel Advisor

alirezarezvani/claude-skills/c-level-advisor/general-counsel-advisor/skills/general-counsel-advisor

by alirezarezvani19392f7a08264ed00486a251f5b2098321771f94MIT27K starsListed Oct 9, 2026Updated Oct 9, 2026Repository updated 5 weeks ago

General Counsel advisory for startups: contract review (MSA, SaaS, NDA, DPA, employment), IP strategy, term sheet decoding, and regulatory landscape mapping. Use when reviewing any contract or term sheet, deciding when to engage outside counsel, defining IP strategy, evaluating regulatory exposure (HIPAA, GDPR, FDA, fintech), or when user mentions general counsel, GC, legal review, contract risk, term sheet, IP assignment, or regulatory exposure. NOT a substitute for licensed counsel — surfaces questions to bring to qualified attorneys.

Includes scriptsBusiness & Finance
AI-generated overview

Startup general counsel advisory: contract risk review, IP strategy, term sheet decoding and regulatory exposure mapping.

What it does
Provides legal frameworks for startup founders and general counsels covering contract review, IP strategy, term sheet decoding and regulatory landscape mapping. It ships two Python scripts: one scans contract text for common risky clauses, the other scores a term sheet for founder-friendliness. It also includes reference playbooks on contracts, IP and regulatory topics. Outputs are framed as questions and counter-proposals to bring to licensed counsel, not as legal advice.
When to use it
Use when reviewing contracts such as MSAs, SaaS agreements, NDAs, DPAs or employment agreements, when a term sheet arrives and needs decoding, when defining IP assignment and open source compliance, or when assessing regulatory exposure such as HIPAA, GDPR, FDA or fintech rules.
Requirements
Python runtime for the two bundled scripts (contract_risk_scanner.py, term_sheet_analyzer.py); contract text or a term sheet JSON file as input. No credentials or network access are described.

General Counsel Advisor

Strategic legal frameworks for startup General Counsels and founders without one. Contract risk, IP strategy, term sheet decoding, regulatory landscape.

This is not legal advice. It surfaces the right questions to bring to qualified outside counsel and catches the obvious traps before they reach a signature. Treat every output as a starting point for a conversation with a licensed attorney, not as a substitute for one.

Keywords

general counsel, GC, legal review, contract review, MSA, SaaS agreement, NDA, DPA, employment agreement, contractor agreement, IP assignment, invention assignment, open source license, OSS compliance, term sheet, liquidation preference, anti-dilution, option pool, vesting, acceleration, drag-along, pro-rata, board composition, regulatory, HIPAA, GDPR, CCPA, FDA, MDR, fintech, BSA/AML, money transmitter, AI Act, indemnity, liability cap, force majeure, auto-renewal, choice of law, venue, non-compete, non-solicit

Quick Start

bash
# Scan a contract for risky clauses (uses bundled sample if no path given)python scripts/contract_risk_scanner.pypython scripts/contract_risk_scanner.py path/to/contract.txt
# Analyze a term sheet for founder-friendlinesspython scripts/term_sheet_analyzer.pypython scripts/term_sheet_analyzer.py path/to/term_sheet.json

Key Questions (ask these first)

  • Who owns the IP being created or shared? (Founders forget that contractors don't auto-assign IP without a written clause.)
  • What's the liability cap, and what's carved out? (Standard: 12 months of fees, with carve-outs for IP infringement, data breach, willful misconduct.)
  • Is there a DPA in place if any personal data flows? (GDPR, CCPA, state laws — non-negotiable if EU/CA data is touched.)
  • What's the termination right, notice period, and auto-renewal trap? (5-year auto-renew with 60-day notice is a common founder mistake.)
  • Does this contract or product launch trigger a new regulatory regime? (Healthcare → HIPAA. Fintech → BSA/AML. Medical device → FDA/MDR.)
  • For term sheets: liquidation preference, pre-money option pool, anti-dilution flavor? (Three places where 5% of founder economics can quietly disappear.)

Core Responsibilities

1. Contract Review

Standard contracts a startup signs in its first 5 years:

  • Vendor MSA — Master Service Agreement (cloud, tooling, services)
  • Customer SaaS Agreement — your standard customer paper + customer redlines
  • NDA — mutual + one-way, with carve-outs for residuals + independent development
  • DPA — Data Processing Agreement (required when personal data flows)
  • Employment Agreement — offer letter, IP assignment, non-compete (where enforceable), arbitration
  • Contractor / 1099 Agreement — IP assignment is critical; misclassification risk
  • Equity Agreements — option grants, RSU agreements, advisor grants (FAST template, YC SAFE for advisors)

Run contract_risk_scanner.py on the text. It flags the 12 most common founder-killer clauses.

2. IP Strategy

  • Invention assignment — every employee and contractor signs one. No exceptions.
  • Open source license compliance — track every OSS dependency's license; AGPL and GPL trigger copyleft obligations.
  • Trade secrets — define what's protected and how (clean room dev, access controls, NDAs).
  • Patents — file provisional within 12 months of disclosure; PCT for international.
  • Trademarks — register the word mark first, design mark second; clear before launch.
  • Copyright — automatic on creation, but register for statutory damages eligibility.

See references/ip_and_regulatory.md.

3. Term Sheet Decoding

When a term sheet arrives, the difference between a founder-friendly and founder-hostile sheet often hides in three clauses:

  • Liquidation preference — 1x non-participating is standard; 1x participating or 2x is hostile
  • Pre-money vs post-money option pool — pre-money pool dilutes founders; post-money dilutes everyone proportionally
  • Anti-dilution — broad-based weighted average is standard; full ratchet is hostile

Run term_sheet_analyzer.py to get a 0-100 founder-friendliness score with flags.

4. Regulatory Landscape

When to engage outside counsel before committing:

TriggerRegimeFirst Step
Healthcare dataHIPAA, HITECH, state breach lawsSpecialist health-tech counsel
Cardholder dataPCI DSS (industry standard, not law, but contractually required)QSA + counsel
Money movementBSA/AML, state money-transmitter (50-state patchwork)Fintech specialist
Medical device claimsFDA 510(k) / De Novo / PMA, MDR (EU), ISO 13485Medical-device specialist
EU residents' personal dataGDPR + EU AI Act if AI is deployedEU privacy counsel
California residentsCCPA / CPRAPrivacy generalist
Securities (tokens, equity crowdfunding)SEC rules (Reg D, Reg A+, Reg CF)Securities counsel
Defense / aerospace customersITAR, EAR, DFARS, CMMCExport-control counsel
AI in EUEU AI Act (risk-tiered)EU privacy + product counsel
AI for hiring (NYC, CO, IL)Local bias-audit lawsEmployment counsel

See references/ip_and_regulatory.md for sequencing.

Workflows

Workflow 1: Contract Review

  1. Save the contract as plain text
  2. Run contract_risk_scanner.py path/to/contract.txt
  3. For each HIGH risk finding, draft a counter-proposal
  4. Bring the redline + counter-proposals to outside counsel
  5. Log the decision via /cs:decide

Workflow 2: Term Sheet Response

  1. Save the term sheet as a JSON file matching the schema in term_sheet_analyzer.py --help
  2. Run python scripts/term_sheet_analyzer.py path/to/term_sheet.json
  3. Review the founder-friendliness score and per-clause flags
  4. Negotiate the worst 3 clauses (don't try to win all 20)
  5. Always have a securities/venture attorney review before signing
  6. Log via /cs:decide with /cs:freeze 30 to prevent regret-driven re-opening

Workflow 3: IP Hygiene Audit

  1. Confirm every employee and contractor (past 12 months) signed invention assignment
  2. Run an OSS license inventory (pip-licenses, license-checker for npm)
  3. Map AGPL/GPL dependencies and confirm compliance (or remove)
  4. File provisional patents on novel inventions (12-month deadline from disclosure)
  5. Register word-mark trademarks for the product name

Workflow 4: Regulatory Trigger Assessment

  1. List planned product features for the next 12 months
  2. Map each feature to the trigger table in this document
  3. For any HIPAA / FDA / fintech trigger, engage a specialist counsel before building
  4. Document the regulatory roadmap and budget alongside the product roadmap
  5. Pair with cs-ciso-advisor for ISO 27001 / SOC 2 sequencing

Output Standard (when invoked via /cs:gc-review)

**Bottom Line:** [sign / negotiate / do not sign]**The Risks:** [3 highest-severity issues]**Counter-Proposals:** [specific language]**Outside Counsel Action Items:** [what to bring to the attorney]**Your Decision:** [the call only the founder can make]

Adjacent Skills

  • c-level-advisor/skills/ciso-advisor/ — Compliance overlap (SOC 2, ISO 27001, HIPAA technical safeguards)
  • c-level-advisor/skills/cfo-advisor/ — Term sheet → dilution math
  • c-level-advisor/skills/ma-playbook/ — Acquisition agreements, integration playbooks
  • ra-qm-team/ — ISO 13485, MDR, FDA 510(k), GDPR execution
  • c-level-agents/skills/gc-review/SKILL.md — /cs:gc-review slash command

References

  • contracts_playbook.md [blocked] — Standard contracts, clause checklist, common founder traps
  • ip_and_regulatory.md [blocked] — IP protection + regulatory landscape mapping
  • term_sheet_decoder.md [blocked] — Term sheet glossary + founder-friendly defaults + pushback strategies

Version: 1.0.0 Status: Production Ready Disclaimer: Not legal advice. Always engage qualified counsel for binding decisions.

Source and attribution

Source:alirezarezvani/claude-skillsinc-level-advisor/general-counsel-advisor/skills/general-counsel-advisorat commit19392f7

License: MIT

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal