An open-source Claude Code plugin that turns a plain markdown vault into an AI-operated company hub — initiatives (each owning its to-dos and docs), knowledge, a decision log, a library of external signals, a CRM, a content pipeline, and more, all maintained by agent commands. The markdown files are the source of truth; Obsidian and the agent are two interfaces over them. Your content stays private; only the mechanism (schema, agent rules, commands) is open.
hq is the plugin (the OS) you install; your vault is the company hub it
creates and operates — a directory of markdown you might call "Acme HQ". One
plugin, many vaults: install hq once, scaffold a vault per company.
hq is distributed through the fryga plugin marketplace. From inside Claude
Code:
/plugin marketplace add fryga-io/claude-marketplace
/plugin install hq@fryga
then restart Claude Code.
(Hacking on the plugin itself? The repo ships a dev marketplace — add your local
checkout with /plugin marketplace add ./ and install hq@hq-dev.)
From the directory where you want your vault to live:
- Run
/hq-init— interactive onboarding. It interviews you for identity (companies, team roster, a one-line description), copies the content-free skeleton into the directory, and writes a personalizedhq.config.yml,CLAUDE.md, andREADME.md. The result is a clean, empty, personalized vault. - Run
/validate-vault— confirms structure, frontmatter enums, wikilinks, indexes, and dashboard guards are all green.
Then operate the vault day to day with the agent and these commands:
/add-to-library— capture an external signal (URL, YouTube link, or pasted text) into the library, keeping the index and synthesis wiki in sync./dream— a maintenance cycle that heals hygiene, flags drift and contradictions, promotes durable signal, and ranks what's hot./weekly— generate a structured weekly rollup for your team./validate-vault— re-run any time before a commit.
The plugin ships:
commands/— the agent commands above.skills/— the agent skills.using-hq/is the always-on governance (session startup, schema pointers, editing discipline, conventions) injected every vault session — the single source of truth for how an agent governs a vault. Alongside it, one capability skill per module — the know-how for operating that module, loaded on demand (working-initiatives,working-knowledge,working-log,working-people,working-companies,working-library,working-crm,working-distillery,working-competitive,working-sales,working-operations).using-hqholds the cross-module always-on discipline and a resolver listing them all; the schema lives indocs/vault-design.md.hooks/— a SessionStart hook that injectsusing-hqinto every session that is inside a vault (it walks up forhq.config.yml; outside a vault it stays silent). This is what makes the rules reachable in a normal session.skeleton/— a content-free structural skeleton (empty index/wiki stubs and dashboards) that/hq-initcopies to scaffold a new vault.docs/vault-design.md— the schema spec: structure, frontmatter schemas, and conventions. The single source of design for a vault.
A vault is made generic by hq.config.yml at its root — the seam that holds the
company list, team roster, and canon files. Nothing else hardcodes identity;
tools find the config (and thereby the vault root) by walking up from the working
directory, the way git finds .git. That same walk-up is how the SessionStart
hook decides a session is inside a vault and loads the rules — so your vault's
CLAUDE.md stays minimal (identity + your own company policy), and the operating
rules live in the plugin, updating centrally instead of going stale in every
vault's copy.
The schema is modular: a core of initiatives, knowledge, and log, plus optional modules — people and companies (entity registries), library (external-signal capture), crm, distillery (content pipeline), competitive, sales, and operations. Every module is content-free in the skeleton; a module's folder earns its place in a vault once it is used.
MIT — see LICENSE.