collect-initial-data

Document data acquisition and initial inventories for CRISP-DM workflows.

Updated Mar 20, 2026
One-click install
npx skills add https://github.com/thbraet/claude-template --skill collect-initial-data
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: collect-initial-data
Source: https://github.com/thbraet/claude-template/tree/main/skills/collect-initial-data
Command: npx skills add https://github.com/thbraet/claude-template --skill collect-initial-data

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Skill helps teams document how data is acquired, inventory received datasets, and record selection rationale, producing a structured data collection report.

Core Features & Use Cases

  • Generate an acquisition log, an initial data inventory, and a loading plan to support CRISP-DM 2.1 Data Understanding.
  • Produce artifacts to guide data onboarding, governance, and reproducibility for data science projects.

Quick Start

Create a complete data collection report for the current project.

Frequently Asked Questions about collect-initial-data

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

FAQPage Schema
How do I document initial data collection for a CRISP-DM project?

To document initial data collection for a CRISP-DM project, you generate an acquisition log, initial data inventory, and storage plans under docs/crisp-dm/2-data-understanding/ and notebooks/ to ensure reproducibility. This provides structured governance artifacts for onboarding datasets.

What is a data inventory and why do I need one for data understanding?

A data inventory is a structured record of received datasets, selection rationales, and loading plans generated during CRISP-DM phase 2. You need it to enable reproducible data science workflows, guide data onboarding, and establish governance for downstream analysis.

How do I create a data acquisition log and loading plan for data science workflows?

You create a data acquisition log and loading plan by profiling available datasets and documenting selection rationales. The process outputs notebook and docs artifacts that capture how data is acquired and stored, ensuring the data onboarding process is reproducible.

Do I need existing CRISP-DM documentation to generate a data collection report?

Yes, generating a data collection report requires reading existing CRISP-DM docs from phases 1.1 through 1.3. This prerequisite ensures the acquisition log and data inventory align with established business objectives and project context.

What's the best way to profile datasets and record selection rationale for data onboarding?

The best way to profile datasets and record selection rationale is to process available datasets through a structured CRISP-DM workflow. This generates a data collection report containing acquisition logs and inventory artifacts that guide governance and reproducibility.

Can I use this approach to inventory data across different data science projects?

Yes, you can inventory data across different data science projects because the approach applies generically to CRISP-DM phase 2. It produces standardized acquisition logs and storage plans that support reproducible workflows regardless of the specific domain.