Data Data Observability
Use when the user asks about data observability: freshness checks, row-count and volume anomalies, schema drift detection, data health dashboards or data incident management with Monte Carlo, Elementary or Soda. Produces monitors, SLAs and incident runbooks across pipeline stages. Not for writing test suites (use data-testing).
Install
npx skills add j4flmao/agent-skills --skill data-data-observabilitygit 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-observability ~/.claude/skills/data-data-observabilityPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Data Observability ## Purpose Design comprehensive data observability across pipelines: freshness, volume, schema, quality, lineage, and incident management. ## Agent Protocol ### Trigger Exact user phrases: "data observability", "data quality monitoring", "data profiling", "data health", "freshness check", "row count anomaly", "schema drift", "data incident", "data lineage", "data monitoring", "observability platform". ### Input Context - Data stack (warehouse, lake, pipelines, BI tools) - Number of tables/datasets to monitor - Existing quality checks and monitoring - Team size and on-call rotation - SLAs for data freshness and quality - Incident management workflow - Monitoring budget and tooling preferences ### Output Artifact Data observability architecture with monitoring checks, alerting rules, and incident response playbook. ### Response Format ```yaml # Observability checks per dataset # Freshness, volume, schema, quality # Alert thresholds # Incident response workflow ``` ### Completion Criteria - [ ] Freshness checks configured for all critical datasets - [ ] Volume monitoring with anomaly detection - [ ] Schema drift detection on source and staging tables - [ ] Quality checks on key columns (nulls, uniqueness, referential integrity) - [ ] Lineage tracking from source to dashboard - [ ] Alerting configured with severity levels - [ ] Incident response runbook written ## Workflow ### Step 1: Dataset Inventory
Details
- Skill name
data-data-observability- Repository
- j4flmao/agent-skills
- Path
skills/data/data-observability/SKILL.md- License
- MIT
- Repo updated
- 17 November 2026
FAQ
What does the Data Data Observability skill do?
Use when the user asks about data observability: freshness checks, row-count and volume anomalies, schema drift detection, data health dashboards or data incident management with Monte Carlo, Elementary or Soda. Produces monitors, SLAs and incident runbooks across pipeline stages. Not for writing test suites (use data-testing).
How do I install the Data Data Observability skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add j4flmao/agent-skills --skill data-data-observability. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Data Data Observability 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).
Datacenter
45j4flmao/agent-skills
Use when the user asks about data center design, Uptime Tier I-IV, rack power and kW per rack, PDU and UPS, cooling, hot/cold aisle containment, N+1 or 2N redundancy, structured cabling, DCIM, or colocation choice. Produces facility and capacity designs. Not for server provisioning (use bare-metal) or network fabric (use devops-network-infrastructure).
Consul
45j4flmao/agent-skills
Use when the user asks about HashiCorp Consul, service discovery, Consul DNS, health checks, Consul KV, ACLs, service mesh intentions, mesh gateways, WAN federation, admin partitions, or consul-template. Produces Consul configs and operations runbooks. Not for Istio or Linkerd (use devops-service-mesh) or Nomad scheduling (use nomad).
Dependency Management
45j4flmao/agent-skills
Use when the user asks about Dependabot, dependabot.yml, Renovate config, lock files, version pinning, dependency update strategy, automerging patch bumps, or npm audit vulnerability scanning. Produces update bot configs and a dependency policy. Not for SBOM generation (use security-sbom) or monorepo workspaces (use monorepo).
Browse the most popular Claude skills, all devops & cloud skills, or write your own with the skills generator.