/is-this-a-problem

1. Load ~/.claude/plugins/config/claude-for-legal/product-legal/CLAUDE.md → Risk calibration.
2. Apply the triage workflow below.
3. Pattern-match. Check for common traps.
4. Answer in one minute: ✅ Fine / ⚠️ Needs a look / 🛑 Hold. One sentence why.
5. If ⚠️ or 🛑: name the next step.

/product-legal:is-this-a-problem "Can we use customer logos on the pricing page?"

Matter context

Matter context. Check ## Matter workspaces in the practice-level CLAUDE.md. If Enabled is ✗ (the default for in-house users), skip the rest of this paragraph — skills use practice-level context and the matter machinery is invisible. If enabled and there is no active matter, ask: "Which matter is this for? Run /product-legal:matter-workspace switch <slug> or say practice-level." Load the active matter's matter.md for matter-specific context and overrides. Write outputs to the matter folder at ~/.claude/plugins/config/claude-for-legal/product-legal/matters/<matter-slug>/. Never read another matter's files unless Cross-matter context is on.

Destination check

Before producing output, check where it's going. If the user has named a destination (a channel, a distribution list, a counterparty, "everyone"), ask whether it's inside the privilege circle. Public channels, company-wide lists, counterparty/opposing counsel, vendors, and clients (for work product) waive the protection. When the destination looks outside the circle, flag it and offer (a) the privileged version for legal only, (b) a sanitized version for the broader channel, or (c) both — don't silently apply a privileged header and then help paste it somewhere the header won't protect it. See the canonical ## Shared guardrails → Destination check in this plugin's CLAUDE.md.

Purpose

Most "quick legal question" Slacks are one of three things: (a) not a problem, say so fast, (b) a real thing that needs a real look, route it, (c) a thing that looks fine but has a trap, catch the trap. This skill sorts in under a minute using the calibration table.

The goal is speed. The PM asked at 4:47pm. They want an answer, not a memo.

Load calibration

Read ~/.claude/plugins/config/claude-for-legal/product-legal/CLAUDE.md → ## Risk calibration. The whole point of this skill is pattern-matching against that table.

The triage

Match against calibration

Does the question match a pattern in the calibration table?

Matches "usually FYI": → Say so. One line. "You're fine — [pattern]. Ship it."

Matches "usually requires work": → Name the work. "Needs a [PIA / vendor review / claims check]. Takes [timeline from table]. Want me to start it?"

Matches "usually blocks": → Stop them. "Hold on — [pattern]. This needs a real look before anyone commits to a date. Let's talk."

Doesn't match anything: → Say that too. "This doesn't pattern-match to anything I've seen here. Needs a human look — [your name] or me tomorrow?"

The trap check

Some questions are fine on the surface but have a twist. Recognize the fact pattern, ask the catch question, then research the applicable doctrine for the specific fact pattern before concluding whether it's a problem or not.

…