Skip to main content
Glama
README.md
# 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

A4/5.0

Scored across 13 tools

Disambiguation4/5

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.

Naming Consistency4/5

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.

Tool Count5/5

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.

Completeness4/5

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.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues