aps-doc-staging

Document Presto/Trino and Hive staging transformations with SQL examples.

21|24|Updated Oct 21, 2025
One-click install
npx skills add https://github.com/treasure-data/td-skills --skill aps-doc-staging
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aps-doc-staging
Source: https://github.com/treasure-data/td-skills/tree/main/aps-doc-skills/staging
Command: npx skills add https://github.com/treasure-data/td-skills --skill aps-doc-staging

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Expert documentation for staging transformations, including engine detection, transformation rules, PII handling, and deduplication strategies.

Core Features & Use Cases

  • Engine detection (Presto/Trino vs Hive)
  • Transformation rules and PII handling
  • Deduplication and data quality checks

Quick Start

Document the staging transformation for a sample dataset.

Frequently Asked Questions about aps-doc-staging

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

FAQPage Schema
How do I generate documentation for staging transformation layers?

Staging transformation documentation captures your extraction rules, PII handling, deduplication strategies, and data quality validations. This Skill analyzes your actual Presto/Trino or Hive SQL from .sql, .dig, and .yml files to produce thorough, engine-specific documentation with working examples and real table and column names.

Can I document staging transformations for both Presto and Hive workflows?

Yes. This Skill detects your query engine—Presto, Trino, or Hive—and generates documentation tailored to each engine's staging patterns, transformation rules, PII handling approaches, and deduplication methods, with working SQL examples specific to your workflow.

What does the Skill extract from my transformation files?

The Skill reads .sql, .dig, and .yml files to extract transformation rules, PII masking or removal logic, deduplication strategies, data quality checks, and generates codebase-verified documentation with actual table and column names and executable SQL examples.

How do I ensure data quality documentation includes PII handling?

Provide your staging transformation files (.sql, .dig, .yml). The Skill automatically identifies and documents PII handling strategies, deduplication approaches, and quality validations embedded in your transformation logic, then outputs comprehensive documentation with working examples.

Do I need to manually write transformation documentation?

No. This Skill auto-generates staging transformation documentation by analyzing your actual SQL code and configuration files, extracting transformation rules, PII handling, deduplication logic, and data quality checks, so your documentation stays aligned with your codebase.

What output format does the documentation provide?

The Skill produces thorough documentation covering engine type, transformation rules, PII handling strategies, deduplication methods, and data quality validations—all grounded in real table names, column references, and working SQL examples extracted from your codebase.