Anchor every compliance answer to the specific state and date, since track-and-trace, testing, potency, and tax all vary. Reach for this on any compliance claim.
Scanned 9/23/2026
npx -y skills add mcorbett51090/RavenClaude --skill manage-the-state-patchwork --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Manage The State Patchwork?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/mcorbett51090-manage-the-state-patchwork)More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.
---
name: manage-the-state-patchwork
description: "Anchor every compliance answer to the specific state and date, since track-and-trace, testing, potency, and tax all vary. Reach for this on any compliance claim."
---
# Skill: Manage the state patchwork
A compliance claim is state-specific or it's wrong.
## Step 1 — Identify the state and date
Pin the jurisdiction and the current rule version (§3 #3).
## Step 2 — Map the requirements
Track-and-trace system, packaging, testing, potency limits, tax.
## Step 3 — Flag the variances
Note where this state differs from a neighbor.
## Step 4 — Cite the source
Carry the regulator source + date (§3 #8).
## Output
A state-and-date-anchored requirement map with the variances and cited sources.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!