mac-display-control
v1.0.0Step-by-step guide for controlling external display or monitor settings on a Mac without third-party GUI apps. Covers Apple Silicon and Intel Macs, all major...
⭐ 0· 97·0 current·0 all-time
by@oakland
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description align with content: all required actions (DDC/CI probing, brightness/contrast/volume/input control, and a software fallback) are covered by the provided shell commands and Automator/cron integration. No unrelated credentials, binaries, or config paths are requested.
Instruction Scope
SKILL.md instructs only local actions necessary for display control: installing Homebrew packages (m1ddc/ddcctl), running DDC commands, creating scripts in ~/scripts, using Automator and cron, and an osascript fallback. The instructions reference creating a temp file (/tmp/display_last_volume) and local scripts, which is expected for the described functionality.
Install Mechanism
This is instruction-only (no install spec). It recommends installing packages via Homebrew (brew install m1ddc / ddcctl) which is appropriate, but also shows the Homebrew installer curl one-liner (remote install script). Running remote install scripts is a standard convenience but carries inherent risk — users should review the installer and package sources before running.
Credentials
No environment variables, credentials, or config paths are requested. The skill's local file writes (e.g., /tmp/display_last_volume, ~/scripts) are proportionate to the mute-toggle and shortcut automation use cases.
Persistence & Privilege
The skill does not request persistent elevated privileges nor set always:true. It instructs creating user-level scripts and using Automator/cron, which is normal for this functionality and limited to the user's account.
Assessment
This is a locally scoped how-to for controlling monitors via DDC/CI and macOS scripting. Before following it: (1) review any remote install commands (the Homebrew curl installer) and prefer installing Homebrew via official instructions or your package manager; (2) verify the Homebrew formulas' sources for m1ddc/ddcctl if you want maximum assurance; (3) be aware DDC commands can change persistent display firmware settings (factory reset is irreversible), and power/rotation commands can have disruptive effects — test carefully; (4) Automator/osascript actions may require granting Automation/Accessibility permissions in System Settings; and (5) scripts created in ~/scripts and temp files like /tmp/display_last_volume run as your user, so inspect any pasted scripts before making them executable.Like a lobster shell, security has layers — review code before you run it.
latestvk97c28301sehyze9esjxjt349x83tnbq
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
