Data Platform Disaster Recovery And Business Continuity

Community

vaquarkhan

data-platform-disaster-recovery-and-business-continuity

Guides agents through disaster recovery and business continuity planning for data platforms. Use when defining region or account failover, backup and restore, RTO or RPO targets, control-plane recovery, or restore drills for pipelines, warehouses, lakehouses, and publish surfaces.

Overview

Publisher	vaquarkhan
Repository	`data-engineering-agent-skills`
Skill name	`data-platform-disaster-recovery-and-business-continuity`
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 Data Platform Disaster Recovery And Business Continuity 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/data-platform-disaster-recovery-and-business-continuity
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/data-platform-disaster-recovery-and-business-continuity

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/data-platform-disaster-recovery-and-business-continuity .claude/skills/data-platform-disaster-recovery-and-business-continuity

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

Use it in TypingMind

Enable Data Platform Disaster Recovery And Business Continuity 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 Data Platform Disaster Recovery And Business Continuity 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 Data Platform Disaster Recovery And Business Continuity 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.

Data Platform Disaster Recovery And Business Continuity

Overview

Use this skill when the question is how the data platform survives major failure, not only how one incident is handled. It helps agents design recovery objectives, backup and restore paths, control-plane recovery, failover decisions, and repeatable restore drills for data systems.

When to Use

defining RTO and RPO for critical datasets or platform services
planning region, account, or environment failover
validating backup and restore behavior for warehouses, lakes, or stateful processors
designing business continuity for shared data products and critical publish paths
running recovery drills before a real outage forces them

Do not confuse incident handling with disaster recovery planning. Disaster recovery is the plan for major platform loss or sustained unavailability.

Workflow

Classify the critical services and data products. Identify:
- critical datasets
- control-plane dependencies
- orchestration and metadata services
- downstream consumer and business impact
Define recovery objectives. Include:
- RTO
- RPO
- acceptable degraded mode
- mandatory publish protections during failover
Map recovery assets and dependencies. Cover:
- backups and snapshots
- checkpoint or incremental state
- orchestration definitions
- secrets and access paths
- lineage and metadata services
- validation and reconciliation controls after restore
Choose the recovery strategy. Options may include:
- restore in place
- warm standby
- cold standby
- cross-region or cross-account failover
- consumer-facing degraded mode with blocked publish
Prove the recovery path. Run drills for:
- restore time
- checkpoint continuity
- publish blocking and reopen criteria
- reconciliation after restore
- ownership and escalation behavior

Common Rationalizations

Rationalization	Reality
"The cloud provider already handles availability."	Provider uptime does not replace dataset restore, metadata recovery, or publish-safe failover design.
"We have backups, so we are covered."	Untested backups and undefined restore ownership do not prove business continuity.
"We can work out the failover steps during an outage."	Major outages are the worst time to discover recovery dependencies or missing permissions.

Red Flags

no named RTO or RPO exists for critical data products
backup inventory ignores metadata, orchestration, or incremental state
failover is described without validation or reconciliation after restore
publish behavior during degraded mode is undefined
recovery drills have never been executed

Verification

Critical data products and services have explicit recovery objectives
Backup, restore, and dependency recovery paths are documented
Recovery strategy matches business impact and platform constraints
Restore drills validate time, correctness, and publish protection
Ownership and escalation paths are clear during major outage scenarios

Frequently asked questions

What does the Data Platform Disaster Recovery And Business Continuity AI skill do?

Why use Data Platform Disaster Recovery And Business Continuity on TypingMind?

Because you install it once and use it with any model. Data Platform Disaster Recovery And Business Continuity 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 Data Platform Disaster Recovery And Business Continuity in TypingMind?

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

Which AI models can use Data Platform Disaster Recovery And Business Continuity?

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 Data Platform Disaster Recovery And Business Continuity?

As many as you like. As long as a model supports skills, you can use Data Platform Disaster Recovery And Business Continuity with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Data Platform Disaster Recovery And Business Continuity 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

Discord User Post

openclaw

OrganizationPopular

Post an approved message as the logged-in Discord user through the Discord desktop app. Use for release announcements or other direct user-authored Discord posts; not for OpenClaw channel sends, bots,…

Test Audit

Invoke whenever writing, changing, reviewing, or sweeping tests. Authoring gate for new tests plus audit workflow for low-value, implementation-coupled, or duplicative tests and the test-only…

Feishu Perm

Feishu collaborator and permission workflows. Activate when the user explicitly asks to inspect or change sharing, permissions, or collaborators.

Block Kit

Use proactively for structured or interactive Slack replies, and when asked to author or validate native Slack Block Kit JSON.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Data Platform Disaster Recovery And Business Continuity

Overview

When to Use

Workflow

Common Rationalizations

Red Flags

Verification

Frequently asked questions

Related AI Skills

Set up your own AI workspace now