schema-field-redaction skillA
schema-field-redaction is agent-read markdown (skill) from estuary/agent-skills: Add redaction annotations to sensitive fields in schemas to block or hash PII. Use when configuring GDPR/HIPAA compliance, protecting credentials, or blocking internal fields from materializations. Use when user says "protect PII", "hide sensitive data", "hash field", "redact field", "GDPR compliance", "don't capture field", "remove field from Estuary", or "prevent Estuary from capturing field"..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Protect Sensitive Data with Field Redaction Add redaction annotations to your collection schema to protect sensitive data at the source. Redacted fields are blocked or hashed before documents are stored or materialized. ## When to Use - **PII Protection**: Hash emails, SSNs, phone numbers for GDPR/HIPAA/CCPA compliance - **Credential Security**: Block passwords, API keys, tokens from ever leaving the capture - **Internal Fields**: Remove internal-only metadata before materialization - **Data Minimization**: Ensure only necessary data reaches downstream systems ## How Redaction Works Redaction is applied at write time — sensitive data never reaches Estuary storage, logs, or downstream materializations. This is the earliest point to remove fields, before derivations or materialization field selection. Redaction only applies to documents captured **after** publishing the annotation. To redact historical data, trigger a dataflow reset backfill on the capture. ## Redaction Strategies | Strategy | Effect | Use When | |----------|--------|----------| | `block` | Removes the field entirely | Field should never exist downstream | …
Read the whole file at its exact version.
How to install
mdr add estuary/agent-skills/schema-field-redaction@git:20260707.049f6aemdr add estuary/agent-skills/schema-field-redaction@sha256:c5f2df53d606c4a5Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_frmztdt6swnyvfmo)
1 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (8877 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
estuary/agent-skills · 7 stars · license Apache-2.0 · pushed 2026-09-17 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_frmztdt6swnyvfmo GET https://markdownregistry.com/api/v1/resolve?ref=estuary/agent-skills/schema-field-redaction GET https://markdownregistry.com/api/v1/blob/c5f2df53d606c4a5cc6647f331820dc2deab6d33187d375a2d322a5a811e192f
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.