Data Data Catalog
Use when the user asks about a data catalog: DataHub, OpenMetadata, Amundsen, Apache Atlas, metadata ingestion, business glossary, data discovery search or data ownership. Produces catalog choice, ingestion recipes, glossary and stewardship model. Not for lineage collection itself (use data-lineage) or governance policy (use enterprise-data-governance).
Install
npx skills add j4flmao/agent-skills --skill data-data-cataloggit clone --depth 1 https://github.com/j4flmao/agent-skills.git /tmp/agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills/skills/data/data-catalog ~/.claude/skills/data-data-catalogPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Data Data Catalog ## Purpose Design and deploy a data catalog platform with metadata ingestion, column-level lineage, business glossary, data discovery, ownership model, and usage analytics. ## Agent Protocol ### Trigger Exact user phrases: "data catalog", "DataHub", "Amundsen", "Apache Atlas", "OpenMetadata", "metadata management", "data discovery", "business glossary", "data lineage", "data ownership", "column-level lineage", "metadata ingestion". ### Input Context - Existing data stack (warehouse, lake, BI tools) - Data catalog tool in consideration (if any) - Data governance maturity level - Number of data assets and teams - Compliance requirements (GDPR, SOX, HIPAA) - Current metadata sources (alerts, logs, metastore) ### Output Artifact Data catalog architecture with platform selection, metadata ingestion pipeline design, governance model with glossary and ownership, and usage analytics framework. ### Response Format ```yaml # Catalog platform selection matrix # Metadata ingestion pipeline # Business glossary structure # Ownership & stewardship model # Usage analytics schema ``` No preamble. No postamble. No explanations. No filler/hedging/transitions. Compress output — why use many token when few do trick. ### Completion Criteria - [ ] Catalog platform selected with rationale - [ ] Metadata ingestion pipelines configured for all sources - [ ] Column-level lineage established for critical datasets - [ ] Business glossary defined with domains and terms
Details
- Skill name
data-data-catalog- Repository
- j4flmao/agent-skills
- Path
skills/data/data-catalog/SKILL.md- License
- MIT
- Repo updated
- 17 November 2026
FAQ
What does the Data Data Catalog skill do?
Use when the user asks about a data catalog: DataHub, OpenMetadata, Amundsen, Apache Atlas, metadata ingestion, business glossary, data discovery search or data ownership. Produces catalog choice, ingestion recipes, glossary and stewardship model. Not for lineage collection itself (use data-lineage) or governance policy (use enterprise-data-governance).
How do I install the Data Data Catalog skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add j4flmao/agent-skills --skill data-data-catalog. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Data Data Catalog popular?
It lives in j4flmao/agent-skills, which has 45 GitHub stars and 6 forks.
Related skills
Agent Observability
45j4flmao/agent-skills
Use when the user asks about agent observability, tracing agent reasoning, debugging an agent loop, OpenTelemetry GenAI spans for LLM calls, LLM cost tracking per agent, agent audit logs or hallucination/eval monitoring in production. Produces instrumentation config, trace schema, dashboards, alerts and cost attribution. Not for generic service tracing without LLMs (use devops-opentelemetry).
AI Agent Architectures
45j4flmao/agent-skills
Use when the user asks to build an AI agent, design an agent that calls tools and keeps memory, write an agent system prompt or pick an agent framework (Claude Agent SDK, OpenAI Agents SDK, LangGraph). Produces an architecture brief covering loop, tools, memory, guardrails and evals, routing depth to child skills. Not for workflow patterns (use ai-agentic-workflows).
AI Agent Core Loop
45j4flmao/agent-skills
Use when the user asks about the agent loop, ReAct vs plan-and-solve, re-planning, Reflexion, an agent stuck in a loop, max iterations or termination conditions. Produces a loop spec or patch with state, success predicate, caps and no-progress detection. Not for overall agent design (use ai-agent-architectures) or tool schemas (use tool-calling-principles).
Data Data Contracts
45j4flmao/agent-skills
Use when the user asks about data contracts, producer/consumer schema agreements, dbt model contracts, Open Data Contract Standard, schema compatibility checks or data SLAs. Produces a contract spec (schema, semantics, SLA, owner) and CI enforcement. Not for Kafka Schema Registry compatibility modes (use data-schema-registry) or test suites (use data-testing).
Magicblock Archive
23Parad0x-Labs/openclaw-skills
Archive MagicBlock Ephemeral Rollup session transaction logs — compresses ER sessions into Liquefy vaults and computes a per-session commitment for the receipt_anchor accumulator (this skill does not anchor on-chain; a devnet receipt_anchor is available for explicit use). Fills the MagicBlock auditability gap. x402 session playback pricing included.
Data Schema Registry
45j4flmao/agent-skills
Use when the user asks about Confluent Schema Registry, Apicurio, Avro or Protobuf schemas for Kafka, compatibility modes (BACKWARD, FORWARD, FULL), schema evolution or SerDe config. Produces schema definitions, compatibility settings and client SerDe setup. Not for cross-team data contracts (use data-data-contracts) or Kafka topic design (use data-streaming).
Browse the most popular Claude skills, all marketing, sales & business skills, or write your own with the skills generator.