metaxy

Guide Metaxy feature definitions, versioning, and metadata tooling in data pipelines.

118|10|Updated Oct 13, 2025
One-click install
npx skills add https://github.com/anam-org/metaxy --skill metaxy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: metaxy
Source: https://github.com/anam-org/metaxy/tree/main/.claude-plugin/skills/metaxy
Command: npx skills add https://github.com/anam-org/metaxy --skill metaxy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Metaxy governs feature definitions, versioning, and metadata workflows for multi-modal data and ML pipelines. This skill provides practical guidance for creating feature definitions, configuring metadata stores, and using the Metaxy CLI to manage governance and lineage.

Core Features & Use Cases

  • Feature Definition Guidance: Learn how to implement a BaseFeature subclass with a FeatureSpec, including dependencies and field-level dependencies.
  • Versioning & Metadata Stores: Get patterns for versioning fields, triggering downstream invalidations, and configuring metadata stores (e.g., metaxy.toml) for reproducible pipelines.
  • CLI & Testing Guidance: Understand common metaxy CLI commands, migrations, and testing patterns to validate feature graphs and metadata correctness.
  • Example Scenarios: From small experiments to large pipelines, apply templates for feature definitions, dependencies, and data lineage.

Quick Start

To begin, ask for a minimal example that defines a feature class using mx.BaseFeature and a simple FeatureSpec, including a basic id_columns and fields.

Frequently Asked Questions about metaxy

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

FAQPage Schema
How do I define feature metadata for ML pipelines using a FeatureSpec?

To define feature metadata for ML pipelines, you subclass mx.BaseFeature and configure a FeatureSpec with id_columns and fields. This structure allows you to declare field-level dependencies and track versions for reproducible data workflows.

What is the best way to configure a metadata store for feature versioning?

The best way to configure a metadata store for feature versioning is by creating a metaxy.toml file. This configuration establishes reproducible pipelines by tracking metadata, governing feature definitions, and triggering downstream invalidations when fields change.

How do I manage feature lineage and migrations with the metaxy CLI?

You manage feature lineage and migrations with the metaxy CLI by running its built-in commands to apply schema changes and validate feature graphs. This ensures metadata correctness and tracks dependencies across your data pipelines.

Can I track field-level dependencies and downstream invalidations in data pipelines?

Yes, you can track field-level dependencies and downstream invalidations in data pipelines by defining them within your FeatureSpec. When a parent field version changes, the system uses these dependency graphs to trigger invalidations in downstream features.

What testing patterns should I use to validate feature graphs and metadata?

To validate feature graphs and metadata, you should use testing patterns that verify dependency resolution and versioning correctness. The skill provides actionable templates to test BaseFeature subclasses and ensure your FeatureSpec configurations are accurate.

Does metaxy work for both small experiments and large multi-modal data pipelines?

Yes, metaxy works for both small experiments and large multi-modal data pipelines. It provides scalable templates for feature definitions, dependency tracking, and data lineage governance, adapting to various pipeline sizes.