cdc-and-incremental-loading — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited cdc-and-incremental-loading (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 system changes data over time and full reloads are not the right answer. It helps agents design safe incremental behavior with clear watermarks, merge rules, deduplication, and replay semantics.
Do not use this when a bounded full refresh is simpler and operationally safer.
Include:
Typical options:
Record:
Deduplication and late-data handling should be first-class logic.
Incremental pipelines that cannot be replayed safely are incomplete.
| Rationalization | Reality |
|---|---|
| "We can just use updated_at as the watermark." | Timestamps alone often miss late changes, clock skew, or delete semantics. |
| "Duplicates are rare enough." | Rare duplicates are still expensive when they affect published metrics. |
| "We can rebuild everything if something goes wrong." | Large backfills are often slow, expensive, or operationally risky. |
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.