<div align="center">

🍳 skillet

A package manager for AI agent skills

Find, install, version and share SKILL.md skills — from a Git-backed registry. No server, no account, no lock-in. Just npx @jnmetacode/skillet add <skill>.

npx @jnmetacode/skillet add pdf

English | 简体中文

</div>

---

Agent Skills are taking over — a SKILL.md folder that teaches an agent a new capability (read PDFs, build slide decks, scrape the web…). But sharing them is a mess: you copy-paste from random repos, pin nothing, and have no way to discover what exists.

skillet is npm/brew for skills. One command to install a skill into your project, a lockfile so it's reproducible, and a registry that's just a JSON file in a Git repo — so there's nothing to host and anyone can contribute with a PR.

npx @jnmetacode/skillet search pdf            # discover
npx @jnmetacode/skillet add pdf               # install into .claude/skills/
npx @jnmetacode/skillet list                  # see what's installed
npx @jnmetacode/skillet new my-skill          # scaffold your own

Why skillet

• Skills are files, not dependencies. Like shadcn/ui, skillet copies the skill into your repo (.claude/skills/<name>/) where you can read and tweak it — not into an opaque node_modules.
• Reproducible. Every install records the exact commit SHA in skillet.lock.json. Commit it, and your whole team gets byte-identical skills with skillet install (the npm ci of skills). Pin a single install with add owner/repo#<sha>; skillet update re-resolves a branch/tag to its latest.
• Zero infrastructure. The registry is a JSON index in a Git repo, served over raw GitHub. No backend, no database, no API keys. Adding a skill is a PR.
• Install from anywhere. A registry name, any owner/repo[/path][#ref], or a local folder.
• Zero dependencies. Pure Node built-ins + your system git. The whole CLI is a few hundred readable lines.

Install targets

npx @jnmetacode/skillet add pdf                              # from the registry
npx @jnmetacode/skillet add anthropics/skills/skills/pptx    # any GitHub repo + subpath
npx @jnmetacode/skillet add owner/repo#v2.1.0                # a tag/branch
npx @jnmetacode/skillet add owner/repo#<commit-sha>          # pin to an exact commit
npx @jnmetacode/skillet add ./skills/my-local-skill          # a local folder

Skills install into .claude/skills/ by default (the common 2026 convention). Change it per-project with skillet init or --dir.

Use it from Claude (MCP)

skillet speaks the Model Context Protocol, so Claude Desktop / Claude Code can search and install skills for you — "find a PDF skill and install it" just works. Add to claude_desktop_config.json (or a project .mcp.json):

{
  "mcpServers": {
    "skillet": {
      "command": "npx",
      "args": ["-y", "@jnmetacode/skillet", "mcp"]
    }
  }
}

Tools exposed: skillet_search, skillet_install (registry-only, name-validated), skillet_list. Zero dependencies — a few hundred lines of JSON-RPC over stdio.

Browse the registry

npx @jnmetacode/skillet gallery        # builds a static, searchable HTML gallery → site/

skillet gallery renders registry/index.json into a single self-contained page (search, copy-to-install, links) — zero backend. The included GitHub Pages workflow rebuilds and publishes it automatically whenever the registry changes, so the registry has a shareable home.

Authoring a skill

npx @jnmetacode/skillet new web-scraper      # creates web-scraper/SKILL.md from a template
# edit it…
npx @jnmetacode/skillet validate ./web-scraper

A skill is just a folder with a SKILL.md:

---
name: web-scraper
description: Scrape pages and extract structured data; use when the user wants web content.
version: 0.1.0
license: MIT
keywords: [scrape, http]
---

# web-scraper
Instructions the agent reads… plus any supporting scripts in the same folder.

Push it to GitHub, then open a PR adding one entry to registry/index.json — see docs/SPEC.md.

Commands

skillet search [query]	search the registry
skillet add <ref>	install a skill (registry name / owner/repo[/path][#ref] / ./local)
skillet install	install all locked skills at their pinned commits (npm ci-style)
skillet list	list installed skills
skillet remove <name>	uninstall
skillet update [name]	re-install tracked skill(s) at the latest ref
skillet new <name>	scaffold a new skill
skillet validate [path]	validate a SKILL.md
skillet gallery	build a static, searchable registry gallery
skillet mcp	run as an MCP server (stdio) for Claude/agents
skillet init	write skillet.json config

Flags: --force, --dir <path>, --registry <url|path>, --json.

How it works

  skillet add pdf
        │  resolve name in registry index (raw GitHub JSON)
        ▼
  git clone --depth 1 anthropics/skills      ← your system git, partial clone
        │  copy skills/pdf/ → .claude/skills/pdf/
        ▼
  pin commit SHA in skillet.lock.json

The "registry" is one JSON file. That's the whole backend.

Compatibility

Works with anything that reads SKILL.md skill folders (Claude Code / Claude Agent Skills and compatible runtimes). skillet is just discovery + install + versioning around the open SKILL.md format — it doesn't lock you to a runtime.

Status

Early MVP — discovery, install (registry / GitHub / local), lockfile pinning, authoring and validation all work today. Star/watch to follow along; PRs and new registry entries are the most useful contribution right now.

Sibling projects

Part of a small, local-first, zero-dependency toolkit for building AI agents — see the toolkit overview & end-to-end recipe:

• 🍳 skillet — a package manager for agent skills (this repo)
• 🔭 tracelet — local DevTools to debug agent runs
• 🧠 engram — a local, private memory layer for agents (and you)

License

MIT — see LICENSE. (Skills installed through skillet keep their own licenses.)