🧰 skillkit
The toolbox for AI agent skills. Scaffold, lint, pack, and install SKILL.md skills — and serve your whole skill library to Claude Code, Cursor, and any MCP client with a built-in Model Context Protocol server.
Community audits found that the overwhelming majority of published SKILL.md files carry at least one "skill smell" — and a large share leak secrets. skillkit catches those before you ship.
📖 Deep docs: Usage guide — lint rules reference, MCP patterns, CI usage · Architecture · Contributing · Changelog · Security
✨ Features
- 🆕
new— scaffold a spec-compliant skill folder in one command - 🔍
lint— validate against the Agent Skills spec plus security smells: leaked API keys, vague descriptions, oversized bodies, folder typos, and more (scored 0–100 with a grade) - 📦
pack— zip a skill for upload to skill-capable platforms - 📥
install— install from a folder or any git URL into~/.claude/skills(or your own directory) - 🗂️
list/remove— manage your installed skill library - 🔌
mcp— a zero-dependency MCP server (stdio, JSON-RPC 2.0) that exposeslist_skills,read_skill, andlint_skilltools to any client - 🪶 Zero dependencies — pure Python standard library
- 🧪 76 tests, CI on Python 3.10 → 3.12
🚀 Quick start
# install from PyPI (installs the `skillkit` command)
pipx install skillkit-cli
# ...or from source
git clone https://github.com/furkan708/skillkit.git
cd skillkit && pip install .
# 1. create a skill
skillkit new commit-writer -d "Writes conventional commit messages from staged diffs. Use when the user asks to commit changes."
# 2. lint it (spec + security + quality)
skillkit lint commit-writer
# ✓ no issues found
# score: 100/100 (grade A) · 0 errors · 0 warnings · 0 notes
# 3. pack it for upload
skillkit pack commit-writer # → commit-writer.zip
# 4. install it for Claude Code
skillkit install ./commit-writer # → ~/.claude/skills/commit-writer
🔌 Serve your skills over MCP
Add skillkit to any MCP client config — Claude Code, Cursor, Windsurf, and every other MCP-compatible agent:
{
"mcpServers": {
"skillkit": { "command": "skillkit", "args": ["mcp"] }
}
}
Your agent can now discover and read every installed skill on demand:
| Tool | What it does |
|---|---|
list_skills |
Discover installed skills with names + descriptions |
read_skill |
Load the full SKILL.md instructions of one skill |
lint_skill |
Validate a skill and get its quality score |
🔍 What lint catches
| Rule | Severity | Check |
|---|---|---|
| SEC001 | ✗ error | Leaked secrets: GitHub/AWS/OpenAI/Slack tokens, private keys, hardcoded credentials |
| SKILL001 | ✗ error | Invalid name: charset, length ≤ 64, reserved words (anthropic, claude) |
| SKILL002 | ✗ error | name does not match the folder name |
| SKILL003 | ✗ error | description longer than 1,024 characters |
| SKILL009 | ✗ error | metadata is not a string→string map |
| SKILL004 | ⚠ warn | Vague description (won't trigger — describe what and when) |
| SKILL005 | ⚠ warn | Body over ~500 lines (move detail into references/) |
| SKILL007 | ⚠ warn | Folder typos: script/, reference/, docs/… |
| SKILL006 | · info | Very thin body — add steps and examples |
| SKILL008 | · info | Unknown frontmatter fields |
Every run ends with a 0–100 score and a letter grade, so you know when a skill is ready to publish.
📖 CLI reference
skillkit new <name> -d <description> [--dir DIR] scaffold a skill
skillkit lint <path> [--json] [--strict] validate a skill
skillkit pack <path> [-o FILE.zip] zip for upload
skillkit install <path|git-url> [--agent claude|project] [--dir DIR]
skillkit list [--agent ...] [--dir DIR] [--json] show installed skills
skillkit remove <name> [--dir DIR] uninstall a skill
skillkit mcp [--dir DIR] serve skills over MCP
Built on the open Agent Skills specification — the same format supported by 40+ platforms including Claude, OpenAI Codex, and GitHub Copilot.
🧪 Tests
pip install pytest
pytest -v
🗂️ Project Structure
skillkit/
├── skillkit/
│ ├── frontmatter.py # minimal YAML frontmatter parser
│ ├── model.py # skill loading (Agent Skills spec)
│ ├── linter.py # rules, security smells, 0-100 score
│ ├── scaffold.py # new + pack
│ ├── installer.py # install / list / remove (folder or git)
│ ├── mcp_server.py # zero-dependency MCP stdio server
│ └── cli.py # command-line interface
└── tests/
🗺️ Roadmap
-
skillkit search— search community skill registries - More install targets (Codex, Copilot CLI paths as they standardize)
-
skillkit doctor— prompt-injection heuristics (planned, not implemented yet)
📄 License
MIT — see the LICENSE file for details.
Metadata
Release files for skillkit-cli 1.0.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| skillkit_cli-1.0.2.tar.gz | 24.9 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| skillkit_cli-1.0.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 44.5 kB
Release files / skillkit_cli-1.0.2.tar.gz
| Download URL | skillkit_cli-1.0.2.tar.gz |
|---|---|
| Size | 24.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1ed8916a8da5d6b90f04e94615bfce15088ea0edd89537c06549e157250f8085
|
|
BLAKE2b-256 checksum How to use checksums |
d6c1342ba10a1d4101f0e6d46dd4c2fb07c8012eabefbf95620312ca83c48957
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 28, 2026.
Transparency logRelease files / skillkit_cli-1.0.2-py3-none-any.whl
| Download URL | skillkit_cli-1.0.2-py3-none-any.whl |
|---|---|
| Size | 19.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9e32b18d6064ff582f57c2ed111f1e434ffce17705f59b29cafc52b927b32b0a
|
|
BLAKE2b-256 checksum How to use checksums |
5c6b59a14fac1cdf4d53ff74998c1c80318f43fe310af0f25ecf82124374e018
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 28, 2026.
Transparency log