Lazyskills
LazySkills is a terminal UI for managing AI agent skills across 70+ coding agents from one keyboard-driven screen.
If you have three or more coding agents and hand-written skills, LazySkills pays for itself in the first broken symlink you didn't have to debug blind. It is free and open source, so the only cost is learning the keymap — roughly ten minutes. Single-agent users with no custom skills will open it once and close it.
Verified 6d ago · liveness 44/100 · cite: rightaichoice.com/tools/lazyskills
- Developers running three or more coding agents with custom skills installed
- Teams standardizing agent skill setup across project and global scopes
- Power users auditing which agents can actually see a specific skill
- Debugging why a coding agent can't find an installed skill
- Users who prefer a GUI over a keyboard-driven terminal interface
- Non-developers with no command-line comfort
- Anyone using a single agent with no custom skills installed
We scan live Reddit threads, YouTube comments, X posts, G2 reviews and other communities — and hand you an honest verdict in under a minute.
- Honest verdict, not marketing
- Real pros & cons from real users
- Attributed quotes with receipts
3 free scans · no card needed
Skip LazySkills if you use a single coding agent with no custom skills, prefer graphical interfaces over the terminal, or need team-wide governance that a local-only tool can't provide.
It's a terminal tool, so there's a learning curve and no GUI—if you're not comfortable in a shell, you'll spend time getting up to speed.
LazySkills is free and open source, so cost is not a factor—unlike proprietary agent managers that charge per seat. It fits individual developers and small teams that standardize on agent skills, with no budget ceiling.
In short
Lazyskills — LazySkills is a terminal UI for managing AI agent skills across 70+ coding agents from one keyboard-driven screen. Best for Developers running three or more coding agents with custom skills installed, Teams standardizing agent skill setup across project and global scopes, Power users auditing which agents can actually see a specific skill. Free to use.
What people actually say about Lazyskills — is it worth it?
We ran a structured research pass across product reviews, community discussions, and post-purchase forum threads to surface the patterns vendors won't publish themselves. Below: the recurring strengths, the hidden costs people mention most, and the cohort that consistently regrets adopting this tool.
1 mentions across 1 source (GitHub) · researched Jul 3, 2026.
Average across the 1 source that answered — each source counts once, not each post.
- +Consolidates all skills into one terminal dashboard.
- +Cross-agent visibility for Claude Code, Cursor, OpenCode, Codex, Gemini.
- +Instant diagnostics: missing SKILL.md, dead symlinks, orphaned locks.
- +Safe preview of actions before execution.
- +Bulk update/remove with confirmation prompts.
- −Very limited community feedback makes reliability assessment speculative.
- −17 open issues may indicate instability or feature gaps.
- −No dedicated support beyond GitHub issues.
- −Requires comfort with terminal and CLI tools.
- −Not applicable for non-agent workflows or single-agent setups.
- • None. Free and open-source.
Viability Score
How well maintained and how widely used is Lazyskills? Built from what the vendor actually publishes (docs, changelog, tutorials, integrations, pricing), whether the site is live, and how much real users discuss it. How we calculate this
Last calculated: September 2026
How we score →Key Features
- Unified TUI for project, global, universal, and agent-specific skills
- Cross-agent visibility for 70+ coding agents
- Diagnostic checks for missing SKILL.md, invalid frontmatter, broken symlinks, lock entries, ghost skills
- Preview metadata, rendered content, and exact command before executing
- Safe skill actions: open, reinstall, update, remove, prune orphaned locks
- Bulk actions with confirmation prompts
- Enable or disable individual skills or entire source groups
- Open skills directly in your editor
- Skill discovery from local checkouts or GitHub sources
- Search skills.sh registry from inside the TUI and install to project or global scope
- Agent-friendly CLI mode with JSON output: find --json, scan --json, update --check
- Keyboard-driven interface with single-key shortcuts and context help via ?
- Search and filter skills by name as you type with /
- Cycle agent filter and scope (all/project/global) with shortcuts
- Runs on macOS, Linux, and Windows via curl, Homebrew, Go, or PowerShell
About Lazyskills
LazySkills is a free, open-source terminal UI for managing AI agent skills across 70+ coding agents, including Claude Code, Cursor, Gemini CLI, Windsurf, Goose, Kilo Code, Kiro, Qwen Code, Codex, opencode, GitHub Copilot, Cline, Roo Code, Amp, Trae, Junie, and OpenHands. It knows where each agent looks for skills — project, global, universal, or agent-specific — and shows every installed skill grouped by the source it came from, so you can see at a glance which agents can actually use a given skill. Diagnostics are where it earns its keep. LazySkills flags missing SKILL.md files, invalid frontmatter, broken symlinks, missing lock entries, and ghost agent skills. Before running anything, you can inspect the metadata, the rendered skill content, and the exact command about to execute. Safe actions cover open, reinstall, update, remove, and pruning orphaned locks, with confirmation prompts on bulk operations, plus enable/disable toggles for individual skills or whole source groups. Discovery happens without leaving the TUI: scan local checkouts or GitHub sources for skills you have not installed, or search the skills.sh registry and install straight to project or global scope. An agent-friendly CLI mode exposes the same data as JSON — `lazyskills find --json`, `lazyskills scan --json`, and `lazyskills update --check` — so a coding agent can query the registry or audit installed skills with no human at the keyboard. Installation is a one-liner via curl, Homebrew, Go, or PowerShell, and it runs on macOS, Linux, and Windows with a fully keyboard-driven interface (press ? for context help, / to search as you type). Agent-specific managers show you one agent's world; LazySkills shows the whole stack, which is the difference when skills start disappearing between tools.
Behind the Verdict
The case for LazySkills is narrow but sharp: you run several coding agents, you install skills into them, and something stops working. An agent can't find a skill, a symlink rots, frontmatter is malformed, a lock entry outlives the skill it points to. Agent-specific tooling won't tell you any of that, because each one only sees its own directory. LazySkills reads across all of them and puts the conflicts side by side. We'd reach for it during setup audits. Switch the agent filter with `a`, flip scope between all, project, and global with `f`, and you get a fast answer to "which agents can actually use this skill?" That is the question that eats an afternoon when it goes wrong. The preview step is the part worth trusting. LazySkills shows metadata, rendered content, and the exact command before running it — important when a bulk remove or prune could touch skills you installed months ago. Confirmation prompts on bulk actions back that up. Where it bites: this is a terminal app with a keymap, and there is no GUI to fall back on. If you live in a mouse-driven editor and never touch a shell, the friction is real. Windows users need PowerShell or WSL. And if you use exactly one agent with no custom skills, there is nothing here you don't already have. The closest alternative isn't another tool so much as doing it by hand — reading each agent's skill directory and hoping you remember which agent reads where. That works until it doesn't. LazySkills is the cheaper habit once you are past two agents.
Researching Lazyskills? Get your full AI stack in 60 seconds.
Free, no signup — tell us your goal and get tools matched to your budget & existing stack.
Real-world workflow fit
Concrete scenarios for the personas Lazyskills actually fits — and what changes day-one when you adopt it.
You use Claude Code and Cursor daily, each with custom skills. You run lazyskills in a project to see a unified view, then filter by agent to confirm Cursor only sees its intended skills.
Outcome: You spot a broken symlink on one skill and fix it via the safe action, ensuring both agents have working skills.
You want to add new skills to your setup. You press 'n' to search the skills.sh registry, preview the install command, and install a testing skill to project scope.
Outcome: You've added a new skill without leaving the terminal, and the skill is immediately available to your agents.
You script a pre-commit hook that runs 'lazyskills update --check' and 'lazyskills find --json' to audit installed skills and query for new ones.
Outcome: Your CI can proactively warn about broken skills or suggest updates, keeping your agent environment healthy.
Use Cases
- Audit which skills your Claude Code agent can actually see
- Debug missing SKILL.md or broken symlinks across multiple agents
- Filter skills by agent to ensure Cursor only has intended tools
- Bulk update or remove skills with safety confirmations
- Discover new skills from GitHub and import them into your setup
- Clean up orphaned skill locks after agent reconfigurations
- Search the skills.sh registry and install new skills without leaving the TUI
- Generate a JSON inventory of skills for automation
Limitations
- LazySkills is a local terminal UI tool with no hosted backend; it manages agent skills by inspecting files on the user's machine.
- It supports 70+ coding agents (e.g.
- Claude Code, Cursor, Gemini CLI, Windsurf, Goose, Kilo Code, Kiro, Qwen Code, Replit) for the skill formats and locations it explicitly recognizes, so custom or obscure setups may not be fully supported.
- It runs on macOS, Linux, and Windows, with installation via curl, Homebrew, Go, or PowerShell.
- The tool requires a terminal environment.
as of 2026-09-01
Verification history
We have re-verified Lazyskills 8 times since . Each pass re-reads the vendor's own pages and re-checks every listed field against that evidence; passes where nothing had changed are marked as such.
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-checked, vendor evidence unchanged
- — re-checked, vendor evidence unchanged
- — re-checked, vendor evidence unchanged
Showing the 6 most recent of 8 verification passes.
Free to cite with attribution — this page re-verifies continuously.
12-month cost
Project the real annual outlay, including the implied monthly cost when only an annual tier is published.
Vendor list price only. Add-on usage, seat overages, and contract minimums are surfaced under Hidden costs & gotchas.
Plans compared
For each published Lazyskills tier: who it actually fits, and what it adds vs. the previous tier. Cross-reference the cost calculator above for projected annual outlay.
Open Source
$0
Ideal for
Any developer or team that wants a free, open-source tool to manage agent skills without budget constraints—from solo developers to small teams standardizing skills.
What this tier adds
Starting tier: all features included at no cost—full TUI, 70+ agent integrations, diagnostics, discovery, and CLI mode.
Where the pricing makes sense
The company stage and team size where Lazyskills's pricing actually pencils out — and where peers do it cheaper.
LazySkills is free and open source, so cost is not a factor—unlike proprietary agent managers that charge per seat. It fits individual developers and small teams that standardize on agent skills, with no budget ceiling.
Setup time & first value
How long it actually takes to get something useful out of Lazyskills — broken out by persona, not the marketing-page minute.
Install with one command (curl, Homebrew, Go, or PowerShell) and launch by typing 'lazyskills'—you'll see your skills inventory within minutes. Reading the keymap reference and trying the shortcuts takes an additional 10-15 minutes to feel fluent.
Switching to or from Lazyskills
How to bring data in from common predecessors and how to get it back out — written for the switcher, not the buyer.
- →From manual skill folders: Run 'lazyskills scan' to discover skills in local checkouts and import them into the TUI.
- ↗To a hosted governance platform: If you need team-wide control, export your skills inventory via 'lazyskills find --json' and migrate to a server-based solution manually.
Integrations
Resources & Guides
Tutorials & Learning
YouTube returned 6 videos for “Lazyskills”, and we withheld 6: 6 could not be judged, because “Lazyskills” is a single word that other videos use for other things. We are showing none, because we could not prove any of them are about Lazyskills.
Official links
Tools that pair well with Lazyskills
Common stack mates teams adopt alongside Lazyskills, with the specific reason each pairing earns its keep.
Featured Head-to-Head Comparisons
Lazyskills vs Spider Cloud
Choose Lazyskills if you need a free, terminal-based tool to manage and diagnose skills across multiple AI coding agents. Choose Spider Cloud if you need a powerful, low-cost web scraping API with AI extraction for feeding real-time data into your AI workflows. Both are developer-focused but serve completely different purposes.
Lazyskills vs Presto Voice
Lazyskills and Presto Voice serve completely different domains: one is a free developer tool for managing AI agent skills across multiple coding assistants, the other is an enterprise voice AI solution for drive-thru order automation. Your choice depends entirely on whether you are a developer debugging agent skills (Lazyskills) or a QSR operator wanting to boost drive-thru revenue (Presto Voice). There is no overlap in use cases.
Lazyskills vs Temporal Ai
For developers juggling multiple AI coding agents and needing to verify skill visibility, Lazyskills is a free, lightweight solution. For teams building production-grade AI workflows that must survive failures and scale, Temporal's durable execution platform is the clear choice despite new usage-based costs.
Alternatives to Lazyskills
View allPopular in Code & Development
Bito
Bito's Governor is an AI model router and code context engine that cuts coding agent spend by grounding every request in your codebase.
Poolside AI
Open-weight agentic coding models — Laguna XS 2.1 and Laguna S 2.1 — built for secure on-prem and air-gapped enterprise AI.
Frequently Asked Questions
Categories
Best-of guides
Topics
Used Lazyskills? Help shape our editorial sentiment research.