data-join

Join two tabular datasets on a shared key using qsv joinp and sqlp.

3.7k|104|Updated Dec 11, 2020
One-click install
npx skills add https://github.com/dathere/qsv --skill data-join
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: data-join
Source: https://github.com/dathere/qsv/tree/main/.claude/skills/skills/data-join
Command: npx skills add https://github.com/dathere/qsv --skill data-join

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Joining two tabular datasets on a shared key is a common data integration task, and this skill automates and optimizes the join workflow within qsv to produce a unified result.

Core Features & Use Cases

  • Automated strategy selection for standard joins (joinp) and non-equi joins (sqlp) as well as ASOF nearest-match joins.
  • Guidance on indexing, profiling join columns, and memory-aware execution to optimize performance on large datasets.
  • Use Case: Inner joins to combine two related tables, Left joins to preserve all records from the left dataset, and ASOF joins to align time-series data.

Quick Start

Join two tabular data files on a shared key and write the merged result to output.csv.

Frequently Asked Questions about data-join

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

FAQPage Schema
How do I join two large CSV datasets on a shared key?

You can join two large CSV datasets on a shared key using smart strategy selection that profiles join columns, applies indexing, and executes memory-aware operations to output a unified dataset.

What is the best way to perform an ASOF join on time-series data?

The best way to perform an ASOF join on time-series data is using a nearest-match join strategy that aligns records based on timestamps, executing via SQL-based processing for non-equi join scenarios.

Can I execute a left join to preserve all records from one dataset while matching another?

Yes, you can execute a left join to preserve all records from the left dataset while matching corresponding rows from the right dataset, producing a unified result with nulls for unmatched entries.

How do I handle nulls and column name alignment when merging tabular files?

When merging tabular files, you handle nulls and column name alignment by configuring the join strategy to automatically manage mismatched column names and fill unmatched fields with null values during the data integration process.

Does smart join strategy selection support full outer and cross joins?

Yes, smart join strategy selection supports full outer and cross joins, automatically choosing between standard join processing and SQL-based processing to execute the requested operation across large files.

When should I use SQL-based processing instead of standard join commands for merging datasets?

You should use SQL-based processing instead of standard join commands when you need to execute non-equi joins or ASOF nearest-match scenarios that standard equality-based joining cannot handle.