Skip to main content

taken

PyPI CI

"A very particular set of skills, acquired over a very long career."

taken is a personal dotfile-style CLI for managing AI agent skills (SKILL.md files). Think chezmoi, but for agent skills — your skills live in ~/.taken/, are git-backed, and can be linked into any project on demand.

Fully compatible with the skills.sh ecosystem (Claude Code, Cursor, OpenAI Codex, and 40+ agents).


Install

uv tool install taken-cli
pipx install taken-cli

Or run it without installing, via uvx:

uvx taken-cli init
uvx taken-cli use

Quick Start

1. Initialize

taken init

Sets up ~/.taken/, prompts for your namespace, creates config and registry.

2. Create a personal skill

taken add my-skill

Scaffolds ~/.taken/skills/<you>/my-skill/SKILL.md and opens it in your editor.

3. Adopt an existing skill from a project

taken add ./agents/my-skill/

Copies the skill folder into ~/.taken/ and registers it, detecting provenance from skills.sh lock files automatically.

4. Install a skill from GitHub

taken install vercel-labs/agent-skills
taken install vercel-labs/agent-skills/react-best-practices
taken install https://github.com/vercel-labs/agent-skills

Interactive fuzzy picker when multiple skills are found. Key flags:

  • --skill <name> — install a specific skill non-interactively (repeatable)
  • --ref <branch|tag|sha> — install from a specific ref
  • --pin — lock to the exact commit SHA so taken update never auto-upgrades it

5. Use a skill in a project

taken use

Fuzzy-picks from your registry, copies the skill into .agents/skills/ in the current project, and mirrors it into .claude/skills/ (symlink or copy, your choice). Tracking lives in ~/.taken/projects.yaml — nothing taken-specific is written into the project.

6. Push edits back to registry

taken save

If you refined a skill while working in a project, save promotes those edits back to ~/.taken/ so they propagate to future projects.

7. Update project skills

taken update

Re-copies the latest registry version into the project. Warns before overwriting if local edits are detected.


Commands

Command Description
taken init First-time setup — creates ~/.taken/, prompts for namespace
taken add <skill-name> Create a new personal skill, opens in editor
taken add <path> Adopt an existing skill folder into taken management
taken install <source> Install a skill from GitHub
taken use [namespace/skill] Copy a skill from registry into the current project
taken save [namespace/skill] Push project edits back to registry
taken update [namespace/skill] Re-copy latest registry version into project
taken list Show all skills in the registry
taken remove <namespace/skill> Remove a skill from registry
taken git <args> Run any git command inside ~/.taken/

How It Works

Skills live in ~/.taken/skills/<namespace>/<skill-name>/. The registry at ~/.taken/registry.yaml is the single source of truth for provenance — tracking whether a skill was created personally, adopted from a project, or installed from GitHub.

When you run taken use, the skill is copied into .agents/skills/ and mirrored into .claude/skills/ — as a relative symlink (default) or a full copy, set globally in config.yaml or per project with --mode. Which skills you copied where is personal state, tracked in ~/.taken/projects.yaml (git-ignored, never pushed). The project only contains the skill folders, so teammates don't need taken installed.


Environment Variables

Variable Description
GITHUB_TOKEN GitHub personal access token — set this to avoid API rate limits when using taken install or taken update
TAKEN_HOME Override the default ~/.taken/ location
VISUAL / EDITOR Editor opened by taken add (falls back to vim)

Metadata

Release files for taken-cli 0.2.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for taken-cli 0.2.0
File Size Uploaded Provenance Actions
taken_cli-0.2.0.tar.gz 26.4 kB Without provenance Details for taken_cli-0.2.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for taken-cli 0.2.0
File Interpreter ABI Platform Actions
taken_cli-0.2.0-py3-none-any.whl Python 3 none any Details for taken_cli-0.2.0-py3-none-any.whl

Total release size: 64.8 kB

Release files / taken_cli-0.2.0.tar.gz

Download URL taken_cli-0.2.0.tar.gz
Size 26.4 kB
Tags Source
SHA-256 checksum
How to use checksums
2ad5e8fdec49374091ba5e0b31da7b46f6e550e7ff6c62f4f98f475146ecfec9
BLAKE2b-256 checksum
How to use checksums
c40c3988911227b14a24416d228886aebe7ee4d4645ad9a6c21d9c0c3800a9ce
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.7 {"installer":{"name":"uv","version":"0.13.7","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Release files / taken_cli-0.2.0-py3-none-any.whl

Download URL taken_cli-0.2.0-py3-none-any.whl
Size 38.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
1325453d755947b6126485343fcee38d22fff21f3c303a2e817b29564df7ddba
BLAKE2b-256 checksum
How to use checksums
b801b5731d4191b0f424a401f9b90a62b65ff451cf656609298a72e64093182d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.7 {"installer":{"name":"uv","version":"0.13.7","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Security for taken-cli 0.2.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page