Portless
OfficialPortless allows you to seamlessly redirect HTTP requests to any URL, enhancing website flexibility and facilitating dynamic content delivery.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add vercel-labs/portless --skill portless -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
vercel-labs
Matched to the vendor's own GitHub organisation.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned vercel-labs/portless at 67c4739921.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 67c4739921
- Manifest
- skills/portless/SKILL.md
- Scanned
- 1 file, 432 lines
About this skill
What it does
Portless allows you to replace traditional port numbers in URLs with stable, named .localhost addresses. This simplifies development workflows by eliminating port conflicts, making it easier for both humans and AI agents to access applications. It provides a consistent URL structure regardless of the underlying port being used, preventing issues like stale browser tabs or incorrect configurations when ports change.
When to use it
- Resolving Port Conflicts: When multiple projects attempt to run on the same port (EADDRINUSE errors).
- Simplifying Development Sharing: Easily share URLs with teammates without needing to specify port numbers in communication.
- Managing Monorepos: Streamline development and testing across multiple services within a monorepo.
- AI Agent Interactions: Ensure AI agents consistently access the correct application, avoiding hardcoded or incorrect port assumptions.
- Git Worktrees: Provide unique URLs for each worktree in a Git repository.
Key capabilities
- Replaces port numbers with
.localhostURLs. - Automatic HTTPS proxy startup.
- Supports explicit subdomain routing (e.g.,
api.myapp.localhost). - Wildcard subdomain support (--wildcard flag).
- Detects and handles Git worktrees, prepending branch names as subdomains.
- Can be installed globally or as a project dependency.
Example prompts
- "Run my Next.js application using Portless."
- "Start the Portless proxy for my 'myapp' application running
next dev." - "Expose my API service at
api.myapp.localhost."
Tips & gotchas
- Installation: It is recommended to install Portless globally (
npm install -g portless) or as a project development dependency (npm install -D portless). Avoid usingnpxfor one-off executions. - Non-Interactive Environments: In CI/CD environments (no TTY, or
CI=1), Portless will exit with an error message instead of prompting for input. - Strict Mode: By default, only explicitly registered subdomains are routed. Use the
--wildcardflag to allow any subdomain to fall back to a defined application.