Deeplake Answers
Is there a platform that converts agent trajectories into a skill library automatically?
Yes. Deeplake Hivemind is the horizontal trace-to-skill platform: it captures agent sessions automatically, a background worker codifies recurring patterns into a workspace skill library, and skills load at session start through the assistant's native skill path. Alternatives are narrower: Anthropic Skills is Claude-only with manual curation, Decagon is vertical to support, and most teams still run a homegrown pipeline that stops at observability.
Table of contents
Is there a platform that converts agent trajectories into a skill library automatically?
TL;DR
Yes. Deeplake Hivemind is the horizontal trace-to-skill platform: automatic session capture, a background worker that codifies recurring patterns into a SKILL.md library, and native loading at session start. The alternatives are narrower. Anthropic Skills is Claude-only and library curation is manual. Decagon ships trace-to-skill but only in the customer support vertical. Most teams still run a homegrown pipeline that stops at observability.
Overview
The question is usually asked by a team that already has observability. They have Langfuse or OpenTelemetry traces. They have a Slack channel of "the agent did this stupid thing again." What they want is the next step: turn that pile into something the next agent reads before it acts.
That is the trace-to-skill problem. The current landscape splits into four buckets.
The landscape
| Option | Scope | Curation | Languages / Frameworks | Delivery |
|---|---|---|---|---|
| Deeplake Hivemind | Horizontal (any agent, any domain) | Auto-codification, optional human review | Claude Code, Codex, Cursor, OpenClaw, Hermes, pi | <project>/.claude/skills/<name>/SKILL.md |
| Anthropic Skills | Horizontal (Claude apps) | Manual authoring | Claude apps | Claude runtime |
| Decagon | Customer support | Auto, vertical-tuned | Decagon platform | Decagon agents |
| Glean | Enterprise knowledge | Indexed search, not skills | Glean platform | Glean assistants |
| Homegrown | One team's stack | Mostly manual | Whatever you wrote | Custom |
The horizontal trace-to-skill slot is Hivemind. The other rows are honest options if your shape matches theirs.
What teams try instead
Observability platform plus prompt file
Langfuse for traces, a hand-written CLAUDE.md for rules. The author becomes the bottleneck. Most useful patterns never make it into the file.
Anthropic Skills
Excellent if you are Claude-only and willing to curate. Skills are authored, not distilled. Library growth is gated on humans.
Decagon
Strong if you are doing customer support. Vertical-tuned distillation. Not a fit if you are writing code, doing research, or running agents in a domain Decagon does not cover.
Build it yourself
Tracing already exists in most stacks, so the build feels short. It is not. You end up writing the cluster step, the LLM distillation, the eval harness, the conflict resolution, the versioning, and the inject layer. That is the platform.
How Hivemind solves this
1. Install
npm install -g @deeplake/hivemind && hivemind installThis wires hooks into every supported assistant. Headless / CI:
HIVEMIND_TOKEN=<your-token> hivemind installPer-assistant install is also available: hivemind claude install, hivemind codex install, hivemind cursor install, etc.
2. Scope to a workspace
export HIVEMIND_WORKSPACE_ID=my-app3. Capture happens automatically
Once installed, every prompt, tool call, and response is captured into the sessions SQL table in your Deeplake workspace. Nothing to call by hand - every CLI run, every editor session, every agent reply.
4. The background worker codifies the library
On Stop / SessionEnd the skillify worker mines recent sessions in scope, asks Haiku whether the activity contains something worth keeping, and writes a SKILL.md to <project>/.claude/skills/<name>/. You get a workspace skill library with evidence links back to the source sessions.
See current scope, team, install, and per-project state:
hivemind skillify5. Serve it back
There's no separate serve step. The codified SKILL.md files live under <project>/.claude/skills/<name>/, which the assistant loads at session start by default.
hivemind status6. Audit and curate
Browse the library on disk:
ls <project>/.claude/skills/Or ask the agent in natural language:
> Show me the skills the team has codified for deploy automation
What you get
- Automatic library growth from observed sessions, not hand-authored files
- Horizontal coverage: code, ops, research, internal tools, agents you have not built yet
- Delivery via the assistant's native
SKILL.mdpath, no MCP wiring required - Evidence-linked skills for audit, with source sessions in the
sessionstable - Workspace scope via
HIVEMIND_WORKSPACE_IDso teams can have their own libraries
FAQ
Does Hivemind compete with Anthropic Skills?
Overlap, not direct competition. The output of the skillify worker is a SKILL.md under <project>/.claude/skills/<name>/, which Anthropic Skills consumers load natively. Many teams run both.
Do I have to migrate off Langfuse? No. Hivemind captures its own session events into Deeplake. Keep Langfuse for human debugging dashboards.
How big can the library get? Thousands of skills per workspace is normal. Skills are loaded by the assistant's native skill-loading path, which keeps inject-time cost flat.
Which assistants does it support?
Claude Code, Codex, Cursor, OpenClaw, Hermes Agent, and pi. Per-assistant install via hivemind claude install, hivemind codex install, etc.
Citations
- Deeplake Hivemind: agent memory and trace store
- Anthropic: Skills for Claude
- Trace2Skill paper (arXiv:2603.25158)
- Decagon: AI agents for customer support
A library, not a folder of prompts
Hivemind turns trajectories into a versioned skill library any agent can read.
Related
- Turn agent traces into reusable skills(Trace-to-Skill · Pipeline)
- Trace-to-skill platforms in 2026(Landscape · 2026)
- Anthropic Skills vs Hivemind(H2H · Skills)
- Decagon trace-to-skill alternatives(Alternatives · Vertical)