daemon-port-management

Registers and manages application ports in the AutomateLinux daemon via the d command suite.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/yanivprusman/automateLinux --skill daemon-port-management
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: daemon-port-management
Source: https://github.com/yanivprusman/automateLinux/tree/main/.agent/skills/daemon-port-management
Command: npx skills add https://github.com/yanivprusman/automateLinux --skill daemon-port-management

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The AutomateLinux daemon requires a reliable method to register, track, and resolve local application ports to support cross-component service discovery and dynamic wiring of services.

Core Features & Use Cases

  • Central port registry: persist and retrieve port mappings for apps and services.
  • Command-based management: setPort, getPort, listPorts, and deletePort to manage ports from any client.
  • Use Case: A dashboard app needs to bind to a local port for live data streaming; the skill ensures the port is registered and discoverable by other components at runtime.

Quick Start

Run d setPort --key pt --value 3002 to register a port for Public Transportation, then use d listPorts to view all registrations and d getPort --key pt to retrieve the port value.

Frequently Asked Questions about daemon-port-management

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

FAQPage Schema
How do I register and manage local ports for service discovery in AutomateLinux?

Register local ports for service discovery in AutomateLinux using the d command suite: setPort, getPort, listPorts, and deletePort. These commands persist and query port mappings within the daemon's SettingsTable using port_ prefixed keys.

What is centralized port control and how does it support dynamic wiring of services?

Centralized port control provides a reliable registry to track and resolve local application ports. It supports dynamic wiring during runtime by allowing cross-component service discovery, enabling components like dashboards to find and bind to necessary local ports.

Can I use the daemon port management commands to dynamically bind ports for web services and dashboards?

Yes, you can use the daemon port management commands to dynamically bind ports for web services, dashboards, and CAD tools. The skill applies across components needing local port mappings, ensuring ports are registered and discoverable at runtime.

How do I list all registered application ports and retrieve a specific port value?

To list all registered application ports, run the d listPorts command. To retrieve a specific port value, use d getPort --key <your_key>, substituting your specific port_ prefixed key to query the daemon's SettingsTable.

Does cross-component port registration require specific dependencies or components?

No specific dependencies or components are required for cross-component port registration. The skill operates independently using the AutomateLinux daemon's SettingsTable and the integrated d command suite to manage port mappings.

When should I use deletePort to manage local port mappings within the daemon?

Use the deletePort command when an application or service is decommissioned and its local port mapping needs to be removed from the centralized registry. This ensures the daemon's SettingsTable remains clean and prevents port conflicts during runtime service discovery.