hybrid-data-patterns

Classify data sources into raw or simple storage strategies.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/bennybennison/agent-toolkit --skill hybrid-data-patterns
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hybrid-data-patterns
Source: https://github.com/bennybennison/agent-toolkit/tree/main/skills/hybrid-data-patterns
Command: npx skills add https://github.com/bennybennison/agent-toolkit --skill hybrid-data-patterns

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill helps teams manage projects that contain both critical, non‑re‑fetchable data and disposable, easily refreshed data by providing a clear strategy to store each source appropriately.

Core Features & Use Cases

  • Decision Tree: Guides you through questions to choose raw or simple storage.
  • Source Registry: Defines each data source’s storage strategy, rationale, and retention.
  • Ingestion Routing: Automatically directs incoming payloads to the raw repository or simple CRUD layer based on the registry.
  • Migration Path: Step‑by‑step process to upgrade a simple source to raw storage without downtime.

Quick Start

Ask the hybrid-data-patterns skill to classify a new data source and generate its storage configuration.

Frequently Asked Questions about hybrid-data-patterns

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

FAQPage Schema
How do I manage mixed data criticality when some sources are non-re-fetchable and others are easily refreshed?

A hybrid data storage pattern handles mixed data criticality by routing non-re-fetchable payloads to raw JSON archives and storing re-pullable data via simple CRUD repositories, ensuring consistent retention and source handling.

When should I use raw JSON archives instead of simple CRUD model storage?

Use raw JSON archives for non-re-fetchable data that cannot be pulled again, and use simple CRUD repositories for disposable data that is easily refreshed, guided by a decision tree to classify each source.

How do I set up a source registry to route data ingestion automatically?

Set up a source registry by defining each data source's storage strategy, rationale, and retention rules, which automatically directs incoming payloads to either the raw repository or simple CRUD layer during ingestion routing.

Can I migrate a data source from simple storage to raw storage without downtime?

Yes, you can upgrade a simple data source to raw storage without downtime by following a step-by-step migration path that transitions the storage strategy while maintaining continuous data access.

What do I need to implement hybrid data storage patterns for my project?

Implementing a hybrid data storage pattern requires defining a source registry, setting up a raw storage layer for JSON archives, and configuring simple CRUD repositories to enforce consistent data handling.