loopy vs Vibe-Skills
The two are close in size: 3.1k stars for loopy, 3.2k for Vibe-Skills. Over the days we have tracked them loopy moved +4335.7% and Vibe-Skills +41.1%, so loopy is growing faster right now.
They split the axes: loopy leads on model freedom, Vibe-Skills on privacy.
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
Combines a public, curated catalog of reusable agent loops with an installable in-agent skill that discovers, crafts, audits, runs, and prepares loops for publication.
- Stars
- 3.1k
- Tracked growth
- +4335.7%
- Maturity
- ●●●●●
- Last commit
- 41d ago
- Language
- JavaScript
- License
- MIT
- Cost to run
- Requires cloud agent provider (may incur provider cost)
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.1%
- Maturity
- ●●●●●
- Last commit
- 4d 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 | loopy | 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. | ●●●●● Whole-repo analysis | ●●●●● Whole-repo analysis |
Noise control How it keeps output volume down — severity thresholds, deduplication, incremental runs over new commits only. | ●●●●● Acceptance gating | ●●●●● Severity gating |
Customization How far it bends to your team: custom rules, prompts, style guides, per-path config. | ●●●●● Adapt & save loops | ●●●●● Config file options |
Privacy Whether your code stays on your own infrastructure: fully local, self-hostable, or cloud API only. | ●●●●● Depends on cloud agents | ●●●●● Self-hostable |
Model freedom Whether you can point it at any provider, or it is wired to one. | ●●●●● Multiple agents supported | ●●●●● 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 loopy if…
Easy setup — a one-command npx installer and in-agent slash-commands let you discover, adapt, run, and publish repeatable agent workflows with built-in acceptance checks and explicit approvals.
- Model freedom: Multiple agents supported (3/5 against 1/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.
- Privacy: Self-hostable (4/5 against 2/5)
What people want from each one
Forward-Future/loopy
foryourhealth111-pixel/Vibe-Skills
Questions people ask
Is loopy better than Vibe-Skills?
They split the axes: loopy leads on model freedom, Vibe-Skills on privacy. loopy is worth picking when easy setup — a one-command npx installer and in-agent slash-commands let you discover, adapt, run, and publish repeatable agent workflows with built-in acceptance checks and explicit approvals.
Which of loopy and Vibe-Skills keeps my code private?
loopy: Depends on cloud agents (2/5). Vibe-Skills: Self-hostable (4/5).
What does each one cost to run?
loopy: Requires cloud agent provider (may incur provider cost). Vibe-Skills: Free, self-hosted.
Full profiles: Forward-Future/loopy and foryourhealth111-pixel/Vibe-Skills. Everything else in Workflow & graph engines.