ThomasMoreAI/legal-skills-open / br/regulatory/skills/cold-start-interview-9
cold-start-interview-9
VerifiedCold-start interview — builds your watchlist, indexes the policy library, and learns your materiality threshold so the monitor surfaces signal instead of noise. Use on fresh install, when reconfiguring (--redo), or when re-checking what connectors are actually responding (--check-integrations).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 32.0 KB |
| references/company-profile-template.md | markdown | 1.4 KB |
references/company-profile-template.md
View on GitHub# Company Profile
*Shared by all Claude for Legal plugins. The first plugin you set up writes this; the rest read it.
Edit directly or re-run any plugin's `/cold-start-interview` to update.*
**Practice setting:** [Solo/small firm | Midsize/large firm | In-house | Government/legal aid/clinic]
**Name:** [Company or firm name]
**Industry:** [What the company does / the firm's primary practice areas]
**What we sell / deliver:** [Products, services, who to — or "N/A, law firm"]
**Size:** [Employee count / lawyers / relevant headcount]
## Geographic and regulatory footprint
**Jurisdictions we operate in:** [e.g., US (CA, NY, TX), UK, EU (DE, FR), AU, SG]
**Primary jurisdiction:** [Where the bulk of work happens]
**Regulators we're subject to:** [SEC, FTC, ICO, EDPB, ASIC, OAIC, etc. — only what applies]
**Open regulatory matters:** [or none]
## Risk posture
**Overall risk appetite:** [Conservative / middle / aggressive]
**What keeps us up at night:** [The thing that would be a very bad day]
**The question leadership always asks:** [or not known yet]
## Key people
**GC / Head of Legal:** [Name]
**Escalation chain:** [Name → Name → Name, or "set per plugin"]
---
*Per-plugin practice profiles (playbooks, review frameworks, house style, matter workspaces) live alongside this file in each plugin's folder. This file holds the facts that are true regardless of which plugin you're using.*
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |