LazySkills is a fast terminal user interface, written in Go and released under the MIT licence, that gives developers a single place to inspect, repair and manage the agent skills installed for coding agents such as Claude Code, OpenCode, Codex, Cursor and Gemini CLI.

What it is

LazySkills is a command-line application that puts a full-screen terminal UI over the skills installed on a machine or in a project. It collects project, global, universal and agent-specific skills into one view grouped by source, so a developer can see what came from the same repository, local folder or custom install, switch between agents to check which skills each one can actually use, and inspect metadata and rendered skill content before acting.

The problem it solves is what a skills installation looks like once it drifts. A skill can be present but unusable because its SKILL.md is missing, its frontmatter is invalid, its symlink is broken, its lock entry has vanished, or an agent-specific copy has become a ghost. Instead of debugging those conditions by hand across directories and lock files, LazySkills highlights them and points at the safe next command. It lives in the ecosystem of agent skills consumed by coding agents, and it replaces manual filesystem inspection and hand-maintained lock bookkeeping.

Key capabilities

• Shows project, global, universal and agent-specific skills together in one TUI, grouped by source.
• Switches agent context to report which skills are usable by Claude Code, OpenCode, Codex, Cursor, Gemini CLI and others.
• Flags broken installs: missing SKILL.md, invalid frontmatter, broken symlinks, missing lock entries and ghost agent skills.
• Previews actions before running them, showing skill metadata, rendered content and the exact command about to execute.
• Performs open, reinstall or update, remove, orphaned-lock pruning and bulk update or removal, with confirmation prompts for destructive operations.
• Scans local checkouts or GitHub skill sources for skills not yet installed, and searches skills.sh from inside the TUI to install at project or global scope.
• Provides headless commands: lazyskills doctor for a read-only health report with --json and --cwd, lazyskills restore to recover locked skills missing from disk, and lazyskills find --json "browser automation" for registry search without the TUI.

Who uses it and how

• Developers running several coding agents at once who need to confirm that a skill installed once is visible to each agent that should see it.
• Teams whose skills arrive from multiple sources — repositories, local folders, custom installs — and who need to catch broken symlinks and missing lock entries after moving a workspace.
• Script and CI authors who call lazyskills doctor --json --cwd /path/to/project for structured health output; the doctor command never changes skills or lock files.
• Anyone rebuilding a workspace from lock files with lazyskills restore when a locked skill is absent from disk.
• Skill hunters who browse skills.sh through the n key or through lazyskills find --json, previewing the install command before committing.

Getting started

Install with curl -fsSL https://lazyskills.sh/install | sh on macOS or Linux, brew install --cask alvinunreal/tap/lazyskills, the PowerShell script on Windows, or go install github.com/alvinunreal/lazyskills/cmd/lazyskills@latest, then run lazyskills from inside a project.

How it compares

No alternative or competing tool is named in the facts provided, so LazySkills stands alone in this registry. It does not replace the agents it serves: Claude Code, OpenCode, Codex, Cursor and Gemini CLI remain the consumers of the skills, while LazySkills sits beside them as the inspection and maintenance layer.

When to use it — and when not to

There is no server, database or SMTP configuration to operate: LazySkills is a local binary that reads and writes skill directories and lock files in the workspace, so the real operational surface is the skills themselves and the locks that record them. It suits developers comfortable in a keyboard-driven terminal, and anyone who needs a graphical dashboard or a hosted service should look elsewhere. The README excerpt also cuts off mid-sentence in its description of restore, so the documentation on recovering from lock files is only partially available and should be checked against the project's own repository.

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

brew install --cask alvinunreal/tap/lazyskills

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

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

lazyskills

lazyskills

lazyskills find --json "browser automation"

lazyskills doctor

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

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

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

lazyskills update