skillgram
Skill management for AI agents: one skill library, linked into every coding agent. No copies, no drift, no "which folder does this harness read?".
skillgram is a skill hub — a registry of SKILL.md files that lives in one directory on disk
— plus the admin layer that keeps every agent pointing at it. Claude Code, Codex, Cursor, Hermes,
Reasonix, Gemini CLI, OpenCode, Kiro, Qwen Code, Aider and Copilot all read the same library.
~/.agents/skills/<category>/<skill>/SKILL.md the hub (the only real copy)
~/.claude/skills/<skill> -> junction to the hub (symlink off Windows)
~/.codex/skills/<skill> -> junction to the hub
- Links, never copies. A native skill with the same name as a hub skill is skipped and reported as a collision, never overwritten.
- Project scope.
use+mountgive a repo exactly its set — twenty skills, not eight hundred — in every harness layout that reads project-level skills. - An MCP server.
skillgram mcpexposessearch/missing/use/status/propose, so the agent asks the hub instead of shelling out.missinganswering{"found": false}is the contract that says do not invent a skill, tell the user. - One idempotent command.
skillgram installresolves the harness, verifies the hub, registers the MCP server through the harness' own CLI, and propagates the project scope. - No LLM unless you ask. It is used only for
bootstrap,proposeandport, always as a JSON plan that skillgram validates and you approve.
Install
pip install skillgram
Then, once per machine:
skillgram install --dry-run # the exact commands, nothing written
skillgram install # harness -> hub -> MCP -> project scope
Python 3.9+, standard library only, no dependencies. Junctions on Windows, symlinks on macOS/Linux.
What it is not
Not a prompt manager, not a memory store, not an embeddings index. It links and administers the skills your agents already read, and it never guesses which harness is asking.
Documentation
- Repository and full README: https://github.com/Xhuk/skillgram
- Site: https://xhuk.github.io/skillgram/
- Install brief for an agent session: https://github.com/Xhuk/skillgram/blob/main/INSTALL.md
- The install flow, as an interactive diagram: https://xhuk.github.io/skillgram/diagrams/skillgram-install.html
- Changelog: https://github.com/Xhuk/skillgram/blob/main/CHANGELOG.md
- Known gaps: https://github.com/Xhuk/skillgram#known-gaps-documented-not-implemented
License
MIT.
1 maintainer
Metadata
1 maintainer
Release files for skillgram 1.4.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 | |
|---|---|---|---|---|
| skillgram-1.4.1.tar.gz | 75.2 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| skillgram-1.4.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 128.3 kB
Release files / skillgram-1.4.1.tar.gz
| Download URL | skillgram-1.4.1.tar.gz |
|---|---|
| Size | 75.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
70551b789e3dc7adf41180c76891a43da4673590380a409b9bbb83d243faa776
|
|
BLAKE2b-256 checksum How to use checksums |
4fdaefd0bdbcc9ed4ec881d207f7c3c5e7dfb111af8088419d3ec892363a1f8d
|
| 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 Oct 19, 2026.
Transparency logRelease files / skillgram-1.4.1-py3-none-any.whl
| Download URL | skillgram-1.4.1-py3-none-any.whl |
|---|---|
| Size | 53.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1cbaf041bc046550b9acbda0ee02651d910bcaabebb4d314384e46911ed5c6d2
|
|
BLAKE2b-256 checksum How to use checksums |
1d18ff8bc40de3db6566ace7ff46f88c63928392c45eb0695372c4649659a0dc
|
| 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 Oct 19, 2026.
Transparency logSecurity for skillgram 1.4.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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for skillgram-1.4.1.tar.gz
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 Oct 19, 2026.
Transparency logA 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.
