🧪 killBottleneck is in public beta — cloud and self-host.🧪 killBottleneck is in beta.Beta on GitHub →
Skip to content

Your own skin

How killBottleneck looks is your choice, not the admin's. This tutorial shows the built-in skins first, then the standalone skin editor for building your own.

1. Pick a skin

Open the menu under your avatar → Appearance. Eleven built-in skins, from the default Indigo to Terminal or Midnight; each works in both light and dark mode, and the choice is saved to your account, so it follows you to every device — including the phone view.

The Appearance dialog. Statuses keep their colors in every skin — overdue is red everywhere.

2. Build your own in the skin editor

The skin editor is a separate small app (MIT-licensed, part of the skin gallery repository). It runs entirely in your browser — nothing is uploaded anywhere. Try it right now at https://tengolabs.github.io/killbottleneck-skins/ — no installation needed.

Start from any built-in template, edit 35 colors, 4 fonts, the corner radius and the background doodle — and watch the light and dark preview side by side.

The comfortable workflow:

  1. Start from a template — pick the built-in skin closest to what you want. (Or export your current skin from the app's Appearance dialog and open that.)
  2. Adjust the colors by group — base, cards, brand colors, the map canvas. The Copy light → dark button is a good starting point for the dark variant.
  3. Download the .kb-skin.json file.

3. Import it into killBottleneck

Back in the app: avatar menu → AppearanceImport skin — from the file, or by pasting the JSON. The skin is validated on import and saved to your account.

A skin is deliberately just data — colors, fonts, a radius. No CSS, no URLs, nothing that can run; the same whitelist is enforced by the editor, the app and the server. A skin someone sends you can look wild, but it can't do anything.

4. Share it (optional)

Skins in the gallery are CC0 — take, tweak, use. If you make one worth showing, open a pull request; CI validates the file.

A company-wide look

Administrators can set the instance-wide default skin in the organization settings. Every user's own choice still wins over the default.

Next

  • Skins — the full reference, including what a skin can and cannot change

fair-code — self-hosting and internal use are free, reselling as a hosted service is not.