Agent skill · AI & Agents

metaxy

This skill should be used when the user asks to "define a feature", "create a BaseFeature class", "track feature versions", "set up metadata store", "field-level dependencies", "FieldSpec", "FeatureDep", "run metaxy CLI", "metaxy migrations", or needs guidance on metaxy feature definitions, versioning, metadata stores, CLI commands, or testing patterns.

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill metaxy --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 4 KB
Bundled scripts: none
Path: skills/ai-ml/metaxy/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Metaxy Metaxy is a metadata layer for multi-modal Data and ML pipelines that manages and tracks feature versions, dependencies, and data lineage across complex computational graphs. ## Core Concepts ### Feature Definitions To define a feature, create a class inheriting from `mx.BaseFeature` with a `FeatureSpec` metaclass argument: ```python import metaxy as mx class MyFeature( mx.BaseFeature, spec=mx.FeatureSpec( key="my/feature", id_columns=["sample_id"], fields=["embedding", "score"], ), ): sample_id: str embedding: list[float] score: float ``` To add dependencies between features, use the `deps` parameter with `FeatureDep`. To specify field-level dependencies (for partial data dependencies processing), use `FieldSpec` with `FieldDep` or `FieldsMapping`. ### Data Versioning Metaxy automatically tracks sample versions and propagates changes through the dependency graph. To trigger recomputation when code changes, set `code_version` on `FieldSpec`: ```python fields = [ mx.FieldSpec(key="embedding", code_version="2"), # Bump to invalidate downstream ] ``` ### Metadata Stores To configure a metadata store, create a `metaxy.toml` file or use programmatic configuration: ```python wit

What's inside
Steps it walks through
  1. Core Concepts
  2. Feature Definitions
  3. Data Versioning
  4. Metadata Stores
  5. Feature Graph
  6. CLI
  7. Testing
  8. Examples
  9. Documentation
Ships with 1 file
  • metadata.json
Commands it runs
mx graph render            # Terminal visualization
mx graph push --store dev  # Push graph to store
mx list features --verbose     # List features with dependencies
mx graph render                # Visualize feature graph
mx metadata status --all-features  # Check metadata freshness (expensive!)
mx migrations apply            # Apply pending migrations
mx mcp                         # Start MCP server for AI assistants
More from claude-skill-registry
All skills →
About this skill
What does the metaxy skill do?

This skill should be used when the user asks to "define a feature", "create a BaseFeature class", "track feature versions", "set up metadata store", "field-level dependencies", "FieldSpec", "FeatureDep", "run metaxy CLI", "metaxy migrations", or needs guidance on metaxy feature definitions, versioning, metadata stores, CLI commands, or testing patterns.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill metaxy --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going