What people actually say about Lazyskills

29 mentions across 3 sources · 62% positive · researched Nov 13, 2026

YouTube, Product Hunt, GitHub

What users praise

  • • 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

What frustrates them

  • • 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

This is a summary. The full report adds every quote we found, a per-source breakdown, recurring themes, hidden costs and the learning curve — run a free scan below, or see the full Lazyskills review.

What comes up again and again about Lazyskills

Recurring themes across everything we collected, with where each one showed up.

  • Cross-agent skill visibility solves a real debugging headache

    praised · seen on Product Hunt, GitHub

  • File operations need caution after the symlink deletion scare

    criticised · seen on GitHub

  • Coverage gaps when agents or layouts aren't recognised natively

    criticised · seen on GitHub

  • Missing private and custom source support limits real-world use

    criticised · seen on GitHub

  • Maintainer is responsive and ships fixes quickly

    praised · seen on GitHub

  • Install friction on macOS due to cask security warning

    criticised · seen on GitHub

How hard is Lazyskills to learn?

Users describe it as intermediate · typically A few hours to get going

Where people get stuck

  • • Memorising TUI keybindings (a, A, f, F, e, o, d, n)
  • • Understanding which skill sources map to which agents
  • • JSON CLI flags are under-documented

Who Lazyskills actually suits

Works well for

  • • Developers running Claude Code, Cursor, and Codex in parallel
  • • Teams with hand-written or registry-installed skills across agents
  • • Anyone debugging why a skill stopped loading after a tool switch
  • • Agent authors needing JSON audit and registry search via CLI

Not the right fit for

  • • Single-agent users who never migrate tools
  • • Teams needing private Git hosting or local-only skill sources
  • • Users who want a GUI, not a terminal keybinding workflow

What people are discussing right now

Discussion volume is low and trending stable

  • Cross-agent skill visibility
  • OpenCode project skill support (now fixed)
  • Symlink deletion bug (now fixed)
  • macOS Homebrew cask warning
  • Custom and private source requests
Back to Lazyskills
LIVE MARKET SENTIMENT

What people really think about Lazyskills

A real-time sweep of the open web — social media, forums, review sites, video reviews and live community discussions — distilled into one honest verdict with the actual mentions behind it.

Real-time Live mentions Unbiased Downloadable
No card needed

What's inside your Lazyskills report

Everything you need to decide — distilled from real, current user opinion.

Live mentions

The actual posts, reviews & complaints about Lazyskills — with links and dates.

Honest verdict

A straight answer on whether it lives up to the hype — and who it’s really for.

Praise & gripes

What users genuinely love and the frustrations that keep coming up.

Real quotes

Representative voices from real users, not marketing copy.

Recurring themes

The patterns across hundreds of opinions, surfaced at a glance.

Red flags

Hidden costs and dealbreakers people only discover after signing up.

How it works

1

Sign up free

Create an account in seconds — get 5 free scans, no card.

2

We sweep the web

Live social media, forums, reviews & video opinions — in ~30–60s.

3

Get your report

An honest, downloadable verdict with the real mentions behind it.

Ready to see the real verdict on Lazyskills?

Your scan is ready in under a minute · $1.

Compare Lazyskills head-to-head

See how it stacks up against the tools people weigh it against.

Top alternatives to Lazyskills

Researching options? Explore the closest alternatives.

Check sentiment on these too

Run a live scan on the alternatives before you decide.

Lazyskills — questions buyers ask

What do people complain about most with Lazyskills?

The complaints that recur most often are macOS flags the Homebrew cask as potentially harmful (still open), no support for custom or private skill sources, only GitHub and GitLab and narrow recognition scope means unsupported agents silently show nothing. Drawn from 29 mentions across 3 sources.

What do users like about Lazyskills?

Users consistently praise shows per-skill which of 70+ agents can actually load it, groups skills by project, global, universal, and agent-specific source and diagnostics catch missing SKILL.md, bad frontmatter, broken symlinks.

Is Lazyskills hard to learn?

Users describe it as intermediate; most people are up and running in a few hours; the usual sticking points are memorising TUI keybindings (a, A, f, F, e, o, d, n) and understanding which skill sources map to which agents.

Who should not use Lazyskills?

Based on what users report, it is a poor fit for single-agent users who never migrate tools, teams needing private Git hosting or local-only skill sources and users who want a GUI, not a terminal keybinding workflow.

What are people saying about Lazyskills right now?

Discussion volume is low and trending stable. Current topics: cross-agent skill visibility, OpenCode project skill support (now fixed) and symlink deletion bug (now fixed).

How current is this report?

Each scan runs live the moment you click — it reflects what people are saying now, and every report lists the dated mentions behind it.

Can I download it?

Yes — download the full report as a polished, shareable PDF.

← Back to LazyskillsBrowse Code & DevelopmentAll AI toolsAll comparisons