Deply Config
Vashkatsi/deply
A skill your agent uses when creating, auditing, validating, or integrating Deply v1.2.0 architecture configuration files for Python projects, including deply.yaml, light/medium/strict guidance…
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 lineage", "FieldSpec", "FeatureDep"…
$ npx skills add anam-org/metaxy --skill metaxy -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install anam-org/metaxy metaxy --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/anam-org/metaxy.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude-plugin/skills/metaxy .claude/skills/metaxy && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "metaxy" agent skill from https://github.com/anam-org/metaxy/tree/main/.claude-plugin/skills/metaxy into .claude/skills/metaxy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "metaxy", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/anam-org/metaxy/tree/main/.claude-plugin/skills/metaxyType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add anam-org/metaxy --skill metaxy -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install anam-org/metaxy metaxy --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/anam-org/metaxy.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude-plugin/skills/metaxy .agents/skills/metaxy && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "metaxy" agent skill from https://github.com/anam-org/metaxy/tree/main/.claude-plugin/skills/metaxy into .agents/skills/metaxy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "metaxy", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add anam-org/metaxy --skill metaxy -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install anam-org/metaxy metaxy --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/anam-org/metaxy.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude-plugin/skills/metaxy .cursor/skills/metaxy && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "metaxy" agent skill from https://github.com/anam-org/metaxy/tree/main/.claude-plugin/skills/metaxy into .cursor/skills/metaxy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "metaxy", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/anam-org/metaxy.git --path .claude-plugin/skills/metaxy--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add anam-org/metaxy --skill metaxy -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install anam-org/metaxy metaxy --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/anam-org/metaxy.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude-plugin/skills/metaxy .gemini/skills/metaxy && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "metaxy" agent skill from https://github.com/anam-org/metaxy/tree/main/.claude-plugin/skills/metaxy into .gemini/skills/metaxy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "metaxy", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install anam-org/metaxy metaxyInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add anam-org/metaxy --skill metaxy -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/anam-org/metaxy.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude-plugin/skills/metaxy .github/skills/metaxy && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "metaxy" agent skill from https://github.com/anam-org/metaxy/tree/main/.claude-plugin/skills/metaxy into .github/skills/metaxy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "metaxy", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add anam-org/metaxy --skill metaxy -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install anam-org/metaxy metaxy --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/anam-org/metaxy.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude-plugin/skills/metaxy .opencode/skills/metaxy && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "metaxy" agent skill from https://github.com/anam-org/metaxy/tree/main/.claude-plugin/skills/metaxy into .opencode/skills/metaxy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "metaxy", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
metaxyThis 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 lineage", "FieldSpec", "FeatureDep"…
Metaxy is an agent skill from anam-org/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 lineage", "FieldSpec", "FeatureDep", "run metaxy CLI", "metaxy migrations", "metaxy lock", "lock features", "external features", "multi-environment", "monorepo features", "enable Map datatype", "enablemapdatatype", or needs guidance on metaxy feature definitions, versioning, metadata stores, CLI commands, testing patterns, feature locking, Map datatype…
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files (for example `examples/cli.md`, `examples/configuration.md` and `examples/feature-definitions.md`).
It sits in Development, covering Test strategy and Monorepo tooling. It works with Python. The repository describes itself as: Pluggable metadata management framework for versioned incremental multimodal data/ML pipelines. The licence is Apache-2.0.
Read from SKILL.md and the folder at commit 8337842. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are python and bash).
From the folder's file list and the shell code blocks in SKILL.md.
Links to these hosts (documentation or services it may open):
docs.metaxy.ioFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Metaxy loads about 1.5k tokens when it runs. Until then it costs about 144 tokens; SKILL.md has 410 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from anam-org/metaxy at commit 8337842, republished under its Apache-2.0 licence (© anam-org). 410 words, ~1,534 tokens.
.claude/skills/metaxy/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.Metaxy is a metadata layer for multimodal Data and ML pipelines that manages and tracks feature versions, dependencies, and data lineage across complex computational graphs.
To define a feature, create a class inheriting from mx.BaseFeature with a FeatureSpec metaclass argument:
import metaxy as mx
class Video(
mx.BaseFeature,
spec=mx.FeatureSpec(
key="media/video",
id_columns=["video_id"],
fields=["audio", "frames"], # Logical fields: describe data contents for versioning
),
):
# Metadata columns: stored in the metadata store, tracked by metaxy
video_id: str
path: str
duration: float
height: int
width: intImportant distinction: fields in FeatureSpec are logical field specs that describe the data contents for versioning and lineage tracking. Class attributes are metadata columns stored in the metadata store. They serve different purposes and should not overlap.
To add dependencies between features, use the deps parameter with FeatureDep. To specify field-level lineage (for partial data dependencies), use FieldSpec with FieldDep or FieldsMapping.
Metaxy automatically tracks sample versions and propagates changes through the dependency graph. To trigger recomputation when code changes, set code_version on FieldSpec:
fields = [
mx.FieldSpec(key="embedding", code_version="2"), # Bump to invalidate downstream
]To configure a metadata store, create a metaxy.toml file or use programmatic configuration:
config = mx.MetaxyConfig(
stores={"dev": mx.StoreConfig(
type="metaxy.ext.polars.handlers.delta.DeltaMetadataStore",
config={"root_path": "/tmp/metaxy"},
)}
)
with config.use() as cfg:
store = cfg.get_store("dev")Supported backends: DuckDB, ClickHouse, BigQuery, LanceDB, Delta Lake.
To visualize and manage the feature dependency graph, use the CLI:
mx graph render # Terminal visualization
mx push --store dev # Push graph to storeMetaxy provides a CLI (metaxy or mx alias) for managing features, metadata, and migrations:
mx list features --verbose # List features with dependencies
mx graph render # Visualize feature graph
mx metadata status --all-features # Check metadata freshness (expensive!)
mx mcp # Start MCP server for AI assistantsCross-project dependencies typically resolve automatically via Python packages — if project B depends on project A as a Python dependency, its features are discovered at import time. Feature locking (mx lock) is needed for multi-environment setups where projects cannot be installed into each other (e.g., separate deployment environments). In that case, use mx push to publish definitions to a shared store, and mx lock to fetch them into a metaxy.lock file. Set locked = true (or METAXY_LOCKED=1) in production to enforce version consistency.
For configuration patterns and CLI usage, see examples/configuration.md and examples/cli.md.
To test features in isolation, use context managers to avoid polluting the global registry:
import pytest
import metaxy as mx
@pytest.fixture
def metaxy_env(tmp_path):
with mx.FeatureGraph().use():
with mx.MetaxyConfig(
stores={"test": mx.StoreConfig(
type="metaxy.ext.polars.handlers.delta.DeltaMetadataStore",
config={"root_path": str(tmp_path / "delta_test")},
)}
).use() as config:
yield configTo enable native Arrow Map column support (recommended for stores that support it), set enable_map_datatype = true in metaxy.toml. Requires the polars-map package. See https://docs.metaxy.io/stable/guide/concepts/metadata-stores/#map-datatype
When working with Map columns, use metaxy.utils.collect_to_polars, metaxy.utils.collect_to_arrow, or metaxy.utils.switch_implementation_to_polars to materialize or convert frames. These utilities preserve Map column types that would otherwise be lost with standard Narwhals backend conversions. See https://docs.metaxy.io/stable/guide/concepts/metadata-stores/#map-datatype
For complete code examples, see:
examples/feature-definitions.md - Feature classes with dependencies and field-level depsexamples/configuration.md - TOML and programmatic configurationexamples/metadata-stores.md - Store operationsexamples/testing.md - Test isolation patternsexamples/cli.md - CLI command referenceFor comprehensive documentation: https://docs.metaxy.io/stable/
Key pages:
© anam-org, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 5 other files in .claude-plugin/skills/metaxy of anam-org/metaxy.
Open the folder on GitHubat commit 8337842
Metaxy next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Metaxy this skillanam-org/metaxy | 124 | — | ~1.5k | Automated safety check: Pass | Apache-2.0 | |
| Deply ConfigVashkatsi/deply | 173 | — | ~945 | Automated safety check: Pass | MIT | |
| Tbdjlevy/strif | 131 | — | ~3.5k | Automated safety check: Pass | MIT | |
| Light Project StructureLight0305/Light-skills | 640 | — | ~3k | Automated safety check: Notes | MIT | |
| Claude Settings Auditgetsentry/skills | 1k | 4 repos | ~3k | Automated safety check: Pass | Apache-2.0 | |
| Rocky Devrocky-data/rocky | 304 | — | ~2.1k | Automated safety check: Pass | Apache-2.0 |
Vashkatsi/deply
A skill your agent uses when creating, auditing, validating, or integrating Deply v1.2.0 architecture configuration files for Python projects, including deply.yaml, light/medium/strict guidance…
jlevy/strif
Git-native issue tracking (beads), coding guidelines, knowledge injection, and spec-driven planning for AI agents.
Light0305/Light-skills
Audits, scaffolds and safely migrates research project folder structures, keeping existing repositories read-only until you approve exact moves from a plan.
getsentry/skills
Analyze a repository to generate recommended Claude Code settings.json permissions.
rocky-data/rocky
Top-level router for Rocky development tasks. An agent skill from rocky-data/rocky.
Marve10s/Better-Fullstack
Scaffold a new app, API, backend, fullstack project, mobile app, polyglot service, monorepo, or starter with Better Fullstack.
anam-org/metaxy
This skill should be used when the user asks to "add a tach module", "configure tach layers", "define module boundaries", "set up interfaces", "run tach check", "check module boundaries", "tach…
anam-org/metaxy
Self-reflect on the current session to identify mistakes and propose improvements to .claude configuration (CLAUDE.md, hooks, skills).
anam-org/metaxy
Write YAML front matter for documentation pages with appropriate titles and descriptions for social cards.
anam-org/metaxy
Use Hypothesis for property-based testing to automatically generate comprehensive test cases, find edge cases, and write more robust tests with minimal example shrinking.
anam-org/metaxy
Effectively use Narwhals to write dataframe-agnostic code that works seamlessly across multiple Python dataframe libraries.
anam-org/metaxy
Use Sybil for testing code examples in documentation and docstrings.
Works with
Categories
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 lineage", "FieldSpec", "FeatureDep"…. Metaxy is an agent skill from anam-org/metaxy.
Metaxy fits situations like: asks to define a feature; create a BaseFeature class; track feature versions; set up metadata store.
Run `npx skills add anam-org/metaxy --skill metaxy -a claude-code`. Or copy the skill folder (.claude-plugin/skills/metaxy in anam-org/metaxy) into .claude/skills/metaxy in your project. Claude Code loads it when a task matches its description.
Run `npx skills add anam-org/metaxy --skill metaxy -a codex`. Or copy the skill folder (.claude-plugin/skills/metaxy in anam-org/metaxy) into .agents/skills/metaxy in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add anam-org/metaxy --skill metaxy -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/metaxy, .gemini/skills/metaxy, .github/skills/metaxy and .opencode/skills/metaxy in your project.
SKILL.md names no scripts, command-line tools or credentials: Metaxy is instructions for the agent only. Our summary lists: Python 3.
SKILL.md names 1 domain. As links in the text: docs.metaxy.io. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Metaxy is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.5k tokens (SKILL.md is roughly 6.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Metaxy: Deply Config (Vashkatsi/deply, 173 stars), Tbd (jlevy/strif, 131 stars), Light Project Structure (Light0305/Light-skills, 640 stars) and Claude Settings Audit (getsentry/skills, 1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
anam-org (a GitHub organization) maintains it in anam-org/metaxy, which has 124 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on September 30, 2026.
Source: anam-org/metaxy on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.