profile-data

Profile client data tables and generate per-table markdown reports.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/lenlla/one_shot_build --skill profile-data
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: profile-data
Source: https://github.com/lenlla/one_shot_build/tree/main/skills/profile-data
Command: npx skills add https://github.com/lenlla/one_shot_build --skill profile-data

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the repetitive and error-prone task of creating per-table data profiling reports so analysts and engineers can quickly understand table contents, row and column counts, and basic data characteristics without manual inspection.

Core Features & Use Cases

  • Per-table Markdown Reports: Produces data-profile-<table>.md files for each specified table in the project context.
  • Conflict Resolution: Detects existing profiles and prompts the user to overwrite, create a new version, or skip, enabling safe iterative profiling.
  • Profiler Sub-Agent Orchestration: Dispatches a profiler sub-agent per table, waits for completion, and collects TABLE, OUTPUT, ROW_COUNT, and COLUMN_COUNT for summary reporting.
  • Use Case: Run profiling across multiple catalog.schema.table datasets during project setup to generate baseline data documentation and inform modeling decisions.

Quick Start

Profile the tables catalog.sales.transactions and catalog.crm.users and save per-table profiles to the project context.

Frequently Asked Questions about profile-data

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

FAQPage Schema
How do I automate data profiling for multiple tables?

Automated data profiling dispatches a profiler sub-agent per catalog.schema.table dataset, sequentially generating per-table markdown reports that record row counts, column counts, and table characteristics.

What is a per-table data profile report?

A per-table data profile report is a markdown file documenting a specific table's contents, row and column counts, and basic data characteristics to establish baseline data documentation for modeling decisions.

How do I handle existing data profiling reports when re-running profiling?

When existing data profiles are detected, the profiling workflow prompts you with conflict resolution options to either overwrite the existing report, create a new version, or skip the table entirely.

Do I need a specific project directory to generate table reporting markdown files?

Yes, generating table reporting markdown files requires access to the kyros-agent-workflow/docs/context/ directory to save the per-table data profile outputs.

Can I profile several catalog.schema.table datasets at once?

Yes, you can profile several catalog.schema.table datasets at once by specifying multiple tables, which triggers sequential sub-agent processing and collects summary metrics for each table.

What are the limitations of sequential data profiling sub-agents?

Sequential data profiling sub-agents process tables one at a time, meaning profiling large numbers of datasets may take longer, and the workflow requires pausing to await each sub-agent's completion before proceeding.