data-specification — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited data-specification (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Write the data specification before writing pipeline code. The spec should define business intent, source and destination expectations, quality rules, and success criteria so the agent is not forced to guess.
Do not use this for trivial spelling fixes or non-behavioral documentation edits.
Include:
If the spec cannot answer frequency, grain, keys, slowly changing behavior, or null handling, pause and ask.
A data change without a written spec becomes tribal knowledge.
| Rationalization | Reality |
|---|---|
| "We just need the table built quickly." | The wrong grain or contract creates expensive downstream rework. |
| "We can infer the business metric later." | That usually creates multiple conflicting definitions of the same metric. |
| "The destination schema is enough." | Schedules, freshness, backfills, and access rules matter just as much as columns. |
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.