Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
glebis avatar

Red

  • 41 installs
  • 339 repo stars
  • Updated August 4, 2026
  • glebis/claude-skills

Check residual re-identification risk on already-redacted text, surfacing surviving identifiers, cross-file linkability, and inferable attribute categories.

About

Re-runs the CONFIDE detectors on redacted output to flag singling-out, linkability, and optional inference risk mapped to GDPR Art-29, reporting categories and counts only. A developer uses it after redacting to gauge what an attacker could still infer before sharing.

  • Risk tiers (HIGH/MEDIUM/LOW) from surviving direct vs quasi identifiers
  • Defensive-only, counts-only, never produces a re-identification recipe

Red by the numbers

  • 41 all-time installs (skills.sh)
  • Ranked #1,410 of 2,203 Security skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/glebis/claude-skills --skill red

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs41
repo stars339
Last updatedAugust 4, 2026
Repositoryglebis/claude-skills

What it does

Check residual re-identification risk on already-redacted text, surfacing surviving identifiers, cross-file linkability, and inferable attribute categories.

Files

SKILL.mdMarkdownGitHub ↗

confide:red — residual re-identification risk check

A defensive audit of YOUR OWN already-redacted output. It does not score against ground truth and is not a benchmark. It surfaces, qualitatively, what an attacker could still do — mapped to GDPR Art-29: singling-out, linkability, inference.

GUARDRAILS — read before running

  • Run only on the user's own redacted output. If asked to de-anonymize or re-identify

third-party / non-consented data, refuse.

  • Report risk categories and counts only — never produce a step-by-step

re-identification recipe or guess the hidden values.

  • Local attacker by default. Enable the cloud/LLM inference probe (--inference)

only on synthetic or explicitly consented data.

  • Absence of a finding ≠ safety. A weak local detector/attacker is a FLOOR, not a

ceiling. Always tell the user human review is still required.

  • This pairs with confide:anon — run red after redacting, on the redacted file.

What it checks

1. Singling-out (deterministic, offline — the load-bearing signal): re-run detect_regex (+ detect_natasha if available) on the redacted text. Anything they still find is a surviving identifier the redaction missed. Counts by type. 2. Linkability (multi-file): given a folder, compare every file pair for shared surviving quasi-identifiers and flag potentially linkable pairs (count + types only). 3. Inference (LLM, optional, opt-in): prompt the local attacker model (cfg.red_attacker_model) for the attribute categories it could still infer (profession, location type, age band, …). Degrades gracefully if no model. WARN the user it under-reports (floor, not ceiling).

Risk tier rule

  • HIGH — any DIRECT identifier survives (EMAIL, PHONE, URL, ID, PERSON).
  • MEDIUM — only QUASI identifiers survive (LOCATION, ORG, DATE, AGE, PROFESSION,

MEDICATION), or linkable pairs exist across files.

  • LOW — no surviving identifiers found (still NOT a guarantee).

How to run

# single redacted file (offline, deterministic)
python3 skills/red/scripts/red.py path/to/file.green.md

# a folder of redacted files (adds linkability)
python3 skills/red/scripts/red.py path/to/redacted_dir/

# add the local inference probe — synthetic/consented data ONLY
python3 skills/red/scripts/red.py path/to/file.green.md --inference

# machine-readable
python3 skills/red/scripts/red.py path/to/file.green.md --json

Output

A residual-risk report: per-file surviving-identifier counts by type, an overall risk tier, the inference categories claimed (if probed), the linkable-pair count, and the caveat that absence of a finding ≠ safety; human review still required. No PII values, no re-identification steps.

Related skills

Securityauditcompliance

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.