Install
$ agentstack add skill-skillnerds-xskill-using-xskill ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Using xskill
Overview
xskill distills reusable Skills (SKILL.md folders) out of the real execution trajectories of coding agents (Claude Code, Codex, OpenCode, Cursor, …). A background daemon watches each agent's session logs, slices them into single-intent atoms, clusters atoms into skills, and writes/versions each skill in its own git folder. New skill versions only replace old ones when real traffic shows they serve users better (canary A/B by UX score) — not by an LLM grading itself.
Core mental model: raw trajectory → atoms → candidate routing → SKILL.md → canary A/B → installed into every agent's skill dir. You operate the daemon; the daemon does the distilling.
When to Use
- Installing xskill or filling in
~/.xskill/config.yaml(LLM + embedding endpoints) - Starting/keeping the daemon running (
xskill serve), or backfilling old trajectories - Joining or hosting a team server (
xskill serve --server/xskill connect) - Understanding the agent pipeline, atoms, canary/UX scoring, or deployment modes
- Re-distilling the whole skill library (e.g. after switching to a stronger model)
Quick Reference
| Command | What it does | |---------|--------------| | pip install xskill | Install (Python 3.9+) | | xskill serve | Standalone daemon: FastAPI + watcher; first run writes ~/.xskill/config.yaml then exits | | xskill serve --server | Team server: owns all LLM calls + git; prints a join token | | xskill connect --token | Join a team server as a thin client | | xskill registry add | Backfill / watch an extra trajectory directory | | xskill search traj\|skill | Search trajectories or skills | | xskill read --eco | Batch-ingest db trajectories (ngagent/opencode) | | xskill rebuild [--force] | Re-distill from existing raw trajectories (see reference) | | xskill stats | Token usage & estimated cost |
The daemon is the engine: most commands only change state in the DB; nothing is distilled unless xskill serve (or the team server) is running.
Progressive Disclosure — read on demand
- Install & configure (config.yaml fields, per-agent collect/install paths, team
client setup): references/installation.md
- How it works (TaskAgent → TaskClusterAgent → SkillEditAgent, atoms, canary/UX
scoring, standalone vs team mode): references/mechanisms.md
- Rebuild the skill library (a ready-to-run prompt that walks a model through
re-distilling correctly): references/rebuilding-skill-library.md
Common Mistakes
- Running
rebuildwith no daemon up.rebuildonly resets DB state; the watcher
in serve does the actual re-split/re-cluster every 30s. No daemon = nothing happens.
- Deleting raw
~/.xskill/*_sessions/*.md. Those are the input to distillation —
delete them and you can no longer rebuild.
- Expecting DeepSeek to do embeddings. DeepSeek has no embedding endpoint; point the
embedding: block at DashScope / OpenAI / Ollama.
- Putting tokens in public places. Team join tokens must never land in a public repo
or chat log.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: SkillNerds
- Source: SkillNerds/xskill
- License: MIT
- Homepage: https://xskill.wiki/
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.