aps-doc-ingestion

Generate ingestion documentation for REST API, database, file, and streaming connectors.

21|24|Updated Oct 21, 2025

Search Tags:#REST #ETL #ingestion #incremental #connectors

Ready to run

npx skills add https://github.com/treasure-data/td-skills --skill aps-doc-ingestion

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: aps-doc-ingestion
Source: https://github.com/treasure-data/td-skills/tree/main/aps-doc-skills/ingestion
Command: npx skills add https://github.com/treasure-data/td-skills --skill aps-doc-ingestion

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Documents ingestion layer patterns, connectors, authentication, rate limits, and incremental strategies.

Core Features & Use Cases

Connector discovery and representation
Authentication patterns and rate limiting
Incremental load and scheduling patterns

Quick Start

Document the ingestion workflow for a REST API source.

Frequently Asked Questions about aps-doc-ingestion

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

FAQPage Schema

How do I document REST API ingestion workflows and connectors?▼

REST API ingestion documentation generates connector specifications, authentication patterns, rate limiting rules, and incremental loading schedules by parsing .dig and .yml configuration files to extract real connector names, table definitions, and connection details into template-ready documentation.

What ingestion patterns does documentation cover for ETL workflows?▼

Ingestion documentation covers authentication methods, rate limiting strategies, incremental load patterns, scheduling configurations, and connector-specific details extracted from codebase definitions to produce accurate, implementation-ready specifications for REST, database, file, and streaming sources.

Can I generate documentation for database and file-based data source connectors?▼

Yes. Documentation generation applies to REST API, database, file, and streaming ingestion workflows, parsing actual datasource definitions and configuration files to document authentication, incremental logic, schedules, and connector names for each source type.

How do I extract incremental loading patterns from connector configurations?▼

Incremental loading documentation is generated by parsing codebase configuration files (.dig, .yml) and datasource definitions to extract incremental logic, scheduling patterns, and connection details, producing specifications that document how each connector implements incremental strategies.

What configuration details are needed to document a connector's authentication and rate limits?▼

Configuration files (.dig, .yml) containing connector definitions, authentication parameters, rate limiting rules, and incremental patterns provide the input; the Skill parses these to produce documentation with real connector names, table specifications, and config-derived authentication and rate-limit details.

Does ingestion documentation work with streaming data sources?▼

Yes. Ingestion documentation generation applies to streaming ingestion workflows alongside REST API, database, and file sources, documenting authentication, rate limiting, incremental patterns, and scheduling for each connector type.