skills.rest
TeoSlayer
TeoSlayerCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

pilot-dataset

Publish and negotiate structured datasets between peers via Pilot Protocol.

7|3|Updated Apr 8, 2026
Search Tags:#schema#provenance#dataset#data-exchange#pilotctl#pilot-protocol
One-click install
npx skills add https://github.com/TeoSlayer/pilot-skills --skill pilot-dataset
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pilot-dataset
Source: https://github.com/TeoSlayer/pilot-skills/tree/main/skills/pilot-dataset
Command: npx skills add https://github.com/TeoSlayer/pilot-skills --skill pilot-dataset

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Exchanging structured datasets between agents requires consistent schemas and provenance tracking, which this skill coordinates.

Core Features & Use Cases

  • Schema negotiation and metadata exchange to align dataset formats and structures.
  • Format-agnostic transfer with support for CSV, JSON, and Parquet, plus optional conversions.
  • Provenance tracking to maintain origin and lineage information across transfers.

Quick Start

Publish a dataset to a peer and negotiate the schema to begin transfer.

Frequently Asked Questions about pilot-dataset

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

FAQPage Schema
How do I exchange structured datasets with schema negotiation between peers?▼

You can exchange structured datasets between peers by using the Pilot Protocol to publish data and negotiate schemas. This process aligns dataset formats and structures while tracking provenance metadata across the transfer.

Can I transfer datasets in CSV, JSON, or Parquet formats using Pilot Protocol?▼

Yes, Pilot Protocol supports format-agnostic dataset transfers across CSV, JSON, and Parquet. It also handles optional format conversions during the data exchange to ensure compatibility between peers.

How does provenance tracking work for structured dataset exchanges?▼

Provenance tracking maintains origin and lineage information across dataset transfers. By using the Pilot Protocol, metadata containing the data's source history is preserved and exchanged alongside the schema during peer negotiations.

Do I need pilotctl running to publish and negotiate dataset schemas?▼

Yes, pilotctl must be running and the Pilot Protocol stack must be available in your environment to operate. These components are required to coordinate the schema negotiation and dataset transfers between peers.

What is the best way to align dataset formats before transferring data to a peer?▼

The best way to align dataset formats is through schema negotiation and metadata exchange. Publishing your dataset via the Pilot Protocol allows peers to negotiate the structure and apply necessary format conversions before transfer.

Why does my dataset transfer fail without consistent schemas?▼

Dataset transfers fail without consistent schemas because peers cannot interpret the incoming data structure. Using Pilot Protocol for schema negotiation before transfer ensures both sides agree on formats and provenance metadata.

Related Skills

Explore More Data & Analytics Skills→
TeoSlayerTeoSlayer
7

pilot-protocol

Enable encrypted peer-to-peer messaging and peer discovery between AI agents via pilotctl.

Community
Advanced
starlake-aistarlake-ai
209

parquet2csv

Convert Parquet files into CSV format for batch ETL pipelines.

Official
Intermediate
TeoSlayerTeoSlayer
7

pilot-archive

Index and search Pilot Protocol messages, file transfers, and metadata.

Community
Intermediate
semantica-agisemantica-agi
3.0k

export

Export knowledge graph data and provenance to JSON, RDF, Parquet, CSV, and GraphML.

Official
Intermediate