design-data-sources

Map external data sources with trust levels, freshness thresholds, and fallback chains.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/SujinHwang27/agent-os-lab --skill design-data-sources
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-data-sources
Source: https://github.com/SujinHwang27/agent-os-lab/tree/main/agent-os-factory-v2.0/.claude/skills/design-data-sources
Command: npx skills add https://github.com/SujinHwang27/agent-os-lab --skill design-data-sources

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Mapping external data sources and establishing trust, freshness, verification, and fallback rules for an agent OS.

Core Features & Use Cases

  • Inventory data sources and assess accessibility and reliability.
  • Define per-source trust levels, freshness thresholds, and verification steps.
  • Design robust fallback chains and staleness handling for mission-critical tasks.

Quick Start

Create a map of all external data sources the OS will query, including trust levels and verification rules.

Frequently Asked Questions about design-data-sources

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

FAQPage Schema
How do I map external data sources for an agent OS?

Assigning trust levels to external data sources involves evaluating accessibility and reliability, then defining usage scopes, verification rules, and data freshness thresholds to ensure the OS only acts on trusted insights.

How do I handle external data outages in an automated workflow?

Handling external data outages requires designing robust fallback chains and staleness handling rules, ensuring mission-critical tasks maintain operational continuity when primary data sources fail.

What are data freshness thresholds and verification rules?

Data freshness thresholds define acceptable staleness limits for queried information, while verification rules specify the validation steps required to confirm external data accuracy before an OS relies on it for insights.

Do I need to define integration constraints for every external data source?

Yes, capturing per-source integration constraints for every external data source is required to define scope, establish usage scenarios, and support reproducible, automated design workflows without unexpected failures.