skill-deployer
Install AI coding CLI skills to Claude Code and Codex with one command.
Both platforms use the same skill format (SKILL.md + optional references/ and scripts/ directories) but store them in different locations and register MCP servers differently. This tool bridges that gap.
Install
pip install skill-deployer
Usage
Check detected platforms
skill-deployer status
Install skills
# Install all bundled skills to all detected platforms
skill-deployer install
# Install a specific bundled skill
skill-deployer install my-skill-name
# Install from a GitHub URL
skill-deployer install https://github.com/user/repo/tree/main/skills/my-skill
# Install from a local directory
skill-deployer install ./path/to/skill
# Target a specific platform
skill-deployer install --claude
skill-deployer install --codex
# Overwrite existing skills
skill-deployer install --force
List skills
# List skills installed on detected platforms
skill-deployer list
# List bundled skills available in this package
skill-deployer list --bundled
Uninstall skills
skill-deployer uninstall my-skill-name
Register MCP servers
Register an MCP server on both Claude Code and Codex in one command:
skill-deployer mcp picocalc picocalc-mcp
skill-deployer mcp picocalc python3 /path/to/mcp_server.py
This writes to .mcp.json for Claude Code and runs codex mcp add for Codex.
How it works
| Claude Code | Codex | |
|---|---|---|
| Skills dir | ~/.claude/skills/ |
~/.codex/skills/ |
| Skill format | SKILL.md (YAML frontmatter) |
SKILL.md (YAML frontmatter) |
| MCP config | .mcp.json in project root |
codex mcp add command |
skill-deployer detects which platforms are installed, copies skill directories to the right location, and handles MCP registration for each platform's config format.
For skill authors
Bundle your skills in the package by adding them to src/skill_deployer/_skills/ and updating manifest.json:
{
"skills": [
{
"name": "my-skill",
"version": "1.0.0",
"description": "What my skill does"
}
]
}
Each skill directory needs a SKILL.md with YAML frontmatter:
---
name: my-skill
description: Trigger description for the AI assistant
---
# Skill content here
Requirements
- Python 3.9+
- Zero runtime dependencies (stdlib only)
License
MIT
Metadata
Release files for skill-deployer 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| skill_deployer-0.1.1.tar.gz | 10.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| skill_deployer-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 24.1 kB
Release files / skill_deployer-0.1.1.tar.gz
| Download URL | skill_deployer-0.1.1.tar.gz |
|---|---|
| Size | 10.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f94b479f8d2e806b3e6f3a1b5ad7a273a6b6151feea271cf5bbb5f8347ae409f
|
|
BLAKE2b-256 checksum How to use checksums |
c6d0dc285277392088f6231c45229a73d379dc8cb5876700b1968c61cc6db49b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.3
|
Release files / skill_deployer-0.1.1-py3-none-any.whl
| Download URL | skill_deployer-0.1.1-py3-none-any.whl |
|---|---|
| Size | 13.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
349e0c72dc433b9887a112d75684f501a726f7d822dcd212e166a605dd84dba1
|
|
BLAKE2b-256 checksum How to use checksums |
a084413840427fad0eab926a5e33072e57281396a0ae18a5f3774789a257d438
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.3
|
Security for skill-deployer 0.1.1
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.