Skil
Also on the command line

Prefer the terminal? There's a CLI for that

Same scan, toggle, and doctor loop — just headless. No brew tap yet. Clone it, build it, run it from your project folder.

  • No login or API key — it reads your local repo.
  • Toggle is the write. On writes the live pair now; off parks it.
  • `skil doctor` catches idle-cost and conflicts before CI does.
install
git clone https://github.com/eric-huychung/skil.git
cd skil && npm install && npm run build
npx skil --help

Then hop into your project folder and run npx skil. It reads whatever directory you're standing in.

zsh — skil
# from your project folder$skil scan✓ Found 52 skills across 4 sources# toggle on — writes .agents + .claude$skil enable build# flag idle-cost, conflicts, dead skills$skil doctor✓ build: 340 tok · 0 warn

Command reference

Same groups as the README. skil --help if you get lost.

Find

  • skil searchtop 10 by installs
  • skil search --trendingwhat's hot
  • skil search <name>lookup by name
  • skil suggestpicks for this repo
  • skil install <id>drop that skill in

Skills

On = live pair. Off = parked, not deleted. Not skil enable — that one’s for commands.

  • skil scanfind SKILL.md folders. leftover-only copies into canonical homes.
  • skil skillscatalog, on / off
  • skil skills enable <id>turn a skill on
  • skil skills disable <id>park it

Commands

A command is a workflow (build → /build). Adding a skill doesn’t turn it on.

  • skil create <name>make a command (starts off)
  • skil listwhat's on the map
  • skil add <command> <skill>put a skill on a command
  • skil remove <command> <skill>take it off
  • skil enable <command>turn the command on
  • skil disable <command>park it
  • skil delete <command>drop the command

Rules

  • skil ruleslist shared AGENTS.md sections
  • skil rules enable <id>turn a section on
  • skil rules disable <id>turn it off

Eval

  • skil doctorcheckup per command
  • skil doctor <command>that command's findings
  • skil usagehow often a skill actually got read