materialize-redshift-create skillA
materialize-redshift-create is agent-read markdown (skill) from estuary/agent-skills: Create a Redshift materialization to stream Estuary collections into Amazon Redshift tables. Use when setting up Redshift as a destination for captured data. Use when user says "send to Redshift", "materialize to Redshift", "Redshift destination", or "load into Redshift"..
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
# Create Redshift Materialization Create a Redshift materialization using flowctl to stream data from Estuary collections into Amazon Redshift tables. **Applies to**: materialize-redshift (Redshift Provisioned and Serverless) ## Step 0: Load Connector Documentation Before proceeding, fetch the official connector docs for prerequisites, config reference, and setup instructions. **Load the docs page:** https://docs.estuary.dev/reference/Connectors/materialization-connectors/amazon-redshift/ Use WebFetch to load this page. It covers: - Prerequisites (Redshift cluster, S3 bucket, IAM credentials) - Full config property reference - SSH tunnel configuration - Network access and IP allowlisting **Search Kapa for tribal knowledge** (if the Estuary MCP is configured): ``` Search kapa ai knowledge sources for "materialize redshift common issues" ``` If Kapa MCP is not configured, the user can set it up: https://docs.estuary.dev/features/mcp-integration/ This skill provides the **flowctl workflow** and **troubleshooting** that docs don't cover. ## Step 1: Gather Requirements Before writing any YAML, ask the user: …
Read the whole file at its exact version.
How to install
mdr add estuary/agent-skills/materialize-redshift-create@git:20260505.8873932mdr add estuary/agent-skills/materialize-redshift-create@sha256:b7161babfbd00338Pin 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_xepkyxeqim2bp3ig)
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 (7389 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_xepkyxeqim2bp3ig GET https://markdownregistry.com/api/v1/resolve?ref=estuary/agent-skills/materialize-redshift-create GET https://markdownregistry.com/api/v1/blob/b7161babfbd00338f5044cab68a619ab368dc0786a05fdfc27b16a64c8511d58
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.