rehydrate
From the author
Put the real values back into an analysis that was produced from GREEN (placeholder) text — LOCALLY, using the user's own reversible map. Completes the confide round-trip (redact -> cloud-analyze the green -> rehydrate locally). Use when the user says "rehydrate", "restore real names", "unmask the analysis", "put the names back", "de-redact this output", "reverse the placeholders", or hands you an analysis full of [CONFIDE_PERSON_0001]/[CONFIDE_DATE_0002] plus a *.map.json. Runs only on the user's own map; the map never leaves the machine; nothing fetched or transmitted. Prints counts only — never echoes restored PII. Warns on placeholders not in the map (possible LLM hallucination).
Install
npx skills add glebis/claude-skills --skill rehydrate -a claude-code
Installs to .claude/skills/rehydrate/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
- Ships scripts we have not reviewedLow
Why 80
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- anonglebis/claude-skillsDe-identify a session transcript (file or folder) by redacting PII LOCALLY before any sharing or cloud use. Produces a redacted GREEN copy with unique reserved-sentinel placeholders ([CONFIDE_PERSON_0001], [CONFIDE_EMAIL_0001], [CONFIDE_DATE_0002]...) plus a counts-only stats summary, and a local secret <name>.map.json (0600, gitignored) that enables confide:rehydrate to restore real values after a cloud analysis. Use when the user says "anonymize this transcript", "redact PII", "de-identify session", "make safe to share", "strip personal data", "anonymize notes before sending to an LLM", or points at a transcript/folder that should be scrubbed. Local-only by default — raw text never leaves the machine; the map is the only artifact with originals and stays local; nothing printed is PII; human review is still required before sharing.Engineering★ 403
- redglebis/claude-skillsResidual re-identification RISK CHECK on text you have ALREADY redacted (defensive, dual-use). Use when the user asks to "check residual re-id risk", "red-team my redaction", "what can an attacker still infer", "is this safe to share", or assess "re-identification risk" after anonymizing. Re-runs the CONFIDE detectors on the redacted output to surface surviving identifiers (singling-out), checks multiple files for linkability, and optionally probes a local model for still-inferable attribute CATEGORIES (inference) — mapped to GDPR Art-29. Reports risk categories/counts only, never a re-identification recipe. Pairs with confide:anon (run AFTER redacting).Legal★ 403
- rethinkOvid/paadUse when options, a recommendation, or an already-chosen approach are on the table and the reasoning under them has not been independently checked — especially when the case rests on cited documentation, remembered behavior, or premises nobody verified. Not for generating alternatives, and not for critiquing a spec, which is /pushback.Planning★ 147
- deslopalvin-reyes/better-agentic-ideRewrite text so it doesn't read as AI-generated. Use when the user asks to de-slop, humanize, tighten or clean up writing, or runs /ade:deslop on a file or pasted text.Writing★ 85
- replica-reconJakeschincariol/replica-skillReverse-engineers any app into a recon map: screen inventory, user flows, component list, inferred data model and a feature matrix, from public pages, screenshots, app store listings, help docs and the user's own account. The first step of the Replica pack. Use when the user says "clone this app", "reverse engineer X", "how does X work", "map out X", "what screens does X have", "I want to build my own version of X", "copy this app", or pastes an app's URL or App Store link and wants to rebuild it.Other★ 6.6K
- reflect-and-improveShaishavMaisuria/research-paper-lifecycle-skillsThe reflection agent. Use it right after another skill produces an artifact such as a rewrite from polish-prose, a rebuttal, an abstract, a preflight fix, or a tailored draft to critique that output against the stated goal, the paper's .paper-memory/profile.yml, the relevant rubric, and past .paper-memory/lessons.md, then decide whether it actually improved. Trigger words include reflect, self-critique, did this get better, did my edit help, regression check, review my own output, iterate, refine, second pass, sanity-check the rewrite, and "is the new version actually better". Runs a bounded self-refine / Reflexion loop, guards against regressions, and appends durable, deduplicated, dated lessons to .paper-memory/lessons.md via a stdlib script so the toolkit gets sharper each paper. Reflection adds cost; it only pays off when there is a measurable target.Science★ 58
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in