schema-field-selection

schema-field-selection is a skill for Claude Code from estuary/agent-skills. It costs 67 tokens per session (1,430 once invoked), scanned A, original, Apache-2.0.

A guide for choosing which fields from Estuary collections appear in destination tables. It supports including required nested fields and excluding unwanted fields.

In plain words
What is it for?
Use it to include deeply nested values, exclude debug or sensitive fields, or override the destination connector's default field choices. Excluding a field here does not remove it from the collection.
Why use it?
It helps keep tables narrower and avoids sending unnecessary or sensitive fields to a destination. This can make downstream data easier to use and manage.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the estuary-schema plugin — 6 skills shipped together

Good fit Use it to include deeply nested values, exclude debug or sensitive fields, or override the destination connector's default field choices. Excluding a field here does not remove it from the collection.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/estuary/agent-skills/schema-field-selection
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add estuary/agent-skills --skill schema-field-selection
Clone the repo
git clone --depth 1 https://github.com/estuary/agent-skills

Made for: Claude Code.

Or install estuary-schema, the plugin that ships this one along with the rest of its 6 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for schema-field-selection

README.md
[![agentmods](https://agentmods.dev/badge/skills/estuary/agent-skills/schema-field-selection/github.svg)](https://agentmods.dev/skills/estuary/agent-skills/schema-field-selection)
Your own site
<a href="https://agentmods.dev/skills/estuary/agent-skills/schema-field-selection"><img src="https://agentmods.dev/badge/skills/estuary/agent-skills/schema-field-selection/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for schema-field-selection

Your own site · 80×15
<a href="https://agentmods.dev/skills/estuary/agent-skills/schema-field-selection"><img src="https://agentmods.dev/badge/skills/estuary/agent-skills/schema-field-selection.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 67 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,430 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00067 $0.01430
Opus 5 $0.00034 $0.00715
Sonnet 5 $0.00013 $0.00286
Haiku 4.5 $0.00007 $0.00143

Measured 8d ago against content hash 50ccd00750f5, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

schema-field-selection scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/schema-field-selection/SKILL.md · 127 lines

How it starts

The opening of the file, as written. The whole thing — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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

flowctl catalog pull-specs --name <materialization-name>

Step 2: Configure Field Selection

Add or modify the fields stanza in the binding:

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

Note: require is an object (field: {}), exclude is an array (- field).

Note: Each connector marks certain fields as required — typically the root document (flow_document) and the collection-key components, and some connectors require additional fields (e.g., CDC-style materializations that depend on _meta/op). Attempting to exclude a connector-required field returns a LOCATION_REQUIRED / FIELD_REQUIRED constraint and the publish fails. The exact list comes from each connector's Validate response.

Depth Modes

The recommended setting controls how deeply nested fields are automatically selected. UI labels are in parentheses:

Value UI Label Description
0 Required Only Selects only fields the connector marks required (root document + key components, plus any connector-specific required fields)
1 Depth 1 (default) Top-level scalar fields
2 Depth 2 Two levels of nesting
true Unlimited Depth All scalar fields at any depth

Read the full file on GitHub · 127 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 8d ago First seen · 127 lines · 67 tokens per session scan A 50ccd00750f5

Subscribe to this mod's changes

schema-field-selection is a skill published in the GitHub repository estuary/agent-skills (7 stars, last pushed 18d ago), licensed Apache-2.0. It adds 67 tokens to every session and 1,430 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

cocoindex

This skill should be used when building data processing pipelines with CocoIndex, a Python library for incremental data transformation. Use when the task involves processing files/data into databases, creating vector embeddings, building knowledge graphs, ETL workflows, or any data pipeline requiring automatic change…

cocoindex-io/cocoindex · 88 tokens

confluent-cloud-cdc-tableflow

Set up end-to-end Change Data Capture (CDC) pipelines on Confluent Cloud using Debezium source connectors, Flink for transformation, and Tableflow for data lake integration. Supports JSONSR, Avro, and Protobuf formats. Handles schemaless topics (plain JSON without SR) and multi-event topics. This skill handles the…

confluentinc/agent-skills · 203 tokens

good-skill

Generate a Confluent Cloud topic creation script with idempotency checks. Use when the user asks to create a topic, provision topics, or write a create-topics.sh for Confluent Cloud. Do NOT trigger for self-managed Apache Kafka, schema registration, Terraform generation, or Kafka Streams topology authoring.

confluentinc/agent-skills · 69 tokens

mysql-context

Pull compact MySQL field diffs into context via the mysql-context MCP binlog indexer. Use when the task depends on what changed in MySQL, recent database changes, a watched table, or a before/after row image. Do not use this to dump current table rows.

velinussage/mysql-context-mcp · 60 tokens

kafka-schema-registry

Scan a project to identify Kafka applications, extract schemas from data models, tag PII fields, generate Terraform for Confluent Schema Registry registration, and produce a migration report with rollout ordering. Use this skill when a user asks to analyze a folder or repo for Kafka usage, extract schemas, audit…

confluentinc/agent-skills · 77 tokens

change-data-capture-admin

Use when enabling, configuring, or monitoring Change Data Capture (CDC) entity selection, channel enrichment, and delivery usage limits from an admin perspective. NOT for writing an Apex change-event trigger — use apex/change-data-capture-apex. NOT for subscribing an external system over Pub/Sub or CometD — use…

PranavNagrecha/AwesomeSalesforceSkills · 76 tokens