Many Artifacts.One Kit.
HubBound turns your team's skills, rules, MCP servers, subagents and hooks into versioned Artifacts, then bundles them into Kits that install on every machine with one command.
What is an Artifact in HubBound?
An Artifact is HubBound's versioned unit of AI tooling: one skill, rule, MCP server, subagent or hook that your organization writes once, owns, and installs on every developer's machine. There are exactly five Artifact types, and each one is configured for the job it does.
Skills
A packaged procedure an agent runs by name for repeatable work, written as files the agent reads.
For example: A release checklist that every agent follows the same way.
Configured with
- Entrypoint file
Rules
A convention the agent must follow, applied always, when the agent judges it relevant, or only to files that match a pattern.
For example: TypeScript conventions applied to every file under src.
Configured with
- When to apply
- File patterns
MCP servers
A Model Context Protocol server that gives the agent tools and data, run as a local process or reached over HTTP.
For example: Your issue tracker, available to every agent on the team.
Configured with
- Transport
- Command or URL
- Secrets
- Permissions
Subagents
A specialized agent that the main agent hands a focused task to, with its own instructions.
For example: A code reviewer that checks every change against the same bar.
Configured with
- Entrypoint file
Hooks
An automation that runs at a set point in the agent's lifecycle, such as a session start, a file write or a tool call.
For example: Format every file the agent writes, before anyone reviews it.
Configured with
- Trigger
- Category
- Entrypoint file
What is a Kit in HubBound?
A Kit is HubBound's bundle of Artifacts: a named, versioned set of skills, rules, MCP servers, subagents and hooks that is installed and distributed as one unit. Each Artifact inside a Kit either follows its current version or stays pinned to one exact version, so a team gets new work where it wants it and stability where it needs it.
Illustrative sample. Kit and Artifact names and versions are for illustration only.
Built from your organization's Artifacts
Add artifact picks any Artifact from your organization, filtered by type. Unlinking one takes it out of the Kit without deleting it, and deleting a Kit, which is permanent, leaves its Artifacts in place.
A new version for every change
Adding, removing or pinning an Artifact saves a new Kit version, a snapshot of the exact version of every Artifact inside it. A Kit version can also carry a changelog.
Fork to adapt
Fork creates a private copy of a Kit that you can modify, from its current version or from a specific one. The original stays exactly as it was.
How do you create an Artifact in HubBound?
In HubBound, you create an Artifact from one short form: a name, one of the five types, a visibility, and the few settings that type needs. Every Artifact starts empty, and its files are added afterwards in HubBound's built-in editor.
A name the CLI can use
Names use lowercase letters, digits and hyphens, like release-checklist, because the name becomes part of the tag that installs the Artifact.
Only the settings its type needs
Pick a type and the form asks for what that type needs: a trigger and a category for a hook, when a rule applies, a transport and connection for an MCP server, or the entrypoint file for a skill or subagent.
Files come next
Files are created or uploaded in the editor, which shows each one raw or as a rendered preview and marks the entrypoint file the Artifact starts from.
Name
release-checklistVisibility
OrganizationVisibility can only be raised: private → organization → public.
Entrypoint
SKILL.mdName
typescript-conventionsVisibility
OrganizationVisibility can only be raised: private → organization → public.
Apply rule
Specific filesFile patterns
src/**/*.tsName
issue-trackerVisibility
OrganizationVisibility can only be raised: private → organization → public.
Transport
stdiohttpCommand
npxArguments
-yName
code-reviewerVisibility
OrganizationVisibility can only be raised: private → organization → public.
Entrypoint
code-reviewer.mdName
format-on-writeVisibility
OrganizationVisibility can only be raised: private → organization → public.
Category
CoreTrigger
File WriteEntrypoint
hook.shIllustrative sample: switch the type to see which settings each one asks for. The form mirrors HubBound's Create artifact window.
How does HubBound version an Artifact?
HubBound versions every Artifact on its own: each change to its files or settings is saved as a new version, which becomes the Artifact's current version, and a History log records who created it, updated it, forked it or changed its visibility. Nobody has to remember to cut a release.
Illustrative sample. The layout mirrors HubBound's Artifacts workbench: the Artifact list, its files, and the editor with its version selector.
Past versions, kept as they were
Depending on your plan, you can open any past version read-only and see exactly what it contained. How many versions HubBound keeps per Artifact also depends on the plan.
Compare plansA History log on every plan
Every event on an Artifact is listed with who did it and when: created, updated, forked, visibility changed, access granted.
Visibility only goes up
Private, Organization or Public. Visibility can only be raised, from Private to Organization to Public, and never lowered.
Access per Artifact
Read lets someone see an Artifact, Write lets them edit it, and Admin also lets them delete it and decide who has access. Org Admins can do all of this on every Artifact.
How does a Kit get installed on every machine?
HubBound installs a Kit with one CLI command, hubbound install kit, followed by the Kit's tag and, optionally, an exact version. That one command applies every Artifact in the Kit to Claude Code, Cursor, Codex, Antigravity and GitHub Copilot, so the same standard lands in whichever AI tools each developer uses.
One tag, one optional version
The tag is the Kit's owner and name, exactly as the Kit and its Marketplace entry show it. Add @ and a version to install that exact version.
Every supported tool, or the ones you pick
By default an install covers all five tools. The --tool flag narrows it to the ones you name. There is no per-type compatibility list to check: every Artifact type installs into all five.
For one project or for the whole machine
--scope local installs into a project that has a hubbound.json file, and --scope global installs for your user. Running hubbound install on its own installs everything the project's hubbound.json lists.
Install a Kit, pinned to an exact version
hubbound install kit jane-a1b2c3/ai-tools-bundle@1.2.0
Install one Artifact for two tools only
hubbound install artifact jane-a1b2c3/my-hook --tool claudecode,cursor
Install everything this project's hubbound.json lists
hubbound install
Installs into
- Claude Code
- Cursor
- Codex
- Antigravity
- GitHub Copilot
Commands and flags as documented in the HubBound CLI reference; the tags are the reference's own examples.
Or distribute it, and nobody has to run anything
An admin can distribute a Kit instead of sharing a command. Org Admins distribute to the whole organization and Team Admins to their teams. A mandatory distribution is installed on every member's machine on the next background sync; an optional one waits for each member to choose.
What is the HubBound Marketplace?
The HubBound Marketplace is where teams discover ready-made Kits and Artifacts: public ones published by the community and, on plans that include it, a private marketplace for your own organization. It is read-only: each entry shows its version and install command, and you fork it into a private copy or distribute it to your teams instead of editing it in place.
- Public, or just your organization
- Filter between the public marketplace and your organization's private one, and between Kits and Artifacts. The private marketplace comes with some plans.See which plans include it
- Fork it to make it yours
- Fork creates a private copy in your organization that you can modify and version like anything your team built.
- Distribute it, or install it
- Distribute sends an entry to a team or to the whole organization, and the install command installs it from the CLI.
Illustrative sample. Entry names, authors and versions are for illustration only, and download counts are left blank. The layout mirrors HubBound's Marketplace.
See how it all connects.
Each piece of HubBound builds on the others. Pick where you want to go next.
Build it once. Install it everywhere.
See how HubBound turns your team's AI tooling into versioned Artifacts and Kits that reach every machine the same way.
