Link
# Linken
<p align="center"><img src="docs/linken.jpg" alt="Linken, an elf hero in a LinkedIn-blue tunic" width="320"></p>
Your LinkedIn, run by Claude. Nothing posts until you click.
| โ๏ธ Post | ๐ฅ Inbox | ๐งน Clean up |
| --- | --- | --- |
| Posts, comments and replies you approve | Drafts replies from your own data export | Keeps who matters, removes clear spam, paced |
```mermaid
flowchart LR
A[๐ค Your AI tool] --> B[๐ Draft]
B --> C{๐ค You approve?}
C -->|yes| D[โ
LinkedIn API]
C -->|no| E[๐ Nothing sent]
```
## ๐ Try it in 2 minutes
| Step | Do |
| --- | --- |
| 1 | `npm run sample` |
| 2 | Claude: `archive_load` `~/.linken-sample` |
| 3 | `connections_summary` |
## Install
| # | Do |
| --- | --- |
| 1๏ธโฃ | `/plugin install linken --marketplace Colorado-Startups/linken` |
| 2๏ธโฃ | Make a LinkedIn app and a token: [setup](docs/setup.md) |
| 3๏ธโฃ | Ask Claude to call `linken_status` |
## ๐ก๏ธ Safety
| Guard | How |
| --- | --- |
| ๐ค Approval dialog | Every post waits for your click |
| ๐ Halt file | Create `~/.linken/halt` and actions stop |
| โฑ๏ธ Pace caps | A daily cap and random gaps |
| ๐ Data stays on your Mac | Token in the Keychain, ledger in `~/.linken` |
| ๐ซ Removes nothing itself | You or your browser agent click Remove, one at a time |
## Links
| Page | Where |
| --- | --- |
| ๐ Quality | <https://colorado-startups.github.io/linken/> |
| โ๏ธ Process | <https://colorado-startups.github.io/linken/process.html> |
| ๐ง Setup | [docs/setup.md](docs/setup.md) |
| ๐ Connections guide | [docs/connections.md](docs/connections.md) |
| ๐ Legal | [Apache-2.0](LICENSE), [trademarks](TRADEMARKS.md) |
Open source from Colorado Startups. Check its work before anything posts. Not affiliated with LinkedIn or Anthropic.
TDQS
Scored across 13 tools
Each tool targets a distinct step in a clear workflow: check/list/next/mark/summary for connections, next/mark/reply_open for inbox, publish/comment for posting, and status for auth. The only real overlap is connections_check versus connections_check_list, which the descriptions separate by lane (single profile vs. up to 40 list rows), and connections_next versus connections_list/summary, which are distinguished by pacing/queue vs. paging vs. aggregates. Minor ambiguity remains around when to use check_list instead of check.
Mostly a consistent noun_verb pattern grouped by namespace: connections_*, inbox_*, post_publish, comment_create, archive_load, reply_open. Deviations are small: linken_status uses a misspelled domain prefix unlike any other tool, and connections_check_list is the only three-token name.
13 tools sit comfortably in the well-scoped range and each maps to a distinct stage of the connections, inbox, or publishing lifecycle. Nothing looks redundant or padded; the safety primitives (caps, halt file, dry-run) are exposed through existing tools rather than one tool each.
The surface covers the full loop: archive_load โ connections_list/check/check_list โ connections_mark โ connections_next, plus inbox_next/inbox_mark/reply_open and post_publish/comment_create, with status for diagnostics. Gaps are minor and mostly deliberate (no LinkedIn-side removal, no scheduling/edit/delete, no text search over connections), but the absence of search by name/company could force agents to page through results.