service-ports

Register and manage service ports in Goliath projects via package.json.

Updated May 13, 2026
One-click install
npx skills add https://github.com/dloschiavo/orca --skill service-ports
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: service-ports
Source: https://github.com/dloschiavo/orca/tree/main/recipe/service-ports
Command: npx skills add https://github.com/dloschiavo/orca --skill service-ports

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the management of service ports in Goliath projects, ensuring that services can be easily discovered and operated.

Core Features & Use Cases

  • Service Port Registration: Automatically registers running services in a consistent format.
  • Port Conflict Resolution: Handles port collisions by hunting for a free port and evicting prior instances when necessary.
  • Service Identity Management: Stores service identity (role, name, port, framework) in the package.json for a single source of truth.
  • Use Case: For a Goliath project with multiple services (e.g., a server and a web app), this Skill ensures that the web app can discover and connect to the server using its canonical port without manual port management.

Quick Start

Use the service-ports skill with pnpm dev to start your development server and have it register its service port automatically.

Frequently Asked Questions about service-ports

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate service port management in Goliath projects?

Automate service port management by using a helper script that registers running services, resolves port collisions, and stores service identity in package.json for consistent discovery across multi-service projects.

How do I resolve port conflicts when running multiple local services?

Resolve port conflicts using a helper script that hunts for free ports and evicts prior instances when necessary, ensuring multi-service projects operate without manual port configuration.

Where should I store service identity for local service discovery?

Store service identity in package.json as a single source of truth, capturing the service role, name, port, and framework to enable consistent discovery and connection across Goliath projects.

Can I use this port discovery tool with pnpm?

Yes, you can use this tool with pnpm by running pnpm dev to start your development server, which automatically registers the service port and handles identity management without manual intervention.

What is the best way to handle port registration for a multi-service project?

Handle port registration by deploying a helper script that modifies package.json and interacts with a local registry, automatically assigning canonical ports so web apps can discover and connect to servers.

Why does my web app fail to discover and connect to the server port?

Connection failures occur when service ports are managed manually; automating registration via package.json ensures the web app discovers the server using its canonical port without configuration drift.