estuary-catalog-history SKILL.md skillA
estuary-catalog-history from estuary/agent-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add estuary/agent-skills/estuary-catalog-history@git:20260505.8873932Pins git:20260505.8873932 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- estuary/agent-skills
- Path
skills/estuary-catalog-history/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260505.8873932, committed May 5, 2026
- Size
- 12,756 bytes
- Repository stars
- 7
- License
- Apache-2.0
View publication history for catalog resources — who changed what and when. Use when investigating timeline of changes, finding who modified a connector, or correlating changes across capture/collection/materialization chains. Use when user says "what changed", "who changed", "publication history", "catalog history", "when was it published", "timeline of changes", or "what happened to my connector".
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# flowctl catalog history - Publication History for Catalog Resources **Concepts**: Every change to a catalog resource (capture, materialization, collection) creates a publication. `catalog history` shows the full timeline of publications including who made the change, what changed, and the full spec at each point in time. ## Basic Usage View publication history for any catalog resource: ```bash flowctl catalog history --name <tenant/resource-name> ``` Examples: ```bash # Capture history flowctl catalog history --name acme/source-postgres # Materialization history flowctl catalog history --name acme/materialize-snowflake # Collection history flowctl catalog history --name acme/orders ``` ## With Full Specs (`--models`) Include the complete spec at each publication point. Requires json or yaml output: ```bash flowctl catalog history --name acme/source-postgres --models -o json | jq ``` ## Output Format Output is **newline-delimited JSON** (NDJSON — one JSON object per line). Use `jq -s` to slurp into an array for filtering/sorting. Fields per entry: - `catalog_name` — resource name - `catalog_type` — capture, materialization, collection, etc. …
Read the whole file at its exact version.
How to install
mdr add estuary/agent-skills/estuary-catalog-history@sha256:8de1a2af61cc2aebThe line at the top of this page pins the label git:20260505.8873932, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_6upjzse5o5z6noxm)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on May 5, 2026.
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 (12756 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-11-04 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_6upjzse5o5z6noxm GET https://markdownregistry.com/api/v1/resolve?ref=estuary/agent-skills/estuary-catalog-history GET https://markdownregistry.com/api/v1/blob/8de1a2af61cc2aeb3fd500c181070af9aba1d4a4462921f8c69342c676f8d3f3
Your AI assistant 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.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.