How do I install the VPN skill?

Run npx skillmds@latest add dvcrn/vpn-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the VPN skill do?

Configure and troubleshoot VPN connections for privacy and remote access. It is listed under Coding & Dev Tools on SkillMD.

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with VPN?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

dvcrn (@dvcrn) published this skill. Their other Agent Skills are listed on their SkillMD profile.

VPN by dvcrn — Agent Skill

Name: VPN
Rating: 4.5 (4 reviews)
Author: dvcrn

File contents

Privacy Misconceptions

VPN shifts trust from ISP to VPN provider — provider sees all traffic, not eliminated
"No logs" claims are marketing — unverifiable without independent audits
VPN doesn't provide anonymity — browser fingerprinting, account logins, payment methods still identify
Free VPNs monetize traffic data — if not paying, you're the product
Self-hosted VPN exits from your IP — no privacy benefit, services see your home address

DNS Leaks

DNS queries can bypass tunnel — reveals visited sites despite encrypted traffic
Test after every setup — leak test sites show if DNS goes through ISP instead of tunnel
System DNS settings may override VPN — force DNS through tunnel in client settings

Kill Switch

Brief VPN disconnects expose real IP — happens without user noticing
Kill switch blocks all traffic when tunnel drops — essential for privacy use cases
Test by forcing disconnect — traffic should stop completely, not fall back to direct

Split Tunneling Risks

Misconfiguration sends sensitive traffic direct — defeats VPN purpose
Full tunnel safer default — split only when deliberately excluding specific apps
Local network access often requires split — printing, casting break with full tunnel

Protocol Traps

PPTP encryption is broken — trivially cracked, never use regardless of convenience
UDP blocked on some networks — TCP fallback needed for restrictive firewalls
WireGuard uses fixed ports — easier to block than OpenVPN on 443

Mobile Issues

WiFi calling fails through most VPNs — carrier limitation, not fixable
Banking apps detect and block VPN — may need exclusion in split tunnel
Battery drain varies significantly — WireGuard most efficient by large margin

Connection Failures

"Connected" but no internet — usually DNS misconfigured, not routing issue
Works on phone not laptop — local firewall or antivirus interfering
Constant reconnects — try TCP instead of UDP, increase keepalive interval

Self-Hosted Traps

Exit IP is your home IP — services see where you live, no geo-bypass benefit
Requires static IP or dynamic DNS — clients can't find changing endpoints
Unmaintained server becomes liability — security updates are your responsibility

---name: vpn-2description: Configure and troubleshoot VPN connections for privacy and remote access.--- ## Privacy Misconceptions - VPN shifts trust from ISP to VPN provider — provider sees all traffic, not eliminated - "No logs" claims are marketing — unverifiable without independent audits - VPN doesn't provide anonymity — browser fingerprinting, account logins, payment methods still identify - Free VPNs monetize traffic data — if not paying, you're the product - Self-hosted VPN exits from your IP — no privacy benefit, services see your home address ## DNS Leaks - DNS queries can bypass tunnel — reveals visited sites despite encrypted traffic - Test after every setup — leak test sites show if DNS goes through ISP instead of tunnel - System DNS settings may override VPN — force DNS through tunnel in client settings ## Kill Switch - Brief VPN disconnects expose real IP — happens without user noticing - Kill switch blocks all traffic when tunnel drops — essential for privacy use cases - Test by forcing disconnect — traffic should stop completely, not fall back to direct ## Split Tunneling Risks - Misconfiguration sends sensitive traffic direct — defeats VPN purpose - Full tunnel safer default — split only when deliberately excluding specific apps - Local network access often requires split — printing, casting break with full tunnel ## Protocol Traps - PPTP encryption is broken — trivially cracked, never use regardless of convenience - UDP blocked on some networks — TCP fallback needed for restrictive firewalls - WireGuard uses fixed ports — easier to block than OpenVPN on 443 ## Mobile Issues - WiFi calling fails through most VPNs — carrier limitation, not fixable - Banking apps detect and block VPN — may need exclusion in split tunnel - Battery drain varies significantly — WireGuard most efficient by large margin ## Connection Failures - "Connected" but no internet — usually DNS misconfigured, not routing issue - Works on phone not laptop — local firewall or antivirus interfering - Constant reconnects — try TCP instead of UDP, increase keepalive interval ## Self-Hosted Traps - Exit IP is your home IP — services see where you live, no geo-bypass benefit - Requires static IP or dynamic DNS — clients can't find changing endpoints - Unmaintained server becomes liability — security updates are your responsibility

Frequently asked questions

VPN