data-source-research

Investigate data sources once and persist reference documents under docs/data-sources.

Updated May 5, 2026
One-click install
npx skills add https://github.com/shakhovskiya-create/shakhoff-claude-marketplace --skill data-source-research
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: data-source-research
Source: https://github.com/shakhovskiya-create/shakhoff-claude-marketplace/tree/main/plugins/solo-sdlc/skills/data-source-research
Command: npx skills add https://github.com/shakhovskiya-create/shakhoff-claude-marketplace --skill data-source-research

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Claude tends to re-investigate unfamiliar data sources across sessions. This skill performs a one-time investigation and writes a permanent reference so future agents read the reference instead of re-researching.

Core Features & Use Cases

  • One-time investigation and permanent reference generation for databases, APIs, file systems, and message queues.
  • Persisted references under a standardized docs/data-sources path to prevent rework in future tasks.
  • Reuse existing references when fresh, and flag references for refresh if stale (e.g., older than 30 days).
  • Triggers automatically when a user mentions a data source, ensuring guidance before coding.

Quick Start

Run this skill before writing code against any new data source to generate and persist a reference document.

Frequently Asked Questions about data-source-research

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

FAQPage Schema
How do I create a permanent reference document for an unfamiliar database or API?

Generate a permanent reference document by investigating the data source once and persisting the findings under a standardized docs/data-sources path. This prevents future agents from re-researching the same unfamiliar database or API.

Why does my agent keep re-investigating the same data source across sessions?

Agents re-investigate the same data source across sessions because no permanent reference document exists. Writing a persisted reference ensures future tasks read the existing documentation instead of repeatedly researching the data source.

When do I need to refresh stale data source documentation?

Refresh stale data source documentation when references become outdated, such as exceeding a 30-day threshold. The skill flags stale references for refresh to ensure development begins with accurate data source guidance.

Can I generate reference documents for file systems and message queues too?

Yes, you can generate reference documents for file systems and message queues. The skill performs one-time investigation and permanent reference generation for databases, APIs, file systems, and message queues alike.

What is the best way to prevent rework when writing code against new APIs?

The best way to prevent rework when writing code against new APIs is to run a one-time investigation before development begins. This generates a permanent reference document that future agents read instead of re-researching the data source.