CEET — Legal / Compliance
What this skill does
Interview an in-house legal counsel, compliance lead, DPO, or legal operations lead. Produce a cognitive clone and AI environment that reviews contracts, drafts policies, and assesses risk in their style.
When to use
- The user wants an AI that does first-pass contract review, policy drafting, or regulatory triage in their voice.
- A GC wants their judgment scaled across a team or product partners.
- A founder wants legal instincts captured before hiring in-house.
Important: The output is not a substitute for legal advice. It is a reasoning style. The AI environment generated should always flag matters for human counsel on final decisions.
Run order
- Read
interview/questions.md.
- Extract themes, with a bias toward risk posture — the spectrum from paranoid to business-forward.
- Ask for redline examples — how they mark up a standard DPA, MSA, or customer agreement.
- Synthesize into the role-specific
templates/cognitive-profile.md.
- Activate into the role-specific
templates/ directory. Save to templates/.
- Hand off via
../docs/tool-integration.md.
Legal-specific things to listen for
- Risk posture. Where on the paranoid↔business-enabling spectrum.
- Contract playbook. Standard markup positions on liability, indemnity, IP, warranty, termination, auto-renewal.
- Escalation criteria. What they handle, what goes to outside counsel, what must go to a partner.
- Regulatory frameworks in scope. GDPR, CCPA, HIPAA, SOC 2, DORA, AI Act, state-by-state US.
- Privacy stance. Data minimization, consent, DPAs, sub-processor discipline.
- Policy drafting voice. Terse, narrative, example-driven?
- Risk register approach. What risks get tracked, how often revisited.
- Business partnership stance. How they frame "no" as "yes, if…"
- IP hygiene. Open-source license review, employee IP, customer data use.
- Disputes & incident response. Breach notification, security incident legal flow.
Synthesis guardrails
- Capture their standard redline positions as a reusable playbook.
- Include a disclaimer block in the AI environment — the AI is reasoning in their style, not providing legal advice.
- Note the jurisdictions they actually practice in and where they don't opine.
- Save outputs to
templates/.
1---2name: ceet-legal-compliance3description: Cognitive Extraction Engine for in-house legal counsel and compliance leads in software companies. Use when a user wants to clone a legal/compliance operator's judgment — how they review contracts, weigh risk, respond to regulatory questions, draft policy, and advise the business. Trigger on phrases like "extract my legal thinking", "clone our GC", "build an AI that reviews contracts like me", "interview me about compliance", "capture my risk framework", "make a legal cognitive clone". Outputs are tool-agnostic.4license: MIT5---67# CEET — Legal / Compliance89## What this skill does1011Interview an in-house legal counsel, compliance lead, DPO, or legal operations lead. Produce a cognitive clone and AI environment that reviews contracts, drafts policies, and assesses risk in their style.1213## When to use1415- The user wants an AI that does *first-pass* contract review, policy drafting, or regulatory triage in their voice.16- A GC wants their judgment scaled across a team or product partners.17- A founder wants legal instincts captured before hiring in-house.1819**Important:** The output is not a substitute for legal advice. It is a reasoning style. The AI environment generated should always flag matters for human counsel on final decisions.2021## Run order22231. **Read** `interview/questions.md`.242. **Extract** themes, with a bias toward **risk posture** — the spectrum from paranoid to business-forward.253. **Ask for redline examples** — how they mark up a standard DPA, MSA, or customer agreement.264. **Synthesize** into the role-specific `templates/cognitive-profile.md`.275. **Activate** into the role-specific `templates/` directory. Save to `templates/`.286. **Hand off** via [`../docs/tool-integration.md`](../docs/tool-integration.md).2930## Legal-specific things to listen for3132- **Risk posture.** Where on the paranoid↔business-enabling spectrum.33- **Contract playbook.** Standard markup positions on liability, indemnity, IP, warranty, termination, auto-renewal.34- **Escalation criteria.** What they handle, what goes to outside counsel, what must go to a partner.35- **Regulatory frameworks in scope.** GDPR, CCPA, HIPAA, SOC 2, DORA, AI Act, state-by-state US.36- **Privacy stance.** Data minimization, consent, DPAs, sub-processor discipline.37- **Policy drafting voice.** Terse, narrative, example-driven?38- **Risk register approach.** What risks get tracked, how often revisited.39- **Business partnership stance.** How they frame "no" as "yes, if…"40- **IP hygiene.** Open-source license review, employee IP, customer data use.41- **Disputes & incident response.** Breach notification, security incident legal flow.4243## Synthesis guardrails4445- Capture their **standard redline positions** as a reusable playbook.46- Include a **disclaimer block** in the AI environment — the AI is reasoning in their style, not providing legal advice.47- Note the jurisdictions they actually practice in and where they *don't* opine.48- Save outputs to `templates/`.
ThomasMoreAI