BDOSKI
all good
BDOSKI
Access token required. Nothing loads without it.
BDOSKI
bdoski needs context. about you.
1 - Who you are
⚠ EXACTLY as on your LinkedIn
2 - Goals & targets
3 - Voice
BDOSKI ships with battle-tested BD writing rules (short, trigger-first, honest, no corporate fluff). Pick a flavour and add personal adjustments - they refine the rules, not replace them.
Warm & informalFriendly, human, a joke where it fits.
Concise & businesslikeShort sentences. Zero fluff. Straight to the point.
ChallengerConfident observations, insight-led, gentle pushback.
4 - LinkedIn archive
Export from LinkedIn: Settings → Data privacy → Get a copy of your data. Two files matter: Connections.csv (your network → contacts DB) and messages.csv (your dialogues → BDOSKI learns to write like you). Both optional - skip if not ready.
5 - Your writer prompt
bdoski wrote a first version of your writer voice, tailored to your field. Read it, tweak anything, then enter. You can always refine it later in Finetuning.
📡 SIGNALS
RSS feeds · daily engine
🔍 GOOGLE RSS
15 freshest news per query
🎯 LCS
LinkedIn Company Scan: posts · hires · joiners
𝕏
sleeping until activation
verses ▾
🎮 STEAM
game news on demand: pick a game, pull its latest into the feed
Threads
Loading…
Select a conversation on the left
?
Loading…
·
✎
Previously contacted - follow-up mode active
📎 files
Relation?
Pick a person on the left, or start typing a name above.
Profile Intelligence?
-
No contact selected
Context?
Chips are added here from Signals and Jobs
Log a message manually?
-
[✓] ↓ Incoming
[✓] ↑ Outgoing
VIA:
💼 SCAN COMPANY
fresh openings of one company · 30-day window
💼 SCAN CATEGORY
who is hiring in a discipline · 14-day window · one signal per company
data: ASGC job board by Amir Satvat
No job signals yet.
Scan a company or a category above.
TASKS
→
STATS - MEASURED, NOT VIBES
Loading...
VOICE FINETUNING?
LINKEDIN ARCHIVE - REFRESH ▾?
Re-import fresh exports anytime, no wizard needed - dedup makes it safe. Connections.csv also marks your 1st-degree network for direct sends (fills only unknown degrees, never overwrites what the extension observed).
This is the person-specific part of the writer voice - who you are, what you offer, your triggers and how you read a situation. A universal core (formatting discipline, anti-fabrication, response format) and a runtime tail (today's date, met-before note, winning messages) are applied automatically at generation and are not shown here. Save applies to every generation from that moment on.
Identity
PRE-GENERATE FROM QUESTIONS - same questions as onboarding, fills the prompt below
Writer prompt
Previous versions
BDOSKI · private beta · Changelog

BDOSKI - how it works & fair use

The extension

BDOSKI talks to LinkedIn through its Chrome extension, running inside your own logged-in session - it reads your inbox and sends messages exactly as you would, from your account. Nothing LinkedIn-related works without it.

Install from the Chrome Web Store (unlisted link), then press ⚡ Link next to the search field and approve the pairing.

Keep Auto Sync ON in the extension popup - that is the loop that keeps your inbox fresh here. The Sync button in the popup forces the same pull immediately; after pressing it, just switch back to this tab - BDOSKI refreshes itself on return.

The one-screen flow

Left: empty search is your live inbox sorted by activity; start typing to search every contact you have. Middle: the person - quick chat on top, AI generation below it, full history collapsed at the bottom. Right: everything BDOSKI knows about them.

Syncing: what talks to LinkedIn and how often

Two very different loops. Your browser polls your own capsule every 45 seconds - LinkedIn never sees these requests at all. The extension talks to LinkedIn itself gently: the thread list every 5 minutes, one extra pull after you send something, and a single conversation fetch when you click a thread - exactly the requests a person with the tab open generates, from your own logged-in session and IP. LinkedIn's own site polls itself more aggressively than that, which is why this profile of activity is indistinguishable from normal use.

Matching, degree and why the archive helps

Threads are matched to contacts by profile link first, then by name. The archive is not used for matching - it fills the history, which is what makes drafts sound informed instead of cold.

Connection degree (needed for direct send) is read from the profile page by the extension. If a person shows "degree unknown": press resolve now under the name - the profile opens in a tab - press Add in the BDOSKI popup there and hit Sync. Switch back to BDOSKI: the degree lands on the person by itself. The send address arrives with the profile scrape (Update in Profile Intelligence) or, for people adopted from the inbox, comes free with the thread link.

Your archive = your voice

The LinkedIn export you upload is what teaches BDOSKI to write like you: your phrasing, your openers, your closers, mined from real conversations that worked. Without it the writer falls back to generic BD rules; with it, drafts sound like yours. The bigger and fresher the archive, the better the result - refreshing it later is safe, duplicates are skipped automatically.

Privacy and GDPR

Your data lives in your own isolated capsule: a separate container and a separate database per client. It is used for exactly one purpose - generating your messages. We do not sell it, share it, or train anything global on it, and it is deleted on request.

Fair use and responsibility

You send messages as yourself, from your own account, to people you choose. You are solely responsible for what you send and to whom. Mass unsolicited messaging may violate LinkedIn's Terms of Service and can get an account restricted. BDOSKI is tooling: it sends nothing on its own and accepts no liability for the consequences of your outreach.