Habi

ha·bi /ˈha.bi/ Filipino, to weave

Download

Where will you weave?

your systemmacOSApple silicon & Intel.dmgyour systemWindows10 & 11, 64-bit.exe

Free and open source. Not signed, so the first launch asks once: here is how.

Habi weaves your team's AI agent skills together

How it works

One skill, all the way around.

From somebody else's library, into your repository, better, and back out to everyone. Six moves, on Habi's own screens.

  1. 01

    Explore

    Skills from everywhere, in one place.

    What the tools' own builders publish, what the community maintains, and your team's Git repositories or folders, side by side. Offline, marked when your team has not reviewed it, updated only when you say so.

    before Habifour repos, two wikis and a thread from last spring

    Habi's Libraries page, “Where your knowledge comes from”: two connected team libraries, libraries from the community, and libraries from the builders of the tools.
    Habi's Libraries page, “Where your knowledge comes from”: two connected team libraries, libraries from the community, and libraries from the builders of the tools.

  2. 02

    Check

    Open a repository. Ask what applies.

    Habi reads the stack, from Java and Kotlin to TypeScript, Go, Rust, Python and PHP, monorepos module by module, and sorts every skill: required, fits, available. Each answer cites its file and line. Nothing is built or run, and when the files can't say, Habi asks.

    before Habifive repos searched by hand, twice

    Habi on billing-service: skills sorted into installed, required by the team and fits this project, and for the open skill, the evidence from pom.xml.
    Habi on billing-service: skills sorted into installed, required by the team and fits this project, and for the open skill, the evidence from pom.xml.

  3. 03

    Install

    Every file, seen first.

    Claude Code, Cursor, Codex, Gemini CLI, GitHub Copilot, OpenCode and Junie, preselected from what the project already uses. Into the project, or onto your machine for every project. You read every line before it lands, and any change can be restored.

    before Habiskill-FINAL2, copied in by hand

    The install review: seven agent tools to choose from, and the three files that would change, line by line.
    The install review: seven agent tools to choose from, and the three files that would change, line by line.

  4. 04

    Improve

    Fix it where you learned it.

    The Skill Studio holds a skill as one document: its purpose, when Habi should suggest it, the instructions, scripts and references. Start from nothing, from part of an instruction file, or from skills you already have. No account, model or library needed.

    before Habi# TODO: write this properly

    The Skill Studio: a skill titled Review a pull request, with its purpose, when to use it and its instructions in one document.
    The Skill Studio: a skill titled Review a pull request, with its purpose, when to use it and its instructions in one document.

  5. 05

    Share

    Send it back as a pull request.

    Choose the files, see exactly what leaves your machine, and Habi prepares the branch and opens the pull or merge request on GitHub or GitLab for you. The reviewer's comments show up right there; revise on the same request.

    before Habi“just keep it locally 🤷”

    A contribution after review: the GitHub pull request, a reviewer's comment, and the diff of the skill that was sent.
    A contribution after review: the GitHub pull request, a reviewer's comment, and the diff of the skill that was sent.

  6. 06

    Update

    See what changed. Update when ready.

    Merged, the fix shows up as an update wherever it is installed, in every project and on your machine. Review it line by line, keep your own edits, and adopt it when the project is ready. One way to check, for your team's skills, the community's and the builders'.

    before Habi“wait, which copy is the latest?”

    Reviewing an update to Liquibase migration review in billing-service: the version it moves from and to, and the new line in SKILL.md, before anything is written.
    Reviewing an update to Liquibase migration review in billing-service: the version it moves from and to, and the new line in SKILL.md, before anything is written.

The principles

Habi will never phone home, guess, run things behind your back, touch a file you haven't seen, lock you in, or pretend strangers are vetted.

  1. 01 never phone home

    No account, telemetry or cloud service. The few requests that leave your machine are listed on a Privacy page in the app; the update check can be switched off.

  2. 02 never guess

    No model calls, no confidence percentages. Every answer comes with its evidence, and when the files can't say, Habi asks.

  3. 03 never run things behind your back

    Inspecting a project builds and executes nothing. A check runs only after you have read the exact command and pressed “Run this command”.

  4. 04 never touch a file you haven't seen

    Every change is a previewed plan, applied atomically and journaled. Whatever it replaces is kept, and restorable.

  5. 05 never lock you in

    Agent Skills folders, AGENTS.md and Git. Uninstall Habi and every installed skill and instruction keeps working; your libraries stay where they are.

  6. 06 never pretend strangers are vetted

    Community libraries are marked as not reviewed by your team; anything that downloads code or touches credentials is called out.

Stop copying skills.Start weaving.