# Data Verification Skill

Use this skill to verify that reports, Excel files, and lineage claims match code and live or historical data.

## Goal

Assign evidence-backed confidence to each lineage claim.

## Verification Status

- `verified`: code and DB/sample evidence both checked.
- `code_verified`: code checked, DB not checked.
- `db_verified`: DB checked, code path not fully traced.
- `partial`: only some sources checked.
- `stale`: previously true but live data drifted.
- `blocked`: cannot verify because of missing access, client, credentials, or environment.

## Procedure

1. Prefer read-only DB queries.
2. Query metadata before row values.
3. Verify row counts, schema fields, statuses, current flags, and sample IDs.
4. Compare live data with existing reports.
5. Record drift explicitly.
6. Never expose secret values.

## Output Sections

- Verification scope
- DB checks
- Code checks
- Sample checks
- Drift findings
- Blockers
- Evidence log