Skip to content

README.md

56 lines · 2.3 KB · Markdown
Raw

@kody/skills

Official community helpers for a reusable agent skill registry.

Share this listing: https://kody.codes/@kody/skills

Intent

Give every Kody account a generic skills registry: store, retrieve, edit, version, and revert reusable skill documents (markdown). Agents discover skills with skill_list, then load them with skill_get. Edits go through skill_save (and delete/history/revert). Versioning is real git when the account uses a plain skills repo; otherwise the package keeps documents in its own packageStorage(). Success means a forked copy can list, read, dry-run a mutation, then write — without Kent-only skills, personal remotes, or a shared platform registry.

Live @kody/skills storage is the official package bucket. Fork first (or invoke your copy) so skills stay in your account.

What it does

  • List and search reusable skill documents (name + description index)
  • Load a skill's markdown (and optional reference files)
  • Save, delete, history, and revert with optional dryRun
  • Optionally migrate durable storage to a plain per-account skills git repo (live-at-HEAD for bulk edits)

Prerequisites / setup

Zero-auth. No OAuth, API key, or bot token.

  1. Fork or install https://kody.codes/@kody/skills so the account owns a saved skills package. Each fork starts with an empty registry.
  2. Prefer static imports of your fork (kody:@you/skills/...) so list/get/save use your bucket. The live official package is shared platform storage.
  3. Optional git durable home: create a plain repo named skills, push an initial commit, then migrate reads with migrate-to-repo (preview with dryRun: true first). Do not hard-code another account's git remote.

Agents: see AGENTS.md for import paths, smoke/dryRun snippets, bulk git-lane notes, and conventions.

Done when

  • The account has its own forked skills package (empty registry is fine)
  • skill_list returns an array; skill_save({ dryRun: true }) previews a write
  • Optional: plain skills repo exists and migrate-to-repo has been reviewed before switching reads

Branding

The community icon is a simple skills / document mark for the official registry listing. Paths are unmodified.