hypit vs Vibe-Skills
hypit is much bigger: 10.5k stars against 3.4k.
They split the axes: hypit leads on customization and model freedom, Vibe-Skills on context depth and noise control.
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
An end-to-end, agent-driven video workflow DSL that clones a reference video into editable, re-runnable compositions and ships mass variants (e.g., 100 variants) rather than producing single one-off renders.
- Stars
- 10.5k
- Tracked growth
- not tracked long enough
- Maturity
- ●●●●●
- Last commit
- 3h ago
- Language
- TypeScript
- License
- NOASSERTION
- Cost to run
- Open-source; can run locally for free, external model 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.4k
- Tracked growth
- +45%
- Maturity
- ●●●●●
- Last commit
- 18d 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 | hypit | 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. | ●●●●● Project directory | ●●●●● Whole-repo analysis |
Noise control How it keeps output volume down — severity thresholds, deduplication, incremental runs over new commits only. | ●●●●● None mentioned | ●●●●● Severity gating |
Customization How far it bends to your team: custom rules, prompts, style guides, per-path config. | ●●●●● Pluggable components | ●●●●● Config file options |
Privacy Whether your code stays on your own infrastructure: fully local, self-hostable, or cloud API only. | ●●●●● Fully local option | ●●●●● Self-hostable |
Model freedom Whether you can point it at any provider, or it is wired to one. | ●●●●● Multiple providers | ●●●●● 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 hypit if…
Open-source local workflows — run fully editable video-generation pipelines on your machine and produce many variants from a single command without per-render vendor fees.
- Customization: Pluggable components (5/5 against 3/5)
- Model freedom: Multiple providers (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.
- Context depth: Whole-repo analysis (5/5 against 3/5)
- Noise control: Severity gating (5/5 against 1/5)
What people want from each one
hypit-ai/hypit
foryourhealth111-pixel/Vibe-Skills
Questions people ask
Is hypit better than Vibe-Skills?
They split the axes: hypit leads on customization and model freedom, Vibe-Skills on context depth and noise control. hypit is worth picking when open-source local workflows — run fully editable video-generation pipelines on your machine and produce many variants from a single command without per-render vendor fees.
Which of hypit and Vibe-Skills keeps my code private?
hypit: Fully local option (5/5). Vibe-Skills: Self-hostable (4/5).
What does each one cost to run?
hypit: Open-source; can run locally for free, external model API costs may apply.. Vibe-Skills: Free, self-hosted.
Full profiles: hypit-ai/hypit and foryourhealth111-pixel/Vibe-Skills. Everything else in Workflow & graph engines.