alvinunreal/lazyskills

Lazy Skills

Blazing-fast mission control for agent skills.

"I don't debug broken skills by hand - I have a TUI to be disappointed for me."

LazySkills is a blazing-fast terminal UI for managing agent skills. It gives you one place to see what is installed, which agents can use each skill, why visibility may be broken, and what actions are safe to run next.

• See every skill in one place - project, global, universal, and agent-specific skills in a single TUI.
• Check agent visibility - switch agents and see which skills are actually usable by Claude Code, OpenCode, Codex, Cursor, Gemini CLI, and many more.
• Spot broken installs fast - highlights missing SKILL.md, invalid frontmatter, broken symlinks, missing lock entries, and ghost agent skills.
• Preview before you act - inspect metadata, rendered skill content, and the exact command LazySkills is about to run.
• Safe skill actions - open, reinstall/update, remove, prune orphaned locks, or run bulk updates/removals with confirmation prompts.
• Discover more from a source - scan local checkouts or GitHub skill sources to find skills you have not installed yet.
• Find and install new skills - search skills.sh from inside LazySkills, preview the install command, then install to project or global scope with confirmation.

Recommended for macOS and Linux:

curl -fsSL https://lazyskills.sh/install | sh

Or use Homebrew:

brew install --cask alvinunreal/tap/lazyskills

Windows:

irm https://lazyskills.sh/install.ps1 | iex

Go users:

go install github.com/alvinunreal/lazyskills/cmd/lazyskills@latest

Then launch it:

lazyskills

Run LazySkills from a project:

lazyskills

Start with the left pane. It groups skills by source, so you can quickly see what came from the same repo, local folder, or custom install.

Useful keys:

LazySkills previews actions before running them, and destructive actions require confirmation.

For agent-friendly registry search without opening the TUI:

lazyskills find --json "browser automation"

Run a read-only health report for the current project:

lazyskills doctor

It ranks scan errors before warnings and shows the affected skill or workspace, path, and safe next step. Use structured output in scripts or other agents:

lazyskills doctor --json
lazyskills doctor --cwd /path/to/project

Doctor never changes skills or lock files. It reports findings and points to commands such as lazyskills restore when a locked skill is missing from disk.

Restore skills that are recorded in the project or global lock file but missing from disk:

lazyskills restore --global
lazyskills restore --project
lazyskills restore --all

Pass skill names to restore only those entries, or --yes to accept the preview non-interactively:

lazyskills restore --project code-review tdd
lazyskills restore --global --yes

Without a scope flag, restore checks both scopes. Before each install it rescans and revalidates that skill’s lock identity and restore command, then aborts without running remaining commands if the skill disappeared, its lock metadata changed, or its command changed—reporting any skills already restored. That narrows races with concurrent installs; it does not make restore fully race-free.

LazySkills can check for new releases and show the command to update your installation manually.

Run the update command directly from your terminal to check for updates and get upgrade instructions:

lazyskills update

Options:

• --check: Query if a newer version is available. Exits 0 if status is checked cleanly.
• --print-command: Print the command required to upgrade on your channel (e.g. brew upgrade) and exit.

When a newer version of LazySkills is available, an update notification will appear in the TUI footer: · U update (vX.Y.Z available)

Press U (capital U) from the inventory view to open the update info modal, which will display the release details and the specific terminal command you need to run to upgrade manually.

There are Lazy Skills stickers. Star the repo and you're entered into a draw to win some, shipped worldwide at no cost to you.

Winners are drawn from stargazers and announced in the sticker giveaway issue, tagged by their GitHub username, so you'll get a notification if it's you. Shipping details are arranged privately from there.

MIT - see LICENSE.