# Disclosure Check

Pre-screen analysis outputs (tables, figures, logs) built on restricted or confidential...

- Repository: https://github.com/pedrohcgs/claude-code-my-workflow (1676 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-09-27
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add pedrohcgs/claude-code-my-workflow --skill disclosure-check -g -a claude-code -y`
Codex: `npx skills add pedrohcgs/claude-code-my-workflow --skill disclosure-check -g -a codex -y`
Cursor: `npx skills add pedrohcgs/claude-code-my-workflow --skill disclosure-check -g -a cursor -y`
Gemini CLI: `npx skills add pedrohcgs/claude-code-my-workflow --skill disclosure-check -g -a gemini-cli -y`

## Description

Pre-screen analysis outputs (tables, figures, logs) built on restricted or confidential data for statistical-disclosure-limitation problems before any release. Scans for small cell counts, complementary-suppression gaps, dominance (p-percent / (n,k)), re-identifiable exact counts, PII leakage, and unrounded sensitive statistics; classifies each finding CRITICAL / WARNING / OK and gates on any CRITICAL. Use before depositing or sharing restricted-data results, or when the user says "disclosure check", "SDL scan", "is this output safe to release", "check for small cells", "disclosure avoidance", "pre-screen for the RDC", or "can I export this from the enclave".

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# `/disclosure-check`, Statistical-Disclosure-Limitation pre-screen

Scan analysis outputs built on **restricted or confidential data** (Census FSRDC, IRS SOI, administrative registers, linked health records, proprietary firm panels) for the disclosure-avoidance problems that get an export request rejected, *before* it reaches the data provider's official disclosure review. The skill is a **pre-screen, not a substitute** for that review.

**Core principle:** A single un-suppressed `n=3` cell, an exact count that pins down one firm, or a `p`-percent dominance failure can re-identify a person or establishment. Catch it on your machine, not in the rejection email from the RDC analyst.

## When to use

- **Before requesting an export** from a Census FSRDC / secure data enclave / RDC.
- **Before depositing** restricted-data results to openICPSR, a journal, or a co-author outside the enclave.
- **Before sharing any figure, table, or log** derived from confidential microdata.
- **As a release gate.** Pair with a pre-commit / pre-deposit invocation so no restricted-data output ships un-screened. This is the foundation of the data-management plan for any restricted-data project.

## Inputs

- `$0`, outputs directory to scan. Defaults to `output/`, where every language's pipeline writes; if it does not exist but a pre-v2.6 `scripts/<lang>/_outputs/` does, scan that and say so. Also accepts any export-staging directory (e.g., a `to_review/` folder the analyst stages for the RDC).
- `--provider`, selects which disclosure-rule profile to load (Phase 0). One of `census` / `irs` / `irb` / `generic`. **Providers differ**, thresholds and rules are not interchangeable; default `generic` is deliberately conservative.
- `--threshold N`, override the minimum cell count (default `n<10`). Census FSRDC commonly uses 10 for establishments; IRS and many IRBs differ. Always reconcile with your provider's *written* rules.

## Workflow

### Phase 0: Load the provider's disclosure rules

The rest: https://github.com/pedrohcgs/claude-code-my-workflow/blob/HEAD/.claude/skills/disclosure-check/SKILL.md