XRefKit
XRefKit is a framework for making AI-assisted work repeatable, reviewable, and handoff-ready.
It helps teams turn domain procedures and knowledge into work that can be performed with explicit evidence, human judgment, and completion checks.
Why XRefKit?
Using AI for real work creates recurring operating problems:
- the AI can act from incomplete context or unsupported guesses
- procedures, domain facts, and judgment criteria get mixed together in prompts
- execution, checking, and handoff collapse into one opaque step
- work becomes hard to continue across agents, humans, or sessions
- outputs may lack evidence, closure discipline, or auditability
XRefKit provides a repository and runtime model for addressing these problems.
What it provides
- Skills — reusable procedures for a defined kind of work
- Knowledge — source-backed domain facts and local rules
- Workflow protocol — recorded progress, deterministic verification, and closure checks
- Evidence and handoffs — outputs, judgments, concerns, and decisions that remain reviewable after the work is done
- Skill Run Dashboard — inspect Skill execution status, referenced XIDs, evidence, judgments, concerns, and handoffs to improve the auditability of results
- XIDs — stable references for connecting procedures, knowledge, and supporting documents
The package includes the resolver, Skill runtime, workflow controls, client tools, and an optional MCP adapter.
The Skill Run Dashboard helps people trace how a Skill run used its referenced XIDs and recorded its evidence before accepting or handing off the result.
Quick start
XRefKit requires Python 3.11 or later.
python -m pip install xrefkit
xrefkit init
xrefkit --help
For local development:
python -m pip install -e .
xrefkit init
For the optional MCP server:
python -m pip install "xrefkit[mcp]"
xrefkit mcp serve --repo . --transport stdio
Where to go next
- Install XRefKit and register Skill Packages
- Understand the workflow protocol
- Use an instruction-backed workflow
- Understand Skills and Knowledge
- Author a Skill with xref
- Browse the complete documentation index
Security
XRefKit does not require provider API keys to explore or install the package.
Do not commit secrets, API keys, access tokens, .env files, or provider
credentials. Authenticate external AI tools through their official provider
mechanisms.
1 maintainer
Metadata
1 maintainer
Release files for xrefkit 0.4.16
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 | |
|---|---|---|---|---|
| xrefkit-0.4.16.tar.gz | 362.8 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| xrefkit-0.4.16-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 685.7 kB
Release files / xrefkit-0.4.16.tar.gz
| Download URL | xrefkit-0.4.16.tar.gz |
|---|---|
| Size | 362.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a0c54a96ec177b80687a0f1907e2a60e8edd5e63033951a7d41b4efd1cd3b4ae
|
|
BLAKE2b-256 checksum How to use checksums |
3f7480432fd3dc7ffb93bb0a526cf8e18fbd482d787b5a42c8babec3f35d907c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
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 Sep 13, 2026.
Transparency logRelease files / xrefkit-0.4.16-py3-none-any.whl
| Download URL | xrefkit-0.4.16-py3-none-any.whl |
|---|---|
| Size | 323.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a33c159d65ac271627e5fafc6e9cbd55911e1ca24fad0962bd6dec422a03ca18
|
|
BLAKE2b-256 checksum How to use checksums |
b195fd6a89b76bab432278b7d3dec2b61717205b8f492f6cb19f68d22e6282b1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
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 Sep 13, 2026.
Transparency logSecurity for xrefkit 0.4.16
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 xrefkit-0.4.16.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 Sep 13, 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.
