Lazyskills is live · free · last verified 5 Nov 2026 · viability monitor
Lazyskills
LazySkills is a free terminal UI that shows which of your 70+ coding agents can actually see each installed AI agent skill.
If you run three or more coding agents with hand-written skills, LazySkills earns its spot the first time a symlink breaks and you'd otherwise debug it blind. The switch-agents-to-see-what-loads check is what separates it from single-agent skill folder managers, and preview-before-execute keeps a bulk remove from wrecking a project. Free and open source, so the cost is the keymap and the agents it doesn't recognize.
Verdict generatedVerified 9d 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
- Anyone debugging why a coding agent can't find an installed skill
- Power users auditing which agents can actually see a specific 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 run a single coding agent with no hand-written skills installed, or if you need a GUI or hosted dashboard rather than a keyboard-driven terminal.
LazySkills is free and open source, published at $0 through a curl, Homebrew, Go, or PowerShell install — there is no seat count, usage metering, or upgrade path to budget for. That puts it in a different category from paid agent-tooling subscriptions: your only cost is the time to learn the keymap and the opportunity cost of adopting it instead of continuing to hunt through skill folders by hand.
In short
Lazyskills — LazySkills is a free terminal UI that shows which of your 70+ coding agents can actually see each installed AI agent skill. Best for Developers running three or more coding agents with custom skills installed, Teams standardizing agent skill setup across project and global scopes, Anyone debugging why a coding agent can't find an installed skill. Free to use.
What is Lazyskills?
Lazyskills — LazySkills is a free terminal UI that shows which of your 70+ coding agents can actually see each installed AI agent skill. Best for Developers running three or more coding agents with custom skills installed, Teams standardizing agent skill setup across project and global scopes, Anyone debugging why a coding agent can't find an installed skill. Free to use.
LazySkills is a free, open-source terminal UI for managing AI agent skills across a stack of 70+ coding agents — Claude Code, Cursor, Codex CLI, opencode, Gemini CLI, GitHub Copilot, Cline, Windsurf, Goose, Amp, Trae, Junie, OpenHands and the rest. It knows where every agent looks for skills, per project and globally, and shows exactly which agents can see each installed skill. That's the whole point: when a skill stops loading after you switch tools, LazySkills names the problem instead of leaving you guessing. It's built for developers who already run multiple agents with hand-written or registry-installed skills. Everything lands in one TUI. Installed skills are grouped by the source they came from — project, global, universal, or agent-specific — and you can cycle an agent filter to check which ones each tool can actually load. Diagnostics highlight the usual breakage: missing SKILL.md files, invalid frontmatter, broken symlinks, missing lock entries, and ghost agent skills. Nothing runs without a preview. You see the metadata, rendered skill content, and the exact command before any action fires, and bulk updates or removals come with confirmation prompts. From inside the app you can open a skill in your editor, reinstall, update, remove, prune orphaned locks, enable or disable individual skills or whole source groups, scan local checkouts or GitHub sources for skills you haven't installed, and search the skills.sh registry to install to project or global scope. The CLI mode exposes the same data as JSON — lazyskills find --json, lazyskills scan --json, lazyskills update --check — so a coding agent can search the registry or audit installed skills with no human at the keyboard. Install via curl, Homebrew, Go, or PowerShell on macOS, Linux, and Windows. It doesn't call an AI model itself; it's plumbing for the agents you already run, and it only covers the skill formats and locations it explicitly recognizes.
Key features
- Unified TUI for project, global, universal, and agent-specific skills, grouped by source
- Cross-agent visibility across 70+ coding agents
- Agent filter cycled with 'a', cleared with 'A'
- Scope filter for all, project, and global cycled with 'f', reset with 'F'
- Diagnostics for missing SKILL.md files, invalid frontmatter, and broken symlinks
- Diagnostics for missing lock entries and ghost agent skills
- Preview skill metadata, rendered content, and exact command before execution
- Safe skill actions: open, reinstall, update, remove, prune orphaned locks
- Bulk actions with confirmation prompts
- Enable or disable individual skills or entire source groups with 'e'
- Open skills directly in your editor with 'o'
- Discover skills from local checkouts or GitHub sources with 'd'
- Search the skills.sh registry and install to project or global scope with 'n'
- Agent-friendly JSON CLI: find --json, scan --json, update --check
- Install via curl, Homebrew, Go, or PowerShell on macOS, Linux, and Windows
Behind the verdict
Where this pays off: you have four coding agents installed, a dozen skills scattered across project and global scopes, and one of them quietly stopped working. Normally you'd go folder by folder comparing layouts. LazySkills puts the whole inventory on one screen, then lets you flip agents to see who can actually load what. That's the workflow it was built for, and it's a genuine time-saver. We'd reach for it when standardizing skill setup across a team, or when a broken SKILL.md or dead symlink is the suspected culprit. The diagnostics call those out directly rather than making you grep for them. Pass if you run a single agent with no custom skills. There's nothing to reconcile, and the keyboard-driven TUI is friction you don't need. The same goes if you want a hosted dashboard: this is a local terminal tool, not a web console. The JSON CLI mode is the sleeper feature. lazyskills scan --json gives a coding agent a full snapshot of installed skills and per-agent visibility, which makes it easy to wire up an audit step in CI or a script. Where it bites: the tool only covers the agent skill formats and locations it explicitly recognizes. Custom or obscure setups outside its list won't show up, and you'll be back to manual checks for those. Against a plain skills folder manager, the difference is cross-agent visibility — that's the feature you're really buying. Preview-before-execute and confirmation prompts on bulk ops are the safety net that makes a mass remove feel survivable.
Limitations
- LazySkills is a free, open-source terminal UI for inspecting and managing AI agent skills — it is not itself an AI model, so it has no underlying models.
- It runs as a keyboard-driven TUI installed via curl, Homebrew, Go, or PowerShell on macOS, Linux, and Windows.
- It manages skills across 70+ coding agents (Claude Code, Cursor, Gemini CLI, Windsurf, Goose, Kilo Code, Kiro, Qwen Code, Replit, Codex CLI, opencode, GitHub Copilot, Cline, Roo Code, Amp, Trae, Junie, OpenHands and more) but only covers the agent skill formats and locations it explicitly recognizes, so custom or obscure agent setups may not be fully covered.
- The interface is keymap-driven, so there is a real learning curve before the filters and actions feel automatic.
- Use cases that require a shared, hosted view of skills across a team fall outside what a local terminal tool does.
as of 2026-10-31
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.
Is Lazyskills still active?
Lazyskills is live · free · last verified 5 Nov 2026 · viability monitor.
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: November 2026
How we score →What do users say about Lazyskills?
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.
ResearchedDiscussed by users across 3 sources (YouTube, Product Hunt, GitHub) · researched Nov 13, 2026.
Weighted by the 8 posts each of 2 sources contributed.
- +Shows per-skill which of 70+ agents can actually load it
- +Groups skills by project, global, universal, and agent-specific source
- +Diagnostics catch missing SKILL.md, bad frontmatter, broken symlinks
- +Preview metadata and exact command before any destructive action
- +JSON CLI (find, scan, update --check) is genuinely agent-friendly
- −macOS flags the Homebrew cask as potentially harmful (still open)
- −No support for custom or private skill sources, only GitHub and GitLab
- −Narrow recognition scope means unsupported agents silently show nothing
- −Very little community discussion outside GitHub — few independent reviews
- −8 open issues with no public roadmap to judge what's coming
- • No direct monetary costs, but file-operation risk and time spent debugging coverage gaps are real
How we verified this
Every listed fact about Lazyskills — pricing, features, links, status — is re-read from the vendor's own pages by our verification pipeline and each change is logged with a date; the last pass ran on 5 Nov 2026. Analysis is drafted with AI models and checked against our editorial standards before publishing; see how we verify.
Verification history
We have re-verified Lazyskills 12 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.
- — changed pricing page
- — changed description, features, summary, who it suits, our verdict, who should skip it, pricing tiers
- — changed pricing tiers, switching out, pricing fit, who should skip it, use cases, switching in, setup time, summary, our verdict, who it suits, hidden costs, limitations, features, description
- — changed summary, pricing tiers, description, our verdict, who it suits, features, who should skip it
- — changed pricing page
- — changed SSL certificate
Showing the 6 most recent of 12 verification passes.
Free to cite with attribution — this page re-verifies continuously.
How much does Lazyskills cost in 2026?
Lazyskills: Free to use. Pricing last verified 5 Nov 2026.
Plans compared
Every published Lazyskills tier, its price as the vendor publishes it, who it fits, and what it adds over the tier below. The 12-month cost projection follows.
| Plan | Price | Billing | Who it's for |
|---|---|---|---|
| Open Source | Free | — | Developers running several coding agents who need to see which skills each one can load, and who want the same data as JSON for automationAdds: Free entry point: the full terminal UI with cross-agent visibility, diagnostics, preview-before-execute actions, the skills.sh registry search, and JSON CLI mode |
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.
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, published at $0 through a curl, Homebrew, Go, or PowerShell install — there is no seat count, usage metering, or upgrade path to budget for. That puts it in a different category from paid agent-tooling subscriptions: your only cost is the time to learn the keymap and the opportunity cost of adopting it instead of continuing to hunt through skill folders by hand.
Has Lazyskills' pricing changed?
No plan price for Lazyskills has moved since we began logging in Aug 2026; the pricing page is re-read on every verification pass.
Who should pick Lazyskills?
Pick Lazyskills if you are Developers running three or more coding agents with custom skills installed, Teams standardizing agent skill setup across project and global scopes, Anyone debugging why a coding agent can't find an installed skill, Power users auditing which agents can actually see a specific skill.
Look elsewhere if you are 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, Teams that need a hosted dashboard rather than a local CLI tool.
Skip it if Skip LazySkills if you run a single coding agent with no hand-written skills installed, or if you need a GUI or hosted dashboard rather than a keyboard-driven terminal.
GeneratedReal-world workflow fit
Concrete scenarios for the personas Lazyskills actually fits — and what changes day-one when you adopt it.
A skill that worked yesterday stops firing in Cursor. You launch lazyskills, press 'a' to cycle to Cursor, and see the skill isn't in the list Cursor reads. Running diagnostics surfaces a broken symlink and a missing lock entry, and you fix it from the TUI after previewing the reinstall command.
Outcome: Minutes of path-hunting replaced by a named diagnosis, and you confirm the fix by re-checking the agent filter before getting back to work.
Before onboarding two new engineers, you open LazySkills, press 'f' to cycle project and global scopes, and walk the inventory to check that each agent's view matches the intended skill set. Bulk actions are run with confirmation prompts so nothing is removed by accident.
Outcome: A shared, verified baseline of which skills each agent sees, established without writing a custom script.
An agent invokes lazyskills find --json or lazyskills update --check in a pipeline step to get a machine-readable inventory of installed skills and any pending updates, then acts on the output.
Outcome: Skill hygiene gets checked on every run instead of only when something visibly breaks.
Use cases
- Audit which skills your Claude Code agent can actually see before a big refactor
- Debug missing SKILL.md files or broken symlinks across several agents at once
- Filter skills by agent to confirm Cursor only has the tools you intended
- Bulk update or remove skills with confirmation prompts protecting you
- Discover uninstalled skills from local checkouts or GitHub sources and import them
- Clean up orphaned skill locks after reconfiguring an agent
- Search the skills.sh registry and install a new skill without leaving the TUI
- Generate a JSON inventory of installed skills for automation or CI
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 is one command (curl, Homebrew, Go, or PowerShell) on macOS, Linux, or Windows; first value usually lands within the first ten minutes as you type 'lazyskills' in a project and press 'a' to cycle agents. Allow an extra session to internalize the keymap ('/', 'a'/'A', 'f'/'F', 'n', 'e', 'o', 'd').
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-folder inspection: point LazySkills at the same projects and it groups every installed skill by source, replacing the directory-by-directory hunt.
- →From a single-agent skill manager: use the 'a' agent filter to extend visibility checks across your whole agent roster in the same TUI.
- →From ad-hoc shell scripts over skill directories: switch to lazyskills scan --json and lazyskills find --json for machine-readable output.
- ↗To a single-agent skill folder layout: the grouped-by-source inventory tells you exactly which files to copy where.
- ↗To a scripted audit: replicate the inventory using lazyskills find --json output as your data source before removing the TUI.
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
What are the best Lazyskills alternatives?
The closest alternatives to Lazyskills we list are Taste Skill, Harness Terminal and Crush. Ranked by direct product-type match, not category overlap.
| Alternative | Pricing | Starts at | Last verified |
|---|---|---|---|
| Taste Skill | Free | Free | — |
| Harness Terminal | Free | Free | — |
| Crush | Freemium | Pricing not published | — |
Alternatives to Lazyskills
View all
Taste Skill
Open-source SKILL.md rules that stop AI coding agents shipping generic frontend UI
Harness Terminal
Harness is a native Mac terminal for coding agents, with a built-in multiplexer and sessions that keep running after you close the window.
Tools that pair well with Lazyskills
Common stack mates teams adopt alongside Lazyskills, with the specific reason each pairing earns its keep.
Taste Skill
Open-source SKILL.md rules that stop AI coding agents shipping generic frontend UI
Harness Terminal
Harness is a native Mac terminal for coding agents, with a built-in multiplexer and sessions that keep running after you close the window.
Crush
Crush: agentic coding in your terminal with multi-model switching and LSP context
Lazyskills vs its closest rival
Lazyskills's closest head-to-head is with Spider Cloud.
Our Lazyskills vs Spider Cloud verdict written Jul 3, 2026 is more than 90 days old, so it is being re-reviewed against current data and is not shown.
Frequently asked questions
Categories
Best-of guides
Topics
For makers of Lazyskills
- Get a Verified Listing for Lazyskills ($39): a written decision within 1 working day.
- Free listing for another tool: Free reviews are decided in order, within 3 weeks of the review starting.
Used Lazyskills? Help shape our editorial sentiment research.