aps-doc-golden

Document golden layer tables with SCD types, business rules, and data quality scoring.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Specialized documentation for golden layer tables, including SCD types, business rules, metric definitions, and data quality scoring.

Core Features & Use Cases

  • Document SCD type 2 implementations and survivorship logic
  • Define metric calculations and aggregation rules
  • Data quality scoring and governance documentation

Quick Start

Example request: "Document golden layer customer master table".

Frequently Asked Questions about aps-doc-golden

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

FAQPage Schema
How do I document golden layer tables with SCD type implementations?

Document golden layer tables by capturing SCD type implementations, business rules, and metric definitions extracted directly from your codebase. The Skill extracts real SQL, CASE statements, and table schemas to produce authoritative documentation without placeholders, including SCD columns, survivorship logic, and aggregation patterns for customer 360 tables.

What should I include when documenting data quality scoring for golden tables?

Include data quality scoring metrics, governance rules, and aggregation logic specific to your golden data lineage. Document how quality scores are calculated, what thresholds apply, and how they cascade through downstream customer 360 and metric tables to maintain transparency across the data pipeline.

Can I extract metric calculations and aggregation rules from existing SQL code?

Yes. The Skill extracts real SQL, CASE statements, and table schemas directly from your codebase to document metric definitions and aggregation patterns. This produces genuine documentation with actual implementation details rather than generic templates, capturing the exact logic used in production.

Do I need codebase access to document golden layer tables?

Yes, codebase access is required. The Skill needs to extract real SQL artifacts, YAML configurations, and table schemas to produce authoritative documentation. This ensures your golden layer documentation reflects actual implementations and business rules in use, not placeholders.

What's the best way to standardize documentation across multiple golden layer tables?

Use the mandated documentation template that captures SCD implementations, metric definitions, data quality scoring, and aggregation patterns consistently. The template enforces consistent structure across customer 360 tables while accommodating actual SCD types, business rules, and real SQL examples from your codebase.