CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

64

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is general-counsel-advisor in alirezarezvani/claude-skills

SKILL.md
Quality
Evals
Security

Quality

Content

60%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, largely actionable body with concrete commands, useful clause defaults, and a strong regulatory trigger table. Its two real weaknesses are that every referenced bundle file is missing from the bundle (breaking both progressive disclosure and the runnable Quick Start), and avoidable token spend on a redundant Keywords section and textbook legal explanations.

Suggestions

Bundle the cited files: add scripts/contract_risk_scanner.py, scripts/term_sheet_analyzer.py, and the three references/*.md files (contracts_playbook.md, ip_and_regulatory.md, term_sheet_decoder.md) — or remove the citations — since every script command and reference link currently dead-ends.

Delete the Keywords section: the ~40 trigger terms already live in the frontmatter description, so the body copy adds tokens without runtime value.

Add feedback loops to the workflows, e.g., re-run contract_risk_scanner.py on the redlined contract to confirm HIGH findings are resolved before sending to outside counsel.

DimensionReasoningScore

Conciseness

Mostly efficient — the regulatory trigger table and clause defaults ('1x non-participating is standard; 1x participating or 2x is hostile') earn their tokens — but the ~40-term Keywords section duplicates the frontmatter description's triggers, and lines like 'Copyright — automatic on creation, but register for statutory damages eligibility' restate standard legal knowledge Claude already has.

3 / 5

Actionability

Provides concrete, mostly executable guidance: copy-paste commands ('python scripts/contract_risk_scanner.py path/to/contract.txt'), specific thresholds ('negotiate the worst 3 clauses', liability cap of '12 months of fees'), and a defined output template. Minor gaps: the term-sheet input schema is deferred to '--help' and '/cs:decide' / '/cs:gc-review' are defined in other skills.

4 / 5

Workflow Clarity

Four workflows with clearly sequenced numbered steps and some checkpoints (scanner HIGH-risk findings drive counter-proposals; 'Always have a securities/venture attorney review before signing'). Falls short of anchor 5 because there is no validate-fix-retry feedback loop — e.g., the scanner is never re-run on the redlined contract to confirm the HIGH findings are resolved.

4 / 5

Progressive Disclosure

References are well-signaled and one level deep ('See references/ip_and_regulatory.md', a References section with linked, annotated files), but none of the referenced files exist — the bundle contains no references/, scripts/, or assets/ directories. Every 'See references/...' link and both Quick Start scripts (contract_risk_scanner.py, term_sheet_analyzer.py) dead-end, so navigation to the detailed material is impossible despite the good structural design.

2 / 5

Total

13

/

20

Passed

Description

96%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

An exemplary description: concrete capabilities with enumerated contract types, an explicit 'Use when' clause rich in natural trigger phrases including the GC abbreviation, and a responsible boundary statement. Only minor overlap risk with adjacent privacy/compliance skills on regulatory triggers.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities with type-level enumeration: 'contract review (MSA, SaaS, NDA, DPA, employment)', 'IP strategy, term sheet decoding, and regulatory landscape mapping', plus the meta-capability of deciding 'when to engage outside counsel'. Coverage is comprehensive for the GC domain with no notable gaps, matching the anchor-5 example's breadth.

5 / 5

Completeness

Clearly answers both questions: the 'what' is the enumerated capability list ('General Counsel advisory for startups: contract review... IP strategy, term sheet decoding, and regulatory landscape mapping') and the 'when' is an explicit 'Use when...' clause with concrete trigger phrases. Also adds a useful boundary ('NOT a substitute for licensed counsel').

5 / 5

Trigger Term Quality

Explicit natural triggers: 'Use when reviewing any contract or term sheet' and 'when user mentions general counsel, GC, legal review, contract risk, term sheet, IP assignment, or regulatory exposure'. Includes the abbreviation synonym pair (general counsel / GC) and named regimes (HIPAA, GDPR, FDA, fintech), giving comprehensive natural-term coverage.

5 / 5

Distinctiveness Conflict Risk

'General Counsel advisory for startups' carves a clear niche with distinctive triggers (GC, term sheet, IP assignment), but 'evaluating regulatory exposure (HIPAA, GDPR, FDA, fintech)' overlaps with what a privacy or compliance skill would also claim. Mostly distinct with minor overlap risk from adjacent compliance skills.

4 / 5

Total

19

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 3 missing

Warning

referenced_paths_exist

Referenced path issues: 10 missing

Warning

Total

14

/

16

Passed

Repository
alirezarezvani/claude-skills
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.