Agent Plugins Marketplace
← All plugins

data-quality-observability

v0.1.2

Data-quality & observability team — agents (data-quality-architect, data-quality-engineer) for the layer answering 'is this data CORRECT, FRESH, COMPLETE, and can we TRUST it?': producer-boundary contracts, validation tests (not-null/unique/accepted-values/referential/distribution), freshness/volume/schema-drift/distribution monitors, threshold vs statistical anomaly detection, data-quality SLAs/SLIs, and data-incident response (triage, quarantine/circuit-breaker, root-cause, backfill). Fluent in dbt tests + dbt-expectations, Great Expectations, Soda, Elementary, managed observability (Monte Carlo, Bigeye, Metaplane), and warehouse-native checks. skills, a knowledge bank (tooling decision tree + 2026 patterns reference), and templates. Distinct from data-platform (ELT/warehouse/BI), analytics-engineering (dbt transforms), data-orchestration (schedules the runs), and data-governance-privacy (policy/PII/lineage) — this is the trust/quality layer over all of them. Requires ravenclaude-core@>=0.7.0.

Claude Code3 Skills

By Matt CorbettLicense: MIT7 GitHub starsUpdated last week

Directory evidence

Runtimes
Claude Code
Parsed components
3 skill or MCP entries
Source updated
Sep 15, 2026
Manifest status
Canonical path parsed

The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →

Install data-quality-observability for Claude Code

Installs for the current user
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install data-quality-observability@agent-plugin-marketplace

Paste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.

The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.

Get the source manually
git clone https://github.com/mcorbett51090/RavenClaude

Clone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/data-quality-observability/.

Plugin files

plugins/data-quality-observability/
├── .claude-plugin/plugin.json
├── skills/choose-data-quality-approach/SKILL.md
├── skills/design-data-contracts-and-tests/SKILL.md
└── skills/set-up-data-observability-monitors/SKILL.md

Included Skills3

choose-data-quality-approachskills/choose-data-quality-approach/SKILL.md

Pick the right data-quality approach and tooling for a described stack by traversing the data-quality tooling decision tree (already-on-dbt? → check shape, known-rule vs unknown-over-time → build vs buy → where checks run → tool), then return the recommended contracts/tests/monitors mix, the tool (dbt tests / dbt-expectations / Great Expectations / Soda / Elementary / a managed platform / warehouse-native), where each check runs, the block-vs-warn policy, the SLAs, and the conditions that would flip the choice. Reach for this when the user asks "dbt tests vs Great Expectations vs Soda vs Monte Carlo?", "contracts vs tests vs monitors?", "where should checks run?", or "build vs buy observability?". Used by `data-quality-architect` (primary).

design-data-contracts-and-testsskills/design-data-contracts-and-tests/SKILL.md

From a dataset and its consumers, derive the producer-boundary data contract (schema, semantics, freshness and volume expectations, ownership) and the concrete validation test suite (not-null, unique, accepted-values, referential integrity, distribution/value-range), each test carrying a severity. Reach for this when the user asks "write the data contract for this table", "what tests should this dataset have?", or "define the guarantees this producer owes its consumers". Used by `data-quality-architect` and `data-quality-engineer`.

set-up-data-observability-monitorsskills/set-up-data-observability-monitors/SKILL.md

Stand up the observability monitors that watch for the unknown over time — freshness, volume, schema-drift, and distribution/anomaly monitors — each anchored to a baseline and a tolerance (not a hard-coded magic number), then wire owner-routed alerting and link a data-incident runbook. Reach for this when the user asks "set up freshness/volume monitors", "alert us before a stakeholder notices bad data", or "detect schema drift and distribution anomalies". Used by `data-quality-engineer` (primary).

Plugin manifests1

plugins/data-quality-observability/.claude-plugin/plugin.json
{
  "name": "data-quality-observability",
  "version": "0.1.2",
  "description": "Data-quality & observability team — agents (data-quality-architect, data-quality-engineer) for the layer answering 'is this data CORRECT, FRESH, COMPLETE, and can we TRUST it?': producer-boundary contracts, validation tests (not-null/unique/accepted-values/referential/distribution), freshness/volume/schema-drift/distribution monitors, threshold vs statistical anomaly detection, data-quality SLAs/SLIs, and data-incident response (triage, quarantine/circuit-breaker, root-cause, backfill). Fluent in dbt tests + dbt-expectations, Great Expectations, Soda, Elementary, managed observability (Monte Carlo, Bigeye, Metaplane), and warehouse-native checks. skills, a knowledge bank (tooling decision tree + 2026 patterns reference), and templates. Distinct from data-platform (ELT/warehouse/BI), analytics-engineering (dbt transforms), data-orchestration (schedules the runs), and data-governance-privacy (policy/PII/lineage) — this is the trust/quality layer over all of them. Requires ravenclaude-core@>=0.7.0.",
  "author": {
    "name": "Matt Corbett"
  },
  "homepage": "https://github.com/mcorbett51090/RavenClaude",
  "license": "MIT",
  "keywords": [
    "data-quality",
    "data-observability",
    "data-contracts",
    "great-expectations",
    "soda",
    "dbt-tests",
    "elementary",
    "freshness",
    "anomaly-detection",
    "schema-drift",
    "data-sla",
    "data-incident"
  ],
  "requires": {
    "plugins": [
      "ravenclaude-core@>=0.7.0"
    ]
  }
}

For maintainers

If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.

[data-quality-observability on Agent Plugins Marketplace](https://pluginsmp.com/plugins/data-quality-observability)