@kentcdodds/skills

@kentcdodds/skills

Intent

A general-purpose skills registry for agents: store, retrieve, edit, version, and revert reusable skill documents (markdown) whose durable home is this package's packageStorage (SQLite skills / skill_files / skill_versions). Agents discover skills with skillList, load them with skillGet, and evolve them with skillSave. Package workflows cannot open a user plain repo, so skillGet must not require a Kody repo named skills.

Forkers start with an empty registry in package storage. A leftover plain skills repo may still exist from an earlier migration; ./use-package-storage copies documents back into SQLite and switches the backend to legacy.

Skills you save also surface in Kody's general search tool and automatic context retrieval through a declared package retriever.

What it does

• List skills with descriptions complete enough to choose one (skillList)
• Load a whole skill or one file (skillGet)
• Create / update skill files with revision history (skillSave)
• Delete a file or an entire skill (skillDelete)
• Inspect recent versions and revert (skillHistory, skillRevert)
• Surface skills in Kody search / context via the package retriever
• Optional migration helpers between a leftover plain skills repo and package storage

Prerequisites / setup

1. No user secret is required — the registry lives in this package's packageStorage.
2. Forkers: registry starts empty. If you have documents in a leftover plain skills repo, run ./use-package-storage (agents: see AGENTS.md) to copy into SQLite.
3. Give each skill a clear description so agents can decide from skillList alone whether to load it. Prefer lower-kebab-case ids and a SKILL.md entry file.
4. Agents: see AGENTS.md for import paths and smoke checks.

Done when

• skillList returns without error (empty array is fine for a fresh fork)
• You can skillSave then skillGet a skill round-trip
• Saved skills appear in Kody search / context via the retriever when descriptions match
• You do not rely on opening a plain skills repo from package workflows