Skip to main content
The /armor:quality skill helps you create and manage data quality checks including metrics and validity rules.

Usage

Or ask naturally:
  • “Add a null check for the email column”
  • “Create a row count metric for orders”
  • “What quality checks exist for this table?”

Quality Check Types

Metrics

Track quantitative measurements over time:
  • row_count: Number of rows
  • null_rate: Percentage of null values
  • distinct_count: Unique value count
  • freshness: Time since last update

Validity Rules

Validate data integrity:
  • NOT_NULL: Column must not contain nulls
  • UNIQUE: Values must be unique
  • ACCEPTED_VALUES: Values must be in allowed list
  • REGEX: Values must match pattern

Example Usage

Add Null Check

Create Row Count Metric

Check Quality Status

Common Questions

When should I use a metric versus a validity rule?

Use a metric when you want to track a number over time and alert on anomalies (null rate climbing from 0.1% to 5%). Use a validity rule when you want a hard pass/fail check on every run (email must match a regex, status must be in an allowed list).

Profile

Table statistics

Coverage

Find gaps in monitoring