external-intel-provider-rollout

Name: external-intel-provider-rollout
Availability: InStock
Author: eulga

Replace mock intel providers with live external adapters while preserving scheduler behavior.

Updated Mar 10, 2026

Search Tags:#testing #integration #rollout #external-api #scheduler #intel-provider #provider-status

Ready to run

npx skills add https://github.com/Eulga/discord-heatmap-bot-trading-calendar --skill external-intel-provider-rollout

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: external-intel-provider-rollout
Source: https://github.com/Eulga/discord-heatmap-bot-trading-calendar/tree/main/.agents/skills/external-intel-provider-rollout
Command: npx skills add https://github.com/Eulga/discord-heatmap-bot-trading-calendar --skill external-intel-provider-rollout

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Replaces mock intel providers with live external adapters and keeps the scheduler, status, tests, and docs aligned so teams can validate and roll out real data sources safely.

Core Features & Use Cases

Replace mock intel providers with live external adapters while preserving existing scheduler semantics, status reporting, and test coverage.
Normalize external data to the bot's internal shapes NewsItem, Quote, and EodSummary and maintain a consistent contract across news_briefing, eod_summary, and watch_poll.
Use for env-var driven rollout validation, provider interoperability checks, and documentation alignment during a live integration.

Quick Start

Read the external intel API specs and contextual goals, inspect the current provider interface, identify the in-scope path (news_briefing, eod_summary, or watch_poll), and implement the smallest live-change that preserves scheduler behavior.

Frequently Asked Questions about external-intel-provider-rollout

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

FAQPage Schema

How do I safely replace mock intel providers with live external APIs?▼

To safely replace mock intel providers with live external APIs, swap mock adapters with real data sources while preserving the existing scheduler, status tracking, and test harness. Enforce data mapping to internal shapes and maintain timeouts and retries for validated rollout.

How does provider status tracking work during a live API rollout?▼

Provider status tracking works by recording job and provider states through the set_provider_status function. This mechanism maintains consistent status reporting across news_briefing, eod_summary, and watch_poll paths during live external adapter integration.

What is the best way to normalize external intel data for a scheduling bot?▼

The best way to normalize external intel data is to enforce strict mapping to internal shapes like NewsItem, Quote, and EodSummary. This maintains a consistent data contract across news, markets, and settings components during live integration.

Can I use environment variables to validate external API integration?▼

Yes, you can use environment variables to drive rollout validation for external API integration. This approach allows you to perform provider interoperability checks and documentation alignment safely before completing the live data source rollout.

Why do my external intel adapters break the existing scheduler semantics?▼

External intel adapters break scheduler semantics when the live replacement bypasses existing timeout, retry, and status tracking rules. Preserve these guardrails and map external data to NewsItem, Quote, and EodSummary shapes to prevent scheduler breaks.

Do I need to update tests and runbooks when rolling out live intel providers?▼

Yes, you need to update tests and runbooks when rolling out live intel providers. The process keeps docs aligned and preserves test coverage to validate that real data sources integrate safely with the bot's scheduler and status reporting.