is-this-a-problem

Fast "is this a problem?" answer for the quick Slack question — pattern-matches against your calibration. Use when the user says "is this a problem", "quick question", "can we do X", "do I need legal review for", "sanity check", or pastes a PM's question that needs a same-minute fine / needs a look / hold call.

Jump to install

Repository: ThomasMoreAI/legal-skills-open
Last source activity: June 1, 2026 at 17:27
Detected SKILL.md language: English
Stars: 40
Forks: 4

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/ThomasMoreAI/legal-skills-open --skill is-this-a-problem

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

name	is-this-a-problem
title	/is-this-a-problem
description	Fast "is this a problem?" answer for the quick Slack question — pattern-matches against your calibration. Use when the user says "is this a problem", "quick question", "can we do X", "do I need legal review for", "sanity check", or pastes a PM's question that needs a same-minute fine / needs a look / hold call.
author	anthropics
author_url	https://github.com/anthropics/claude-for-legal/tree/main/product-legal/skills/is-this-a-problem
license	Apache-2.0
version	0.1.0
execution_mode	open
jurisdiction	general
practice	general
language	en

/is-this-a-problem

Load ~/.claude/plugins/config/claude-for-legal/product-legal/CLAUDE.md → Risk calibration.
Apply the triage workflow below.
Pattern-match. Check for common traps.
Answer in one minute: ✅ Fine / ⚠️ Needs a look / 🛑 Hold. One sentence why.
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.

Question sounds like	Why it might not be simple	Catch it by asking
"Can we add [vendor] to the integration?"	Vendor touches a new data category — flag as potentially implicating privacy and vendor-risk regimes and route for research	"What data flows to them?"
"Can we A/B test the pricing page?"	Differential pricing by segment can implicate consumer-protection and anti-discrimination regimes — flag and route for research	"Are both arms seeing the same price for the same thing? How are users assigned to arms?"
"Can we auto-enroll users in the new feature?"	Default-on behavior for users who previously opted out can implicate consent and consumer-protection rules — flag and route for research	"Does this respect existing preferences?"
"Can we use customer logos on the site?"	Logo use is a separate permission from the contract relationship — flag as potentially implicating publicity / endorsement rules and the customer's own contract terms	"What does the contract say about publicity? Do we have written permission?"
"Can we train on this data?"	Usage rights for the original collection purpose may not extend to training — flag and research the notice/consent the users were given at collection	"What did we tell users when we collected it? What jurisdictions are the users in?"
"It's just an internal tool"	Internal tools still process personal data — flag as potentially implicating privacy regimes and route for research	"Whose data does it touch? Employees, customers, third parties?"
"We already do something similar"	"Similar" is doing a lot of work — the delta is where the issue usually is	"Similar how? What's actually different?"
"Can we use [AI vendor / LLM] for this?"	Vendor AI terms may permit training on inputs; use case may need an AIA — flag and route to `/ai-governance-legal:use-case-triage`	"Is there an AI addendum? What data goes into the model?"
"Can we add AI to this feature?"	May be a new use case not in the registry; may trigger AIA requirement — flag and route to `/ai-governance-legal:use-case-triage`	"What does the AI do — assistive or automated? Who does it act on?"
"The model just decides automatically"	Automated decision-making without human review is regulated in some jurisdictions — flag and research the applicable rules for the affected users' jurisdictions	"Who's affected? Is there a human in the loop? Where are the affected users?"
"It's AI-generated content"	Output IP and disclosure duties vary by jurisdiction and vendor terms — flag and route for research	"What's the content type? Does the vendor's ToS address output ownership? Who is the audience?"
"We're just fine-tuning on our data"	Training data rights, output IP, and vendor obligations all change — flag and route to `/ai-governance-legal:vendor-ai-review`	"What's in the training data? Is any of it customer or employee data?"

is-this-a-problem

Install options

Review the source files

/is-this-a-problem

Matter context

Destination check

Purpose

Load calibration

The triage

Match against calibration

/is-this-a-problem

Matter context

Destination check

Purpose

Load calibration

The triage

Match against calibration

The trap check

Output format

When to NOT use this skill

Tone

Close with the next-steps decision tree

is-this-a-problem

Source facts

Install options

Review the source files

More from this repository

/is-this-a-problem

Matter context

Destination check

Purpose

Load calibration

The triage

Match against calibration

/is-this-a-problem

Matter context

Destination check

Purpose

Load calibration

The triage

Match against calibration

The trap check

Output format

When to NOT use this skill

Tone

Close with the next-steps decision tree

More from this repository