api-and-saas-ingestion-patterns — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited api-and-saas-ingestion-patterns (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 source system is an external API or SaaS platform rather than a database or file drop. It helps agents design reliable extraction, pagination, throttling, auth handling, and backfill-safe ingestion contracts.
Do not treat APIs like static tables. They change behavior, availability, and limits over time.
Include:
Handle:
Decide whether the source supports:
API sources often need raw response retention for incident diagnosis.
| Rationalization | Reality |
|---|---|
| "We can just loop through pages." | Pagination bugs and retry gaps often cause silent data loss. |
| "The vendor API is stable enough." | SaaS APIs change rate limits, fields, and semantics more often than teams expect. |
| "If a request fails, we can rerun later." | Without windowing and idempotency rules, reruns can miss or duplicate data. |
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.