Expert documentation generation for ingestion layers. Automatically detects connector types (REST API, Database, File, Streaming), documents authentication patterns, rate limiting strategies, and incremental load patterns. Use when documenting data source ingestion workflows.
47
48%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Risky
Do not use without reviewing
Optimize this skill with Tessl
npx tessl skill review --optimize ./aps-doc-skills/ingestion/SKILL.mdSpecialized skill for generating comprehensive documentation for ingestion layers. Automatically detects and documents connector-specific patterns, authentication methods, rate limiting, and incremental strategies.
Use this skill when:
Example requests:
"Document the Klaviyo ingestion workflow"
"Create documentation for Salesforce API ingestion"
"Document all data sources in the ingestion layer"
"Generate ingestion documentation following this template: [Confluence URL]"WITHOUT codebase access = NO documentation. Period.
If no codebase access provided:
I cannot create technical documentation without codebase access.
Required:
- Directory path to ingestion workflows
- Access to .dig, .yml configuration files
Without access, I cannot extract real table names, connectors, or incremental logic.
Provide path: "Code is in /path/to/ingestion/"Before proceeding:
Documentation MUST contain:
NO generic placeholders. Only real, extracted data.
This skill automatically detects and documents:
REST API Connectors:
Detects from configuration:
- endpoint URLs (https://api.example.com/v1/...)
- HTTP methods (GET, POST, PUT)
- Pagination patterns (offset, cursor, page number)
- Response format (JSON, XML)
Documents:
- API endpoint structure
- Request/response examples
- Pagination strategy
- Response handlingDatabase Connectors:
Detects from configuration:
- JDBC connection strings
- Query-based ingestion patterns
- Incremental query logic
- Connection parameters
Documents:
- Connection configuration
- Source queries
- Data type mappings
- Isolation levelsFile-Based Connectors:
Detects from configuration:
- S3/GCS bucket paths
- File patterns (*.csv, *.json, *.parquet)
- Compression formats (gzip, zip, snappy)
- File naming conventions
Documents:
- Bucket/path structure
- File format specifications
- Decompression logic
- File processing orderStreaming Connectors:
Detects from configuration:
- Kafka topics/consumer groups
- Kinesis streams
- Partition strategies
- Offset management
Documents:
- Topic/stream configuration
- Consumer settings
- Checkpoint mechanisms
- Backpressure handlingOAuth 2.0:
Detects:
- Token endpoint URLs
- Client ID references
- Scope definitions
- Token refresh logic
Documents (securely):
- Authentication flow
- Token lifecycle
- Scope requirements
- Refresh strategy
(WITHOUT exposing secrets)API Key Authentication:
Detects:
- API key header names
- Key rotation patterns
- Rate limit tiers
Documents:
- Header configuration
- Key rotation schedule
- Usage tier limitsBasic Authentication:
Detects:
- Username/password references
- Credential storage patterns
Documents:
- Authentication method
- Credential managementService Account / JWT:
Detects:
- Service account files
- JWT token generation
- Key expiration
Documents:
- Service account setup
- Token generation process
- Key rotation policyDetects from workflow:
- Request throttling (requests per second/minute)
- Retry backoff strategies (exponential, linear)
- Concurrent request limits
- Circuit breaker patterns
Documents:
- Rate limit thresholds
- Backoff algorithm
- Retry configuration
- Concurrent connection limitsTimestamp-Based:
Detects:
- updated_at, modified_at, created_at fields
- Timestamp comparison logic
- Watermark tracking
Documents:
- Incremental field name
- Timestamp format
- Watermark storage
- Lookback windowSequence-Based:
Detects:
- Auto-increment ID fields
- Sequence tracking
- Max ID queries
Documents:
- Sequence field name
- High-water mark logic
- Gap handlingFull Reload:
Detects:
- No incremental field
- Full table scans
- Truncate-and-load patterns
Documents:
- Full reload schedule
- Data volume considerations
- Performance impactFollow this EXACT structure (analyzed from production examples):
## Overview
{Brief description of ingestion layer}
### Project Structure
{Directory tree from actual codebase}
## Main Ingestion Runner
**Workflow File**: ingestion_runner.dig
{Schedule, tasks, parallelization}
## Database Configuration
{Table with databases and purposes}
## Monitoring and Logging
{SQL queries for status checks}
## Individual Source Documentation
{Links to child pages}# {Source} Ingestion
## Overview
**Workflow Files:**
- {source}_ingest_inc.dig - Incremental
- {source}_ingest_hist.dig - Historical (if exists)
{Description}
**Data Source Type**: {type}
**Connector**: {connector name}
**Source System**: {system}
**Target Database**: {database}
---
## Configuration Files
{Table with file types and purposes}
---
## Active Tables (Incremental)
{Table with all incremental tables from datasources.yml}
## Active Tables (Historical)
{Table with all historical tables - if exists}
---
## Incremental Workflow Process
### Step 1: Log Ingestion Start
{Code snippet from workflow}
### Step 2: Setup Table and Time
{Explain create table logic + get last time logic}
### Step 3: Load Incremental Data
{Code snippet + query example}
### Step 4: Log Ingestion Success
{Code snippet}
---
## Historical Workflow Process
{Similar steps for historical if exists}
---
## Parallelization
{Explain _parallel settings and concurrency}
---
## Error Handling
{_error block from workflows}
---
## Authentication
{td_authentication_id reference}
---
## Data Flow Diagram
{Simple text diagram showing source → target}
---
## Incremental Logic
{Explain first run vs subsequent runs}
---
## Timestamp Format
{Document actual format from configs}
---
## Monitoring and Troubleshooting
{SQL queries for checking status, errors}
---
## Key Features
{Bullet list of main capabilities}
---
## Adding New Tables
{Step-by-step guide with real examples}
---
## Configuration Reference
{Sample datasource config + load config}
---
## Summary
{Brief recap of workflow capabilities}This skill generates production-ready ingestion documentation by:
Key capability: Transforms codebase into professional Confluence documentation.
79bb9b8
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.