Disclosure Check
Pre-screen analysis outputs (tables, figures, logs) built on restricted or confidential...
Install
npx skills add pedrohcgs/claude-code-my-workflow --skill disclosure-check -g -a claude-code -y- Repository
- pedrohcgs/claude-code-my-workflow1.7k
- Category
- Engineering
- Updated
- 1mo ago
- License
- MIT
- Context cost
- Mediumabout 2,414 tokens
- Runs scripts
- No, instructions only
What it does
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".
/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 tooutput/, where every language's pipeline writes; if it does not exist but a pre-v2.6scripts/<lang>/_outputs/does, scan that and say so. Also accepts any export-staging directory (e.g., ato_review/folder the analyst stages for the RDC).--provider, selects which disclosure-rule profile to load (Phase 0). One ofcensus/irs/irb/generic. Providers differ, thresholds and rules are not interchangeable; defaultgenericis deliberately conservative.--threshold N, override the minimum cell count (defaultn<10). Census FSRDC commonly uses 10 for establishments; IRS and many IRBs differ. Always reconcile with your provider's written rules.
