Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
Version History
- The run_command documentation now uses computer and command names directly instead of requiring IDs. - Example payload construction for run_command now uses jq to safely escape and inject arguments, reducing the risk of JSON injection. - Clarified tips for omitting parameters in the run_command section. - No code or logic changes; documentation enhancements only.
What This Skill Does
TRIGGERcmd lets you list and run pre-registered commands on any computer tied to your account via its REST API. Commands are triggered by name, with optional parameters, from any machine with network access.
TRIGGERcmd provides a single API layer across multiple registered computers, removing the need to configure SSH or VPNs per machine.
When to use it
- Starting a home server backup script while at the office
- Launching an application on an unattended desktop remotely
- Toggling a media player on a living room PC from another device
- Running a maintenance script on a remote machine without SSH setup
- Checking which commands are registered across all your computers
Example Workflow
Here's how your AI assistant might use this skill in practice.
User asks: Run the backup script on MyLaptop
- 1Reads TRIGGERCMD_TOKEN from environment variable or token file
- 2Calls /api/command/list to confirm the backup command exists on MyLaptop
- 3Constructs JSON payload with computer and command names using jq to prevent injection
- 4Posts to /api/run/trigger and captures the API response
- 5Returns the confirmation message and queued status to the user
Backup script triggered on MyLaptop; API confirms the command is queued
Requirements
Accounts, API keys, or tools you or your AI assistant may need to set up while using this skill.