design-creative
Run a Public Portal Relay with portal-relay
Learn how to set up a public Portal relay using the portal-relay skill, with Docker Compose, DNS delegation, and game-server support.
Where this fits
You're a developer who wants to contribute to the Portal network, but the public relays are congested. You have a Linux box with a public IP and want to run your own relay to reduce latency and add resilience. The portal-relay skill automates the setup: Docker Compose, DNS delegation, and optional game-server ports — turning a manual, error-prone process into a single prompt.
Why agents benefit
- One-shot provisioning: The agent generates and runs the entire Docker Compose stack, eliminating step-by-step manual configuration.
- Automatic DNS delegation: It handles the one-time NS record setup, so your relay's authoritative DNS works without external tooling.
- Game-server ready: The skill can open TCP/UDP lease ports (e.g., 27015-27020) for hosting game servers through the relay.
- Public pool registration: It registers your relay in the public relay pool, making it discoverable by other Portal clients immediately.
- Health verification: The agent checks that the relay is live and reachable, giving you confidence before you share it.
Practical scenarios
Contribute to the Portal network
You want to give back to the ecosystem. With portal-relay, you can spin up a relay on a spare VPS in minutes, then add it to the public pool. The agent handles the DNS delegation and registration, so your contribution is live without manual intervention.
Self-host for low-latency tunneling
Your team's tunnel traffic is suffering from high latency on public relays. By running your own relay in a region close to your users, you cut round-trip times. The skill's Docker Compose setup makes it trivial to deploy on any Linux host with a public IP.
Open a relay with game-server support
You're running a multiplayer game and need dedicated UDP/TCP ports. The skill configures lease ports, allowing players to connect through your relay without exposing your entire host. This is ideal for private gaming communities or testing game networking.
Add it to your agent workflow
Install the skill with:
npx skills add gosuda/portal-tunnel --skill portal-relay
Then ask your agent: "Set up a portal relay on this host with game-server ports 27015-27020." The agent will create the compose file, start the services, configure DNS, and register the relay. No manual steps required.
Compare before adopting
Before committing, compare this skill against alternatives. Check the GitHub repo's stars (263) and recent commits for maintenance freshness. Consider whether you need portal-expose (for exposing local services) instead — portal-relay is specifically for running a relay, not for tunneling out. Also evaluate if you prefer a manual setup or a different relay implementation from the Portal ecosystem.
Why it is worth tracking
The Portal network thrives on community contributions, and portal-relay lowers the barrier to running a relay. Its MIT license, active author, and growing star count signal a healthy project. Track it if you value decentralized infrastructure or plan to self-host relays for performance or privacy. Evaluate it whenever you need a relay that's under your control — it's a practical, well-scoped skill that fits neatly into an agent's deployment toolkit.
For more details, see the OpenAgentSkill listing at https://www.openagentskill.com/skills/gosuda-portal-relay.
Featured Skill
portal-relay
Skill by gosuda