disaster-recovery-bcp

Develop and execute disaster recovery workflows for quantitative trading systems.

Updated Feb 10, 2026
One-click install
npx skills add https://github.com/GhostOf0days/codex-quant-skills --skill disaster-recovery-bcp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: disaster-recovery-bcp
Source: https://github.com/GhostOf0days/codex-quant-skills/tree/main/disaster-recovery-bcp
Command: npx skills add https://github.com/GhostOf0days/codex-quant-skills --skill disaster-recovery-bcp

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pandas, argparse, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the critical need for robust disaster recovery and business continuity planning in quantitative trading systems, ensuring minimal downtime and data integrity during disruptions.

Core Features & Use Cases

  • Performance Monitoring: Tracks stage-level latency, jitter, and throughput under stress.
  • Automated Diagnostics: Runs scripts to collect and summarize critical performance metrics.
  • Controlled Rollout: Provides a playbook for verifying recovery behavior before production deployment.
  • Use Case: When a production trading system experiences unexpected latency spikes or connectivity issues, this Skill can be activated to run diagnostics, analyze failure points, and verify recovery procedures.

Quick Start

Use the disaster-recovery-bcp skill to run diagnostics on the input data file 'trade_data.csv' and save the results to 'diagnostics.json'.

Frequently Asked Questions about disaster-recovery-bcp

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I monitor stage-level latency and jitter in quantitative trading systems?

You can monitor stage-level latency and jitter by running automated diagnostic scripts that collect and summarize performance metrics from trade data. This Skill instruments pipeline stages to track throughput stability and latency decomposition under stress conditions.

How do I verify disaster recovery procedures for a production trading system?

Disaster recovery procedures for a production trading system are verified using a controlled rollout playbook that tests recovery behavior before deployment. This Skill executes workflows to ensure minimal downtime and data integrity during connectivity issues or latency spikes.

What is stage-level latency decomposition and when do I need it for trading failover?

Stage-level latency decomposition breaks down the total execution time across individual pipeline components to pinpoint bottlenecks. You need it for trading failover when experiencing packet-loss, network path degradation, or resource saturation that impacts business continuity.

Can I use pandas to analyze performance diagnostics for trading system failover?

Yes, this Skill uses pandas to process input trade data files and run diagnostics that summarize critical performance metrics. The analysis outputs are saved to JSON format to support trading system failover verification and business continuity planning.

What is the best way to instrument network paths for packet-loss recovery in trading systems?

The best way to instrument network paths for packet-loss recovery is to optimize routing and monitor resource saturation across pipeline stages. This Skill defines explicit latency budgets and verifies packet-loss recovery behavior to maintain trading system resilience.

What are the limitations of running disaster recovery diagnostics on trade data CSV files?

Limitations of running disaster recovery diagnostics on CSV files include potential bottlenecks from parsing large datasets and reliance on static input data rather than live streams. This Skill processes CSV inputs using pandas and outputs static JSON summaries for offline recovery verification.