unlazy vs Vibe-Skills
The two are close in size: 3.1k stars for unlazy, 3.2k for Vibe-Skills. Over the days we have tracked them unlazy moved +164.7% and Vibe-Skills +41.6%, so unlazy is growing faster right now.
They split the axes: unlazy leads on model freedom and setup ease, Vibe-Skills on context depth.
Stars and commit dates come from our own daily tracking. The six axes are read off each project's documentation by our review pipeline, so they describe what a project says about itself, not what we measured in its code.
Where they stand today
Implements the Depth Tree decomposition with a strict, evidence-backed runnable gate ledger that enforces approvals and re-verification for substantial agent tasks.
- Stars
- 3.1k
- Tracked growth
- +164.7%
- Maturity
- ●●●●●
- Last commit
- 4d ago
- Language
- JavaScript
- License
- MIT
- Cost to run
- Free to run locally; external agent API costs may apply
Orchestrates and verifies multi-step work by discovering and assigning local Skill modules and enforcing end-to-end checks with resumable state.
- Stars
- 3.2k
- Tracked growth
- +41.6%
- Maturity
- ●●●●●
- Last commit
- 6d ago
- Language
- Python
- License
- Apache-2.0
- Cost to run
- Free, self-hosted
Six axes, head to head
Each axis runs 0 to 5. The label under a score is what that project's own docs claim, not a category average.
| Axis | unlazy | Vibe-Skills |
|---|---|---|
Context depth How much of your codebase it sees before it answers: the open diff, the diff plus related files, or the whole repository. | ●●●●● Diff + related files | ●●●●● Whole-repo analysis |
Noise control How it keeps output volume down — severity thresholds, deduplication, incremental runs over new commits only. | ●●●●● Approval & strict checks | ●●●●● Severity gating |
Customization How far it bends to your team: custom rules, prompts, style guides, per-path config. | ●●●●● Config files & templates | ●●●●● Config file options |
Privacy Whether your code stays on your own infrastructure: fully local, self-hostable, or cloud API only. | ●●●●● Self-hostable | ●●●●● Self-hostable |
Model freedom Whether you can point it at any provider, or it is wired to one. | ●●●●● Specific agents | ●●●●● Single provider |
Setup ease What it takes to get a first useful run out of it. | ●●●●● One-command install | ●●●●● Config + docs |
Which one to pick
Pick unlazy if…
Reproducible verification — use when you need strict, executable acceptance gates, recorded approvals, and re-verification for long-horizon agent work.
- Model freedom: Specific agents (3/5 against 1/5)
- Setup ease: One-command install (5/5 against 3/5)
Pick Vibe-Skills if…
Privacy-first — runs on your host and coordinates local Skill libraries to plan, execute, and verify complex multi-step tasks.
- Context depth: Whole-repo analysis (5/5 against 3/5)
What people want from each one
foryourhealth111-pixel/Vibe-Skills
Questions people ask
Is unlazy better than Vibe-Skills?
They split the axes: unlazy leads on model freedom and setup ease, Vibe-Skills on context depth. unlazy is worth picking when reproducible verification — use when you need strict, executable acceptance gates, recorded approvals, and re-verification for long-horizon agent work.
Which of unlazy and Vibe-Skills keeps my code private?
unlazy: Self-hostable (4/5). Vibe-Skills: Self-hostable (4/5).
What does each one cost to run?
unlazy: Free to run locally; external agent API costs may apply. Vibe-Skills: Free, self-hosted.
Full profiles: Leonxlnx/unlazy and foryourhealth111-pixel/Vibe-Skills. Everything else in Workflow & graph engines.