File And Partner Feed Ingestion logo

File And Partner Feed Ingestion

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

Overview

Publishervaquarkhan
Repositorydata-engineering-agent-skills
Skill namefile-and-partner-feed-ingestion
Stars
60
Forks
8
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by vaquarkhan on GitHub. Read the source before you install it.

Installation

Install the File And Partner Feed Ingestion AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/vaquarkhan/data-engineering-agent-skills/tree/main/skills/file-and-partner-feed-ingestion
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/vaquarkhan/data-engineering-agent-skills.git /tmp/data-engineering-agent-skills
mkdir -p .claude/skills
cp -r /tmp/data-engineering-agent-skills/skills/file-and-partner-feed-ingestion .claude/skills/file-and-partner-feed-ingestion
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable File And Partner Feed Ingestion in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads File And Partner Feed Ingestion on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so File And Partner Feed Ingestion is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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

RationalizationReality
"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

Frequently asked questions

What does the File And Partner Feed Ingestion AI skill do?

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.

Why use File And Partner Feed Ingestion on TypingMind?

Because you install it once and use it with any model. File And Partner Feed Ingestion is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install File And Partner Feed Ingestion in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/vaquarkhan/data-engineering-agent-skills/tree/main/skills/file-and-partner-feed-ingestion. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use File And Partner Feed Ingestion?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with File And Partner Feed Ingestion?

As many as you like. As long as a model supports skills, you can use File And Partner Feed Ingestion with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the File And Partner Feed Ingestion AI skill free?

Yes. It is published on GitHub by vaquarkhan under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇