general-counsel-advisor
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.
- License 许可
- MIT
- 最近更新
- 2026-06-04
- Stars
- ★ 2
- Forks
- 0
01 前言 Front Matter
- name
- general-counsel-advisor
- license
- MIT
- metadata
- { "author": "Alireza Rezvani", "domain": "general-counsel-leadership", "updated": 1778544000000, "version": "1.0.0", "category": "c-level", "frameworks": "contract-review, ip-strategy, term-sheet-decoding, regulatory-mapping", "python-tools": "contract_risk_scanner.py, term_sheet_analyzer.py" }
- description
- 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.
02 资源文件 5
- 参考文档references/contracts_playbook.md7.7 KB
- 参考文档references/ip_and_regulatory.md10.5 KB
- 参考文档references/term_sheet_decoder.md11.6 KB
- 脚本scripts/contract_risk_scanner.py16.4 KB
- 脚本scripts/term_sheet_analyzer.py16.5 KB
03 SKILL.md 正文
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
# Scan a contract for risky clauses (uses bundled sample if no path given)
python scripts/contract_risk_scanner.py
python scripts/contract_risk_scanner.py path/to/contract.txt
# Analyze a term sheet for founder-friendliness
python scripts/term_sheet_analyzer.py
python 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:
| Trigger | Regime | First Step |
|---|---|---|
| Healthcare data | HIPAA, HITECH, state breach laws | Specialist health-tech counsel |
| Cardholder data | PCI DSS (industry standard, not law, but contractually required) | QSA + counsel |
| Money movement | BSA/AML, state money-transmitter (50-state patchwork) | Fintech specialist |
| Medical device claims | FDA 510(k) / De Novo / PMA, MDR (EU), ISO 13485 | Medical-device specialist |
| EU residents' personal data | GDPR + EU AI Act if AI is deployed | EU privacy counsel |
| California residents | CCPA / CPRA | Privacy generalist |
| Securities (tokens, equity crowdfunding) | SEC rules (Reg D, Reg A+, Reg CF) | Securities counsel |
| Defense / aerospace customers | ITAR, EAR, DFARS, CMMC | Export-control counsel |
| AI in EU | EU AI Act (risk-tiered) | EU privacy + product counsel |
| AI for hiring (NYC, CO, IL) | Local bias-audit laws | Employment counsel |
See references/ip_and_regulatory.md for sequencing.
Workflows
Workflow 1: Contract Review
- Save the contract as plain text
- Run
contract_risk_scanner.py path/to/contract.txt - For each HIGH risk finding, draft a counter-proposal
- Bring the redline + counter-proposals to outside counsel
- Log the decision via
/cs:decide
Workflow 2: Term Sheet Response
- Save the term sheet as a JSON file matching the schema in
term_sheet_analyzer.py --help - Run
python scripts/term_sheet_analyzer.py path/to/term_sheet.json - Review the founder-friendliness score and per-clause flags
- Negotiate the worst 3 clauses (don't try to win all 20)
- Always have a securities/venture attorney review before signing
- Log via
/cs:decidewith/cs:freeze 30to prevent regret-driven re-opening
Workflow 3: IP Hygiene Audit
- Confirm every employee and contractor (past 12 months) signed invention assignment
- Run an OSS license inventory (
pip-licenses,license-checkerfor npm) - Map AGPL/GPL dependencies and confirm compliance (or remove)
- File provisional patents on novel inventions (12-month deadline from disclosure)
- Register word-mark trademarks for the product name
Workflow 4: Regulatory Trigger Assessment
- List planned product features for the next 12 months
- Map each feature to the trigger table in this document
- For any HIPAA / FDA / fintech trigger, engage a specialist counsel before building
- Document the regulatory roadmap and budget alongside the product roadmap
- Pair with
cs-ciso-advisorfor 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
../ciso-advisor/— Compliance overlap (SOC 2, ISO 27001, HIPAA technical safeguards)../cfo-advisor/— Term sheet → dilution math../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-reviewslash command
References
- contracts_playbook.md — Standard contracts, clause checklist, common founder traps
- ip_and_regulatory.md — IP protection + regulatory landscape mapping
- term_sheet_decoder.md — 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.
04 同仓库更多 Skills
syllabus
Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Triggers whenever a user uploads a syllabus, course outline, or curriculum document and wants supplementary readings. Also triggers on: 'syllabus reading list', 'find papers for my course', 'create a reading list from this syllabus', 'recent research for my class', 'supplementary readings', 'find journal articles for these topics', 'what recent papers cover this material', 'any new research on these course topics', 'update my syllabus with recent papers'. Even casual mentions when a syllabus is attached should trigger this skill.
research
Default entry point for any research request — a hybrid router that classifies the question deterministically and either delegates to a specialist research skill (pulse for trends/sentiment, grants for NIH funding, litreview for academic literature, syllabus for course reading, patent for prior-art + IP landscape, dossier for entity research) or runs its own plan-decompose-multi-source-search-synthesize-cite fallback workflow when no specialist matches. Always surfaces the routing decision so users can override. Triggers — "research [topic]", "look into [topic]", "what do we know about [topic]", "investigate [topic]", "find me information on [topic]", "do some research on [topic]", "I need to understand [topic]", or any research request that doesn't obviously match a more-specific specialist skill. Output is a markdown briefing (default) or .docx document (on request) with full citations and an audit log.
pulse
Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X/Twitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend/sentiment/problems/opportunities/comparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Triggers: 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]', or any variation requesting multi-source recency intelligence on a topic. Also use for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.
patent
Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search / freedom-to-operate / competitive landscape / acquisition diligence / litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Triggers: 'prior art search for [invention]', 'patent search on [topic]', 'freedom to operate analysis', 'FTO for [product]', 'patent landscape for [field]', 'is [invention] novel', 'patents on [topic]', 'competitive patent analysis', 'prior art for litigation', 'patent diligence on [company]'. Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.
notebooklm
Browser automation skill for controlling Google's NotebookLM. Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio Overview, infographics, slide decks, study guides, briefing docs, mind maps, timelines, FAQs), and creating new notebooks. Triggers on any phrase involving NotebookLM — 'open NotebookLM', 'check my [name] notebook', 'pull info from NotebookLM', 'ask my notebook about X', 'add [source] to NotebookLM', 'create an infographic in NotebookLM', 'use NotebookLM Studio', 'generate a slide deck from my notebook', or any variation where the goal involves NotebookLM. Requires browser automation environment — fails gracefully when unavailable.
litreview
Academic literature orientation skill that searches papers via Consensus, builds a strategic search plan using PICO (default) or SPIDER / Decomposition / hybrid as fallbacks, and synthesizes findings into a professionally formatted Word document (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5/10/20 queries) controls coverage vs. speed. Output is a 'launching pad' — not a finished review, but an orientation guide that lets a researcher dive in confidently. Triggers: 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'. Do NOT trigger for single one-off paper searches where the user just wants a quick list — that's a plain Consensus search.