daemon-command-extension

Extend the AutomateLinux daemon with new commands via constants, handlers, and registry updates.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps developers extend the AutomateLinux daemon by adding new commands, enabling richer automation capabilities and customization of the daemon's behavior.

Core Features & Use Cases

  • Define new command signatures: Add command names and required parameters to the central registry.
  • Implement handlers: Write dispatcher logic to process the new command and generate a response.
  • Register and test: Wire up the command in the signature and dispatcher arrays and verify via build and test workflows.

Quick Start

Create a new command by updating daemon/include/Constants.h, implement a handler in daemon/src/mainCommand.cpp, register the signature in COMMAND_REGISTRY, map the dispatcher in COMMAND_HANDLERS, then build and run tests (e.g., d send MyNewAction --param "value").

Frequently Asked Questions about daemon-command-extension

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

FAQPage Schema
How do I add a new command to the AutomateLinux daemon?

Adding a new command to the AutomateLinux daemon involves updating Constants.h with signatures, writing a handler in mainCommand.cpp that returns CmdResult, and registering it in the COMMAND_REGISTRY and dispatcher arrays for proper routing.

What is the process for extending the AutomateLinux daemon's command interface?

Extending the command interface requires defining command signatures in the central registry, implementing handler logic to process requests and generate responses, and wiring up the dispatcher mappings followed by testing via the d CLI.

How do I test a new daemon command using the d CLI?

You test a new daemon command using the d CLI by sending a command with parameters, such as d send MyNewAction --param "value". This verifies that the newly registered handler processes the request correctly through the dispatcher.

Do I need to update the COMMAND_REGISTRY when extending the AutomateLinux daemon?

Yes, updating the COMMAND_REGISTRY is required when extending the AutomateLinux daemon. You must register the new command signature there and map it in the COMMAND_HANDLERS array to ensure the dispatcher routes requests to your new handler correctly.

What should a daemon command handler return when implemented in C++?

A daemon command handler implemented in C++ must return CmdResult. This standardizes the dispatcher logic to process the new command and generate the appropriate response within the AutomateLinux daemon architecture.