warehouse-and-schema-design — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited warehouse-and-schema-design (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.
Use this skill when the primary challenge is how data should be modeled for reliable analytics consumption. It helps agents choose good grain, keys, relationships, and serving patterns so downstream work stays understandable and performant.
Do not reduce schema design to column naming alone. Good schema design is about behavior, meaning, and query ergonomics.
Clarify:
Common options:
Include:
A perfect logical model that no analyst can use is not successful.
| Rationalization | Reality |
|---|---|
| "We can figure out grain later." | Grain mistakes spread quickly through metrics and dashboards. |
| "A wide table is always easier for analysts." | Very wide tables often hide conflicting grains and unclear semantics. |
| "Normalization is more correct, so we should always prefer it." | Correctness and usability both matter; serving models need intentional trade-offs. |
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.