Dex Trove

A trove of dexterities for your agents. Dex Trove is short for Dexterity Trove: a licence-clean library of skills, agents, instructions, hooks and plugins your AI can pick up. They're learned from open repos and packaged for Ananke, Claude Code and GitHub Copilot.

Dex Trove learns artifacts from repositories such as github/awesome-copilot, anthropics/skills and obra/superpowers, plus our own first-party skills. It admits only items whose licence allows redistribution, checked one item at a time from the licence text. Each item becomes a standard folder with an Ananke manifest and full provenance, and the whole library ships to PyPI as dex-trove.

📚 Browse the catalog: https://neo-pragnya.github.io/Dex-Trove/. Every item has its own page with its licence evidence, upstream source and install commands.

Install and use

pip install dex-trove

dex search architecture diagram
dex show neo-pragnya/marvellous-aws-architecture-docs
dex install superpowers/systematic-debugging --target claude            # ~/.claude/skills/…
dex install awesome-copilot/git-commit --target copilot                 # ./.github/skills/…
dex install awesome-copilot/arize-ax --target copilot                   # a plugin installs its members
dex install anthropic/mcp-builder --target dir --path ./vendor

Pin exact versions

Dex remembers every version it ever shipped. A lock installs exactly what you pinned, even after the trove moves on, fetching older releases from their upstream commit and checking the digest:

dex lock superpowers/systematic-debugging      # writes dex.lock.json
dex install --locked --target claude --scope project
dex release list superpowers/systematic-debugging
dex related superpowers/executing-plans        # requires, complements, alternatives, each with evidence
dex search write the failing test first --rank semantic

With Ananke

Every item ships an ananke.yaml inside the wheel, so Ananke can discover all of them with no glue code:

pip install ananke-plexus dex-trove
ananke registry init
ananke registry learn python:dex-trove           # everything in the installed wheel

dex ananke sync --kind skill --source neo-pragnya # or a curated slice

Plugins become Ananke bundles whose members resolve to the trove's skills and agents. Items whose text contains credential-shaped strings are left out of the trove (secret-shaped in EXCLUDED.json), even when the strings are only placeholders. A secret scanner can't tell a placeholder from a real key, and a package firewall quarantines the whole wheel for one hit.

Licence policy in one table

Resolution goes from the most specific evidence to the least: item frontmatter, then the item's licence file, then ancestor folders, then the repo licence. Restrictive terms anywhere in the item win. Upstream files are copied byte-for-byte. The governing licence text travels with each item (as LICENSE.upstream when the item didn't ship one), and THIRD_PARTY_NOTICES.md aggregates the attributions.

Repository layout

sources.yaml              what we learn from (adapter, licence expectations, exclusions, inspirations)
trove/<kind>/<ns.name>/   the library: upstream files + ananke.yaml + dex.json (+ LICENSE.upstream)
trove/catalog.json        index of every item          trove/EXCLUDED.json   what was refused and why
trove/trove.lock.json     commit each source was learned at
trove/releases.json       every version of every item (append-only)
trove/relations.json      typed relations with evidence       trove/install-checks.json  what Dex verified
src/dex_trove/            the `dex` CLI and learn pipeline
website/                  Astro docs site (content generated by `dex docs export`)
docs/design/              DESIGN.md and CHECKLIST.md

Documentation

Full docs live in docs/ and on the website:

• Concepts: why · architecture · artifact kinds · related items · capability memory · licence policy · provenance & versioning · security model
• Guides: getting started · installing items · Ananke integration · adding a source · first-party skills · docs site · release
• Reference: CLI · sources.yaml · item format · trove files · reuse matrix · capability matrix · licence identification · exclusion reasons · configuration · Python API
• Design: design document · checklist

Contributing: learn → review → release

make install                    # uv sync --all-extras (includes ananke-plexus for strict validation)
uv run dex learn                # or: uv run dex learn awesome-copilot --prefer-local
make verify                     # ruff · mypy strict · pytest · dex validate
make docs-build                 # dex docs export + astro check + build

1. Map a new source in sources.yaml. Check its licence and add it under candidates: first.
2. dex learn <source> and review the diff of trove/ and trove/EXCLUDED.json in a PR.
3. Merge. The docs site redeploys, and a vX.Y.Z tag publishes to TestPyPI and PyPI (build once, Trivy gate, provenance attestation, trusted publishing; see the release guide).

A weekly workflow re-learns every enabled source and opens a PR, so upstream licence changes surface for review. See CONTRIBUTING.md and SECURITY.md.

Credits

Dex Trove exists because of the authors of the projects above. Their work keeps its original licence and copyright notices. The Sources & inspirations page lists each one. Dex Trove's own code is MIT.