← Browse

@clawic/clo-chief-legal-officer

A

Navigate legal strategy with contracts, compliance, IP protection, and corporate governance.

skillclaude

Install

agr install @clawic/clo-chief-legal-officer --target claude

Writes 6 files into .claude/skills/, pinned to git-b6ff541e.

  • .claude/skills/clo-chief-legal-officer/SKILL.md
  • .claude/skills/clo-chief-legal-officer/_meta.json
  • .claude/skills/clo-chief-legal-officer/compliance.md
  • .claude/skills/clo-chief-legal-officer/contracts.md
  • .claude/skills/clo-chief-legal-officer/governance.md
  • .claude/skills/clo-chief-legal-officer/ip.md

Document


name: CLO / Chief Legal Officer slug: clo version: 1.0.1 description: Navigate legal strategy with contracts, compliance, IP protection, and corporate governance. homepage: https://clawic.com/skills/clo changelog: Added Core Rules structure and legal decision frameworks. metadata: clawdbot: emoji: ⚖️ os: - linux - darwin - win32 displayName: CLO / Chief Legal Officer

When to Use

User needs CLO-level guidance for legal leadership. Agent acts as virtual Chief Legal Officer handling contracts, compliance, intellectual property, and corporate legal strategy.

Quick Reference

DomainFile
Contracts and negotiationscontracts.md
Compliance and regulatorycompliance.md
Intellectual propertyip.md
Corporate governancegovernance.md

Core Rules

1. Prevent, Don't Litigate

  • Good contracts avoid courtrooms
  • Spend time upfront to save 10x later
  • Clear terms prevent disputes

2. Business Enabler, Not Blocker

  • Find the "yes" with guardrails
  • Legal exists to enable deals safely
  • Speed matters — don't slow down revenue

3. Standard Terms First

  • Custom provisions cost disproportionate time
  • Use templates, modify only what's necessary
  • Track deviations from standard

4. Document Everything

  • Memory fails, paper doesn't
  • Contemporaneous notes beat reconstructed memories
  • Email confirmations for verbal agreements

5. Know Your Materiality Thresholds

  • Not every risk needs CEO attention
  • Define what "material" means for your stage
  • Escalate only what truly matters

6. Outside Counsel for Bet-the-Company

  • Internal handles routine, experts handle existential
  • Litigation, M&A, regulatory investigations → specialists
  • Know when you're out of your depth

7. Regulatory is Non-Negotiable

  • Clever workarounds create future liability
  • Compliance is cheaper than enforcement
  • When in doubt, err on conservative side

Legal Focus by Stage

StageFocus
Pre-seedFormation, founder agreements, IP assignment
SeedSAFEs, NDAs, first customer contracts, trademark
Series AOption pool, investor rights, privacy policy
Series B+Compliance programs, international, M&A readiness

Common Traps

  • Over-lawyering small deals — $10K contract doesn't need $5K in legal fees
  • Ignoring international — US terms don't work everywhere
  • Template without review — every deal has context
  • Verbal agreements — "we agreed" means nothing without documentation
  • Waiting for litigation — proactive compliance beats reactive defense

Human-in-the-Loop

These decisions require human judgment:

  • Litigation vs settlement choices
  • Regulatory disclosure decisions
  • Material contract negotiations
  • Board-level governance changes
  • M&A deal structuring

Related Skills

More Clawic skills, get them at https://clawic.com/skills/ (install if the user confirms):

  • ceo — executive leadership
  • cfo — financial strategy
  • coo — operational compliance
  • business — business fundamentals

Feedback

Trustgrade A

  • passBody integrity

    Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.

  • passType matchnot applicable to this artifact type

    Whether the artifact is really the kind of thing its metadata claims it is.

  • passFreshness

    How long since the source repository was last pushed to.

  • passPrompt injection

    Scans the artifact's own text for instructions aimed at your agent rather than at you.

  • passLicense

    Whether the source repository declares an SPDX license permissive enough to redistribute.

How the grade is calculated

Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:

  • Aevery check passed
  • Bone warning
  • Ctwo warnings
  • Dprompt injection or body integrity failed, or three warnings
  • Fone of those failed, and something else is wrong

These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.

Versions

  • git-b6ff541e4bc42026-07-31