NordVPN CLI Skill (Linux)

A ClawBot skill for controlling the NordVPN Linux CLI (nordvpn) to connect/disconnect, select locations, verify status, and adjust settings from automations and workflows.

Assumptions / Compatibility

• * Works with the official nordvpn CLI (example shown: 4.3.1 [snap]).
• Requires the NordVPN daemon running (usually nordvpnd) and sufficient permissions.
• Some commands may require elevated privileges depending on distro + install method (snap vs deb).

Installation

Option A: Snap (common on Ubuntu)

CODEBLOCK0

Option B: Distro package / repo (varies)

If you installed via Nord’s repo or a package manager, just verify:

CODEBLOCK1

Verify daemon is running

CODEBLOCK2

Authentication / Login

NordVPN CLI typically requires logging in once per machine/user session.

CODEBLOCK3

If the environment is headless, the CLI will guide you through the login flow (often via a browser link / code). After login, confirm:

CODEBLOCK4

ClawBot guidance: treat login as a manual prerequisite unless you explicitly automate the browser-based login flow.

Quick Reference

Status

CODEBLOCK5

Connect (best available)

CODEBLOCK6

Connect to a country / city / group

CODEBLOCK7

Disconnect

CODEBLOCK8

List locations

CODEBLOCK9

Settings (read + change)

CODEBLOCK10

Allowlist (bypass VPN for certain traffic)

CODEBLOCK11

Skill Design

What this skill should do well

1. 1. Idempotent connection actions

* If already connected to the requested target, do nothing (or return “already connected”).
* If connected elsewhere, optionally disconnect then connect to target.

1. 2. Reliable verification

* After connect/disconnect, always run nordvpn status and parse the result.

1. 3. Safe fallbacks

* If a requested city/country/group is invalid, provide closest alternatives by listing:

* nordvpn countries
* nordvpn cities <country>
* nordvpn groups

1. 4. Human-in-the-loop login

* If nordvpn reports not logged in, return a structured response instructing to run nordvpn login.

Recommended “actions” (API surface)

Implement these as the skill’s callable intents/tools:

• * status() → returns parsed connection status
• INLINECODE10 → connects to best available
• INLINECODE11
• INLINECODE12 (optionally with country for disambiguation)
• INLINECODE14
• INLINECODE15
• INLINECODE16
• INLINECODE17
• INLINECODE18
• INLINECODE19
• INLINECODE20
• INLINECODE21
• INLINECODE22

Suggested Implementation Pattern (CLI orchestration)

1) Always start with status

CODEBLOCK12

Parse fields commonly returned by the CLI, such as:

• * Connection state (Connected/Disconnected)
• Current server / country / city
• IP, protocol, technology

2) Connect flow

Goal: connect to a target (country/city/group) with verification.

Pseudo-logic:

• * Run INLINECODE23
• If disconnected → connect directly
• If connected to different target → nordvpn disconnect then connect
• Run nordvpn status again and confirm connected

Commands:

CODEBLOCK13

3) Disconnect flow

CODEBLOCK14

4) Resolve targets safely

If user asks for a city:

• * Prefer nordvpn cities <country> when country is known
• Otherwise attempt connect; if it fails, list countries and search-like suggestions.

CODEBLOCK15

Common Errors & Handling

Not logged in

Symptoms:

• * CLI complains about authentication/account/login.

Handling:

• * Return: “Login required. Run nordvpn login and repeat.”
• Optionally: run nordvpn account to confirm.

Daemon not running / permission denied

Symptoms:

• * Can’t connect, service errors, permission errors.

Handling:

• * Check systemctl status nordvpnd (systemd installs)
• Confirm snap service health (snap installs vary)
• Ensure user belongs to the right group (some installs use a nordvpn group):

CODEBLOCK16

Invalid location/group

Symptoms:

• * “Unknown country/city/group” or connect fails immediately.

Handling:

• * Provide available options:

CODEBLOCK17

Practical Automation Recipes

Ensure VPN is connected (any server)

CODEBLOCK18

Reconnect to a specific country

CODEBLOCK19

Toggle killswitch (example)

CODEBLOCK20

Notes

• * Command options and setting keys can differ by NordVPN CLI version. Always rely on:

CODEBLOCK21

• * If you need stable machine-readable output, the NordVPN CLI does not consistently provide JSON; plan to parse human-readable status text defensively (line-based key/value extraction, tolerate missing fields).