schema-field-selection skillA
schema-field-selection is agent-read markdown (skill) from estuary/agent-skills: Control which fields are included or excluded in materializations using depth modes and field overrides. Use when reducing table width, including nested fields, excluding PII, or optimizing performance. Use when user says "exclude fields", "include nested field", "too many columns", "select specific fields", or "field depth"..
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
# Field Selection for Materializations
Control which fields are included or excluded in materializations using depth modes and field overrides.
**Docs:** https://docs.estuary.dev/guides/customize-materialization-fields/
## When to Use
- Reduce table width by excluding unnecessary fields
- Include deeply nested fields that aren't selected by default
- Exclude sensitive fields from materializations (note: data still exists in the collection — for true PII protection, use redaction on the writeSchema instead)
- Override connector's default field recommendations
## Procedure
### Step 1: Pull the Materialization Spec
```bash
flowctl catalog pull-specs --name <materialization-name>
```
### Step 2: Configure Field Selection
Add or modify the `fields` stanza in the binding:
```yaml
bindings:
- source: tenant/your/collection
resource: { table: your_table }
fields:
recommended: true # Depth mode (see below)
require: # Object — explicitly include fields
deeply/nested/field: {}
another_field: {}
exclude: # Array — explicitly exclude fields
- sensitive_data
- debug_info
```
…Read the whole file at its exact version.
How to install
mdr add estuary/agent-skills/schema-field-selection@git:20260707.049f6aemdr add estuary/agent-skills/schema-field-selection@sha256:50ccd00750f50375Pin 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_fpcu4hit45pmla65)
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 (6751 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_fpcu4hit45pmla65 GET https://markdownregistry.com/api/v1/resolve?ref=estuary/agent-skills/schema-field-selection GET https://markdownregistry.com/api/v1/blob/50ccd00750f50375e7955ca1b56dc722f10389c3e29bf24e601e21c4a911055b
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.