Post-puls: scores for your LinkedIn post while you write it

Post-puls opens a panel beside LinkedIn's "Start a post" dialog and tells you how the post stands while you write it. The panel has two parts:

• Live checks in the browser, on every keystroke. What shows before "…more" (about 210 characters), length against an 800–1600 character band, first-line length, average sentence length, a link in the body (it belongs in the first comment), number of hashtags (at most 3), and whether the post ends with a question.
• Jev's verdicts when you pause. Jev is TypeSafe's model for typed judgements. It answers six fixed questions: how strong the opening is, whether there is one clear point, whether the post is concrete, how much jargon and how many anglicisms it has, whether the tone is defensive, and whether the ending invites replies. Jev never suggests wording — it only judges. Answers with low confidence, or that belong to an older version of the text, are dimmed.

Install

1. Download Post-puls (.zip) and unzip it into a folder you keep. The extension runs from that folder, so don't delete it afterwards.
2. Open edge://extensions (or chrome://extensions), turn on Developer mode, and choose Load unpacked with the unzipped folder.
3. Pin the Post-puls icon in the toolbar (under the puzzle icon) so you can reach its settings.

Add your Jev key

The live checks work without a key. Jev's verdicts need your own TypeSafe key.

1. Create or copy an API key at TypeSafe. A separate key for the browser lets you revoke it on its own.
2. Click the Post-puls icon, paste the key, and press Gem og test. If it says "Virker: jev-…, … ms", the key works.

The Model field can stay empty; jev-latest is used then.

Use

Reload LinkedIn and click Start a post. The panel appears to the right of the dialog. Close it with × and it stays away until you open a new post.

The chip at the top of the panel shows Jev's state: Tilføj Jev-nøgle (add key) or Nøgle afvist (key rejected) opens the settings; for lang means over 3000 characters, LinkedIn's own limit.

Where your key and text go

• The key is stored in chrome.storage.local: this browser profile on this machine only, not synced. It is stored unencrypted in the profile, like any other extension setting.
• Only the extension's background worker reads the key. The script running inside linkedin.com never sees it.
• The post text is sent only to api.typesafe.ai, when Jev is asked. There is no Agentics server in between.
• Every pause while you write is one call on your key — about 1,200 input tokens.

Limits

• Posts are judged as Danish, and the jargon question counts anglicisms, so an English post gets a skewed jargon score.
• The extension follows LinkedIn's current compose dialog. If LinkedIn changes it, the panel may stop appearing until a new version is out.
• It is not in the Chrome Web Store or Edge Add-ons yet, so it does not update itself: download the new zip, replace the folder, and press reload on the extension.