port-daddy-cli

Assign atomic development ports to services for local multi-agent workflows.

2|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/curiositech/port-daddy --skill port-daddy-cli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: port-daddy-cli
Source: https://github.com/curiositech/port-daddy/tree/main/.gemini/extensions/port-daddy/skills/port-daddy-cli
Command: npx skills add https://github.com/curiositech/port-daddy --skill port-daddy-cli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Port conflicts, race conditions, and uncoordinated agent workflows in local development slow down iteration and cause flaky behavior; this Skill provides atomic port assignment, coordination primitives, and recovery mechanisms to eliminate those issues.

Core Features & Use Cases

  • Atomic Port Assignment: Deterministic mapping from semantic identities to stable development ports to avoid collisions between agents.
  • Multi-Agent Coordination: Pub/sub messaging, distributed locks, and an agent registry with heartbeats to coordinate concurrent developer or AI agent tasks.
  • Project Scanning & Configuration: Deep-scans repositories to generate .portdaddyrc service definitions and bring up all local services consistently.
  • Diagnostics & Recovery: Health checks, a diagnostic doctor command, and automatic salvage of crashed agent sessions to recover work.

Quick Start

Claim a stable development port and register your agent by invoking the port-daddy CLI to claim your service identity and start the daemon if needed.

Frequently Asked Questions about port-daddy-cli

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

FAQPage Schema
How do I prevent dev port conflicts when running multiple local agents?

To prevent dev port conflicts, assign atomic development ports to services using semantic identity mapping, ensuring stable port allocation and eliminating collisions between concurrent agents.

What is the best way to coordinate multi-agent workflows and prevent race conditions?

Multi-agent coordination is best achieved through pub/sub messaging, distributed locks, and an agent registry with heartbeats to synchronize concurrent tasks and prevent race conditions.

How do I automatically generate configuration for all local development services?

Generate local service configuration by deep-scanning project repositories to automatically create .portdaddyrc service definitions for bringing up all services consistently.

Do I need a specific environment setup to use atomic port assignment and distributed locks?

Yes, atomic port assignment and distributed locks require a running Port Daddy daemon reachable at localhost:9876, supporting CLI, HTTP, and SDK integrations with SQLite-backed state.

Why are my local development agents experiencing resource contention and flaky behavior?

Resource contention and flaky behavior occur due to uncoordinated agent workflows and race conditions, which can be resolved by applying atomic port assignment and coordination primitives.

How can I diagnose daemon health and recover crashed agent sessions?

Diagnose daemon health and recover crashed agent sessions by running health checks, a diagnostic doctor command, and automatic salvage mechanisms to restore work from failed agents.