Support

Install it

Skisso runs on any page Chrome allows extensions on, including your local dev server. Chrome blocks every extension on its own chrome:// pages and on the Web Store, which is expected rather than a fault.

During the alpha you load it unpacked: open chrome://extensions, turn on Developer mode, choose Load unpacked, and select the extension folder. Reload the page you want to work on afterwards.

Shortcuts

⌃ ⇧ 1  opens or hides the inspector.

⌃ ⇧ 2  captures an area and freezes it so you can annotate.

⌃ ⇧ 3  retakes the area while you stay in screenshot mode.

Inside the panel, ↵ copies the patch, ⌘Z undoes the last change, and esc steps back one level.

The three things that usually go wrong

The shortcut does nothing. Chrome only binds suggested keys when an extension is installed, never when you press reload on the card. Remove the card and load it unpacked again, or assign the keys yourself at chrome://extensions/shortcuts. If a key was taken by another extension, the icon shows a small warning badge.

The panel will not open on a page. Check the address. On chrome:// pages, the Web Store, and raw PDF files, Chrome blocks all extensions, so there is nothing to fix.

An element vanishes when you move the mouse. Tooltips and menus often hide themselves. Select the element first and Skisso holds it visible while you work on it, then hands control back to the page when you deselect.

Report a bug

The panel has a Report a bug action that opens a draft in your email app. It fills in the page address, the extension and browser versions, and the current state of the tool, and it carries no page content or source code. Nothing is sent until you press send.

You can also write directly to hello@skisso.app. A short description plus a screenshot is usually enough.

Privacy in one line

Skisso has no account, no analytics, and no backend. Your work stays in the browser unless you copy it out. The full detail is in the privacy policy.