Your governed skill library. Add skills, browse what you have, see how they cluster, and manage the sources that produce them.
Add skills
Paste a SKILL.md document. Uploading runs deduplication and clustering automatically. Uploading the same skill again from the same source creates a new version.
Browse skills
| Name | Status | Rank | Loads | Wins | Votes |
|---|
Clusters
Clustering groups similar skills into a library. The representative is the top ranked skill in each cluster, the one that ships on export.
| Label | Active members | Representative | Id |
|---|
Register a source
A source is who authored a skill: a team, an agent, a person, or a tool. Every skill and vote carries its provenance.
Sources
Click a source to see its credit: the realized value its skills produced.
| Kind | Name | Id |
|---|
Find the best skill for a task
Describe what an agent is about to do. Kiln returns the single best skill, or nothing when no skill matches well enough.
Proposals awaiting review
Candidate skills that changed existing guidance or hit a risk rule are held here. The live skill keeps serving until you decide. Approving needs the administrator token.
| Mode | Reason | Target | Id |
|---|
Administrator area. Connect the language model that extraction uses, and see how skills get into Kiln.
Connect a language model
Extraction uses a language model. Pick how this deployment authenticates. Your key, if any, is written to your own AWS Secrets Manager and is never stored by Kiln.
Teams and groups
Map a group from your identity provider to a Kiln team so skills can be scoped to it. Use the group name for Okta, or the group object id (GUID) for Entra ID. Members of a group see that team's skills plus anything shared with everyone.
| Team | Identity provider group | Description |
|---|
Extraction runs locally
Extraction happens on your own machine so your traces never leave it. The local tool reads your traces, distills a skill, and uploads only the finished skill to this server, which then auto publishes it or holds it for review under Proposals. The server never receives traces.
Create a new skill from traces
kiln extract \ --url http://127.0.0.1:8000 \ --file ./traces.json \ --mode creation \ --source-id <your source id> \ --seed-name rotate_keys \ --seed-description "Safely rotate cloud access keys."
Deepen an existing skill from traces
kiln extract \ --url http://127.0.0.1:8000 \ --file ./traces.json \ --mode deepening \ --seed-skill-id <skill id from the Skills tab>
Set your model key in the local environment, for example ANTHROPIC_API_KEY, before running. The tool builds the provider locally; choose it with --provider and --model. Traces stay on your machine and only the skill is uploaded.