An agent skill for driving Hibiki's brand and content agent from a terminal — drafting posts, asking what to post next, researching a subject, reading a page as the brand's agent would — without opening the web portal.
npx skills add gethibiki/skillThat installs it into whichever agents are on the machine: Claude Code, pi,
Codex, Cursor and the rest. Add -g to install it once for every project rather
than into the current one.
The skill drives @hibiki/cli,
which talks to Hibiki's public API with a key from Settings → API Keys in the
portal:
curl -fsSL https://raw.githubusercontent.com/gethibiki/cli/main/install.sh | sh
hibiki login
hibiki brand use <brand-id> # writes .hibiki.json — commit itA single-file binary, checksum-verified, no Node or npm — see
gethibiki/cli. The skill works without it
too: every operation has a documented curl equivalent, because the CLI is a
thin client over the same public API.
Grant the key brands:read, tasks:read, tasks:write and analysis:run. The
portal's default is read-only and will not queue work. A self-hosted install
points at itself with HIBIKI_API_BASE.
The two lanes Hibiki actually has, kept apart rather than blended:
| Lane | Command | Shape |
|---|---|---|
| Queued | hibiki draft … |
Writes a task row and polls. Minutes. Survives a killed shell. |
| Synchronous | hibiki ask <kind> |
JSON in, JSON out, on the request. Seconds. |
…and the rule the whole design rests on, which is the real reason this is a skill rather than a README: the agent judges, the CLI transports. A coding agent that reads this drives Hibiki instead of writing the post itself — so every saved row has one author, and you can always say which.
The skill is written for Hibiki's public API, so a change here usually follows a change there. Open an issue or a PR.
MIT.