kombai-io/agent-plugins

work-with-kombai

Design UI with Kombai's taste agent.

View source

How to use

  1. Copy the installation command and review the source package before installing it in your own agent environment.
  2. Check the source document for required tools, credentials and supported hosts.
  3. Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/kombai-io/agent-plugins --skill work-with-kombai

Before you start

  • Installation does not include a model subscription, API allowance or permission to access your files.
  • Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document

Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.

When running in Codex's sandbox, first read codex-access.md beside this file and do what it says before the first command below: it says how to get network access without trying the restricted command first. Elsewhere, skip it.

Run Kombai's CLI (kombai below) from node "$HOME/.kombai/cli/install/latest/launch.mjs" if that file exists; if not, fall back to npx -y @kombai/cli@0.2.0.

Run kombai skill and follow what it prints; it is this skill's full text.

If that command fails before it prints anything:

  • `npx` or `node` not found. Kombai needs Node.js 20 or later. Tell the user, give them the steps for their OS, and wait; do not install Node yourself.
  • macOS: brew install node if Homebrew is installed, otherwise the LTS installer from https://nodejs.org.
  • Windows: winget install OpenJS.NodeJS.LTS, otherwise the LTS .msi from https://nodejs.org.
  • Linux: nvm (https://github.com/nvm-sh/nvm), then nvm install --lts. The distro's package is often older than 20.

When they say it is installed, run the command again. If node is still not found, ask them to restart this agent or its editor, so it picks up the new PATH; do not ask them to install again.

  • `CLI_NODE_TOO_OLD`. The same steps upgrade Node; with nvm, nvm install --lts then nvm alias default lts/*. If the error comes back after an upgrade, an older node is first on PATH: show the user which -a node (where node on Windows).
  • Windows PowerShell says running scripts is disabled. Run npx.cmd in place of npx.
  • The network is blocked (a sandboxed shell). Ask for network access the way your client does; Node is not missing.