# File And Partner Feed Ingestion

> Guides agents through file-based and partner-feed ingestion workflows. Use when landing data from SFTP, managed file transfer, shared buckets, recurring flat files, manifests, or externally supplied feeds that need validation, replay safety, and publish discipline.

- **Type:** Skill
- **Install:** `agentstack add skill-vaquarkhan-data-engineering-agent-skills-file-and-partner-feed-ingestion`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [vaquarkhan](https://agentstack.voostack.com/s/vaquarkhan)
- **Installs:** 0
- **Category:** [Developer Tools](https://agentstack.voostack.com/c/developer-tools)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [vaquarkhan](https://github.com/vaquarkhan)
- **Source:** https://github.com/vaquarkhan/data-engineering-agent-skills/tree/main/skills/file-and-partner-feed-ingestion
- **Website:** https://vaquarkhan.github.io/data-engineering-agent-skills/

## Install

```sh
agentstack add skill-vaquarkhan-data-engineering-agent-skills-file-and-partner-feed-ingestion
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# File And Partner Feed Ingestion

## Overview

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.

## When to Use

- onboarding `SFTP`, MFT, or shared-bucket file feeds
- ingesting recurring `CSV`, `JSON`, `XML`, or columnar extracts from external partners
- validating manifests, checksums, control totals, or arrival windows
- handling late, duplicate, partial, or corrected file deliveries
- defining replay-safe landing and publish behavior for externally supplied data

Do not assume file ingestion is simple just because the payload arrives in a batch.

## Workflow

1. Define the feed contract.
   Clarify:
   - file format and expected schema
   - naming convention
   - arrival schedule or SLA
   - manifest, checksum, or control-total expectations
   - ownership and contact path for the partner or source team

2. Design the landing boundary.
   Decide:
   - where raw files land
   - what metadata is captured
   - how duplicates are detected
   - how partial or corrupt deliveries are quarantined

3. Validate before publish.
   Include:
   - schema and required-field checks
   - checksum or manifest validation
   - row-count or control-total validation
   - late-file and missing-file detection

4. Make replay behavior explicit.
   Decide how:
   - corrected files are handled
   - duplicate files are ignored or reconciled
   - replay windows are bounded
   - downstream publishes stay protected until validation passes

5. Define failure and escalation behavior.
   Document:
   - who gets alerted
   - what blocks publish
   - how the partner is contacted
   - how recovery evidence is recorded

## Common Rationalizations

| 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. |

## Red Flags

- file naming and arrival expectations are undocumented
- manifest, checksum, or control totals are ignored
- duplicate and corrected file behavior is undefined
- late or missing files do not create actionable alerts
- downstream publish opens before the landing validations complete

## Verification

- [ ] The feed contract defines format, arrival, and ownership expectations
- [ ] Landing, quarantine, and duplicate-handling rules are explicit
- [ ] Validation covers schema, completeness, and control totals where relevant
- [ ] Replay and corrected-file behavior are documented before go-live
- [ ] Failure handling and partner escalation paths are operationally clear

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [vaquarkhan](https://github.com/vaquarkhan)
- **Source:** [vaquarkhan/data-engineering-agent-skills](https://github.com/vaquarkhan/data-engineering-agent-skills)
- **License:** MIT
- **Homepage:** https://vaquarkhan.github.io/data-engineering-agent-skills/

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-vaquarkhan-data-engineering-agent-skills-file-and-partner-feed-ingestion
- Seller: https://agentstack.voostack.com/s/vaquarkhan
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.