file-and-partner-feed-ingestion — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited file-and-partner-feed-ingestion (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 ingestion depends on externally delivered files rather than APIs or CDC streams. It helps agents design landing, validation, late-file handling, checksum or manifest controls, replay safety, and publish boundaries for partner-managed feeds.
SFTP, MFT, or shared-bucket file feedsCSV, JSON, XML, or columnar extracts from external partnersDo not assume file ingestion is simple just because the payload arrives in a batch.
Clarify:
Decide:
Include:
Decide how:
Document:
| Rationalization | Reality |
|---|---|
| "It is just a file drop." | File-based feeds often fail through late arrival, partial delivery, duplicate upload, or silent schema drift. |
| "We can validate after loading." | Weak landing controls let corrupt or incomplete partner data flow too far downstream. |
| "If the partner resends the file, we are fine." | Resends without replay-safe handling can create duplicate or conflicting publishes. |
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.