aps-doc-id-unification

Generate documentation for ID unification workflows from .dig and .yml files.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of comprehensive, reference-grade documentation for ID unification systems, covering identity resolution algorithms, merge rules, entity graphs, and multi-workflow orchestration.

Core Features & Use Cases

  • Full workflow documentation: Capture and document all workflows (prep, unification, enrichment) with real names and configurations.
  • Match rules & merges: Document how records are matched, merged, and how canonical IDs are derived.
  • Output templates & references: Produce structured outputs suitable for Confluence and Markdown, with references to code paths and data models.
  • Use Case: Document an end-to-end ID unification pipeline used to merge customer identifiers across systems and maintain data provenance.

Quick Start

Provide the codebase path to ID unification workflows and the destination documentation path. This will guide generation of real, actionable docs based on actual .dig and .yml files.

Frequently Asked Questions about aps-doc-id-unification

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

FAQPage Schema
How do I document ID unification workflows across prep, unification, and enrichment stages?

ID unification documentation captures the complete pipeline by extracting real workflow names, merge strategies, and match rules from your .dig and .yml configuration files. The Skill generates structured reference docs detailing how records are matched, merged, and how canonical IDs are derived across all three stages.

What should I include in documentation for identity resolution merge rules?

Merge rules documentation should specify match keys, matching criteria, conflict resolution logic, and the canonical ID derivation process. This Skill extracts those details directly from your workflow configurations and produces reference-grade docs suitable for Confluence or Markdown with code path references.

Can I generate documentation for multi-workflow ID unification orchestration?

Yes. The Skill documents end-to-end orchestration across multiple workflows, including prep parameter files, runtime configurations, table names, and how workflows interact. It produces comprehensive reference material covering the complete ID unification system architecture.

What access do I need to generate ID unification documentation?

You need access to the codebase containing your actual .dig workflow files, .yml configuration files, and prep parameter files. The Skill reads these directly to extract real keys, workflow names, table names, and runtime settings for accurate documentation generation.

What output formats does ID unification documentation support?

The Skill produces structured outputs in both Confluence and Markdown formats, with embedded references to code paths and data models. This enables easy integration into documentation systems and version control while maintaining traceability to your actual workflow code.