ClawHub

macOS Automator

v1.0.0

Automate macOS tasks by composing and executing Automator workflows through automator CLI and AppleScript control.

⭐ 0· 454·2 current·2 all-time
byIván@ivangdavila
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
Name/description match required binaries (automator, osascript) and macOS Automator app path checks. Requested artifacts (workflow paths, local memory under ~/automator/) are appropriate and proportional to the stated goal of composing and running Automator workflows.
✓
Instruction Scope
Runtime instructions are limited to local Automator interfaces (automator CLI and AppleScript via osascript). The SKILL.md explicitly requires absolute paths, read-before-write checks, and two-step confirmations for destructive runs. The skill does propose writing a small local memory directory (~/automator/) but states writes require explicit user confirmation.
✓
Install Mechanism
Instruction-only skill with no install spec and no downloaded code. No archives or external packages are pulled in, which minimizes disk-write and supply-chain risk.
✓
Credentials
No environment variables, credentials, or unrelated config paths are requested. The only filesystem interaction is a local ~/automator/ directory for optional memory and confirmed workflow edits, which aligns with the skill's purpose.
✓
Persistence & Privilege
always:false and user-invocable; the skill will persist small local state in ~/automator/ when the user permits. It does not request system-wide config changes or other skills' credentials. AppleScript/Automator runs do require macOS automation/privacy permissions, which is expected for this functionality.
Assessment
This skill appears coherent with its purpose, but before enabling it: (1) verify you trust the skill source, (2) be prepared to grant macOS Automation permissions for Automator/osascript when prompted, (3) review any workflow files and absolute paths the agent proposes to run or edit (do not run unknown/destructive workflows), (4) allow the skill to create ~/automator/ only if you accept local storage of preferences and run logs, and (5) keep destructive operations gated by the two-step confirmations the skill requires. If you want extra caution, run in verbose/read-only mode first and back up important files before permitting write or destructive workflows.

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

latestvk976hq18yb7q1jxc0f035sa7f5824254

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Runtime requirements

A Clawdis
OSmacOS
Binsautomator, osascript

Comments