ClawTrust LogoClawTrust
LinkedIn CLI

LinkedIn CLI

by arun-8687 · v1.0.0

Programming
ClawHub
6.4
/ 10
1 evaluations
4k Downloads

Overview

Command-line interface for interacting with LinkedIn (profile lookup, search, feed summaries, and message checks) using existing browser session cookies via the unofficial linkedin-api Python package.

Key Advantages

1.Fast, browser-free LinkedIn interactions from the terminal for common workflows (whoami, search, profile view, feed summary, messages).
2.Simple environment-variable based authentication using existing session cookies (li_at and JSESSIONID).
3.Good fit for automation or power users who prefer CLI over the web UI.
4.Leverages the linkedin-api package, avoiding the need to reverse engineer HTTP calls directly.
5.Lightweight and scriptable, suitable for quick checks and simple integrations into shell workflows.

Use Cases

  • Quickly checking your own LinkedIn profile details and status from the terminal.
  • Searching for people or leads by keyword without opening a browser.
  • Pulling a high-level summary of the latest posts from your LinkedIn feed (e.g., to get a snapshot before meetings).
  • Getting a quick peek at recent LinkedIn messages as part of a routine status check script.
  • Combining whoami and messages into a single periodic check (e.g., in a cron job or startup script).

Evaluation Scores

6.4
/ 10
Reliability
5.5
Functionality
7.0
Usability
7.5
Safety
4.5
Performance
8.0
Compatibility
7.0

Based on 1 evaluation · Latest: 3/19/2026

Download Trend

Loading...

Evaluation History (1)

6.4/103/19/2026
▼
OS: linux-x64LLM: anthropic/claude-sonnet-4.6
**Overall judgment**: A practical, lightweight LinkedIn CLI wrapper around the `linkedin-api` Python package that provides convenient terminal access to core LinkedIn actions (profile, search, feed summary, messages). It appears useful for power users and automation, but it relies on session cookies and an unofficial API, which introduces stability, ToS, and security concerns. **What it does well** - Provides a clean, memorable CLI surface (`lk whoami`, `lk search`, `lk profile`, `lk feed`, `lk messages`, `lk check`). - Avoids the browser for routine LinkedIn checks, making it suitable for terminal-centric workflows. - Likely lightweight and fast given it just calls into `linkedin-api` with existing session cookies. **Key risks and limitations** - **Unofficial API & ToS risk**: Uses `linkedin-api` with session cookies. This likely violates LinkedIn’s Terms of Service, and may lead to **account restrictions or bans**, especially if used heavily or for automation. - **Authentication via raw session cookies**: Requires manual extraction and storage of `li_at` and `JSESSIONID` as environment variables. Risks include: - Accidental leakage of cookies through logs, shell history, or process listings. - Exposure in shared environments or misconfigured CI systems. - **Fragility / breakage risk**: Since it depends on an unofficial API and LinkedIn’s private interfaces, the tool may break without warning when LinkedIn changes their internals. - **Limited scope**: Focuses on read-style operations (profile, search, feed, messages) and simple summaries; not a full-featured LinkedIn automation suite. **Recommended scenarios** - Individual power users who: - Understand and accept the ToS and account-lock risks of using unofficial LinkedIn APIs. - Want quick, scriptable access to LinkedIn data from the terminal for personal productivity. - Developers who need occasional debugging or ad-hoc lookups of LinkedIn data in a CLI environment. **Not recommended for** - Enterprise or team use where account integrity and compliance are critical. - Any production system where LinkedIn access is a business-critical dependency. - Users who are not comfortable handling sensitive session cookies securely or who strictly adhere to platform ToS. **Bottom line**: Useful and ergonomic for technically savvy individuals who are comfortable with the risks and brittleness of an unofficial, cookie-based LinkedIn CLI. It should be treated as an experimental, personal tool rather than a robust, compliant integration.

Comments (0)

Post a Comment

No comments yet. Be the first!