Device Control (Iyeque)

v1.1.1

Expose safe device actions (volume, brightness, open/close apps) for personal automation.

0· 811·1 current·1 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for iyeque/iyeque-device-control.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Device Control (Iyeque)" (iyeque/iyeque-device-control) from ClawHub.
Skill page: https://clawhub.ai/iyeque/iyeque-device-control
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Required binaries: node
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install iyeque-device-control

ClawHub CLI

Package manager switcher

npx clawhub@latest install iyeque-device-control
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
medium confidence
Purpose & Capability
The skill claims to control volume, brightness, and apps and only requires node in metadata, which is consistent with the included ctl.js that shells out to platform-native tools (pactl/amixer, osascript, brightnessctl, nircmd, pkill/taskkill). The manifest does not request unrelated credentials or config paths. One inconsistency: SKILL.md says the `app` parameter may be an application name or path, but the code's sanitizeAppName disallows path separators ('/') so passing a full path will be rejected.
Instruction Scope
SKILL.md instructs running the bundled ctl.js with actions and arguments; the code follows those instructions and documents platform-specific dependencies. The runtime does read /proc/version to detect WSL and executes local system binaries. Inputs are validated with strict allowlists for app names and integer validation for numeric values, which limits command-injection risk. However some commands are invoked via shell (exec/execPromise) rather than execFile in a few platform branches (macOS osascript, nircmd and Windows powershell usage, Linux open_app uses exec), which is expected for these platform-specific tools but is worth noting.
Install Mechanism
No install script is provided (instruction-only with one included JS file). Nothing is downloaded or extracted by the skill itself. The skill relies on external platform utilities (pactl/amixer/brightnessctl/osascript/nircmd/pkill/taskkill) which the SKILL.md documents; installing those is left to the user and is expected for this capability.
Credentials
The skill requests no environment variables or credentials and does not access network endpoints or secrets. Its access is limited to local filesystem reads (to detect WSL) and launching local system binaries — proportional to the stated device-control purpose.
Persistence & Privilege
The skill is not always-enabled and does not request elevated or persistent platform privileges, nor does it modify other skills or system-wide agent settings. It only executes ad-hoc commands when invoked.
Assessment
This skill appears to do what it says: run local system commands to control volume, brightness, and open/close apps. Before installing or using it, consider: (1) it runs platform binaries on your machine — ensure you trust those utilities (e.g., nircmd on Windows) and install them from official sources; (2) SKILL.md mentions supplying an app path but the code rejects path separators, so use application names (not full paths) or update the skill if you need path support; (3) although inputs are allowlisted and numeric inputs validated, the skill sometimes invokes shell commands (necessary for certain platforms); only give it to agents you trust to run local commands; (4) test the skill in a safe environment first to confirm behavior on your OS. If you need the skill to accept full paths or handle other app name characters, request the author clarify or patch the sanitizeAppName behavior.

Like a lobster shell, security has layers — review code before you run it.

Runtime requirements

🎛️ Clawdis
Binsnode
latestvk9783n8qhr9ngphpyn6japqy1n81a3tj
811downloads
0stars
3versions
Updated 2mo ago
v1.1.1
MIT-0

Device Control Skill

Control device volume, brightness, and applications via command line. Supports Linux, macOS, Windows, and WSL.

Security

All inputs are validated and sanitized to prevent command injection:

  • Volume/brightness values must be numbers between 0-100
  • App names are restricted to alphanumeric characters, spaces, dashes, and underscores
  • Shell metacharacters are blocked

Tool API

device_control

Execute a device control action.

  • Parameters:
    • action (string, required): One of set_volume, change_volume, set_brightness, open_app, close_app.
    • value (string/number, optional): The value for the action (0-100 for volume/brightness, delta for change_volume).
    • app (string, optional): The application name or path (required for open/close actions).

Usage:

# Set volume to 50%
node skills/device-control/ctl.js --action set_volume --value 50

# Change volume by +10 or -10
node skills/device-control/ctl.js --action change_volume --value 10
node skills/device-control/ctl.js --action change_volume --value -10

# Set brightness to 75%
node skills/device-control/ctl.js --action set_brightness --value 75

# Open an application
node skills/device-control/ctl.js --action open_app --app "firefox"
node skills/device-control/ctl.js --action open_app --app "Visual Studio Code"

# Close an application
node skills/device-control/ctl.js --action close_app --app "firefox"

Platform Support

ActionLinuxmacOSWindowsWSL
set_volume✅ (pactl/amixer)✅ (osascript)✅ (nircmd)✅ (nircmd)
change_volume
set_brightness✅ (brightnessctl)⚠️ (requires brightness CLI)✅ (WMI)✅ (WMI)
open_app
close_app✅ (pkill)✅ (pkill)✅ (taskkill)✅ (taskkill)

Requirements

  • Linux: pactl (PulseAudio) or amixer (ALSA), brightnessctl (optional, for brightness)
  • macOS: Built-in osascript, brightness CLI tool (optional, for brightness)
  • Windows/WSL: nircmd.exe for volume control (download from nirsoft.net)

Comments

Loading comments...