Source Reliability And Extraction Resilience

Community

vaquarkhan

source-reliability-and-extraction-resilience

Guides agents through source reliability and extraction resilience. Use when upstream systems are flaky, slow, rate-limited, late, or operationally unreliable and ingestion behavior must remain safe and observable.

Overview

Publisher	vaquarkhan
Repository	`data-engineering-agent-skills`
Skill name	`source-reliability-and-extraction-resilience`
Stars	60
Forks	8
Bundled files	Instructions only
License	MIT
Links	Skill source Repository Homepage

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 Source Reliability And Extraction Resilience AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

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.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/vaquarkhan/data-engineering-agent-skills/tree/main/skills/source-reliability-and-extraction-resilience
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/vaquarkhan/data-engineering-agent-skills/tree/main/skills/source-reliability-and-extraction-resilience

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

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/source-reliability-and-extraction-resilience .claude/skills/source-reliability-and-extraction-resilience

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Source Reliability And Extraction Resilience 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 Source Reliability And Extraction Resilience 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 Source Reliability And Extraction Resilience 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.

Source Reliability And Extraction Resilience

Overview

Use this skill when the real risk is upstream instability rather than downstream modeling. It helps agents design safe ingestion behavior around outages, late data, flaky responses, inconsistent source states, and operational dependencies.

When to Use

unstable upstream systems
intermittent extraction failures
delayed source availability
rate-limited or timeout-prone sources
ingestion designs that must survive source incidents

Do not assume source availability is constant just because the contract exists.

Workflow

Characterize the upstream failure modes. Include:
- outages
- late availability
- inconsistent snapshots
- timeout behavior
- partial responses
Define safe extraction behavior. Decide:
- retry policy
- timeout handling
- quarantine behavior
- when to fail closed versus publish partial data
Add observability around the source, not only the pipeline.
Bound replay and catchup behavior for upstream recovery scenarios.
Document human-operable recovery steps.

Common Rationalizations

Rationalization	Reality
"The source team says it is reliable."	Reliability claims still need runtime evidence and safe fallback behavior.
"We can just retry more."	More retries can worsen load, mask incidents, or still produce partial bad state.
"Partial data is better than stale data."	That depends on the business contract and must be explicit.

Red Flags

no documented source failure modes
partial-source behavior is undefined
the pipeline can publish partial data without warning
source recovery depends on tribal knowledge

Verification

Upstream failure modes are characterized
Extraction and publish behavior under failure is explicit
Source health is observable separately from downstream success
Recovery and catchup rules are documented

Frequently asked questions

What does the Source Reliability And Extraction Resilience AI skill do?

Why use Source Reliability And Extraction Resilience on TypingMind?

Because you install it once and use it with any model. Source Reliability And Extraction Resilience 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 Source Reliability And Extraction Resilience in TypingMind?

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

Which AI models can use Source Reliability And Extraction Resilience?

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 Source Reliability And Extraction Resilience?

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

Is the Source Reliability And Extraction Resilience 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

Grok

NousResearch

OrganizationPopular

Delegate coding to xAI Grok Build CLI (features, PRs).

Setup Wizard Generator

NousResearch

OrganizationPopular

Generate a bash wizard guiding a human through manual setup.

Mcp Oauth Remote Gateway

NousResearch

OrganizationPopular

Manual OAuth for remote MCP servers on headless gateways.

Serving Llms Vllm

vLLM: high-throughput LLM serving, OpenAI API, quantization.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Source Reliability And Extraction Resilience

Overview

When to Use

Workflow

Common Rationalizations

Red Flags

Verification

Frequently asked questions

Related AI Skills

Set up your own AI workspace now