Provides practical guidance for using the simulang CLI and the @simular-ai/simulang-js runtime to author, run, and debug desktop automation scripts in TypeScript or JavaScript. Covers first-time setup (permissions on macOS), running modes (interactive REPL, headless, version pinning), API inspection via 'simulang which', and common pitfalls.
Invoke this skill when the user mentions simulang, is editing .ts/.mts/.js/.mjs/.simulang scripts that import simulang-js, or needs help with running, troubleshooting, or versioning simulang scripts. Useful for permission troubleshooting on macOS, choosing the correct simulang-js version, and recommending run flags.
Agents capable of invoking CLI commands, running Node scripts, and reading local project files (Copilot/GitHub-code-style agents, Claude Code, Codex, Gemini CLI) will work well with this skill.
simulang is a CLI skill for desktop automation using TypeScript/JavaScript via the simulang-js library. The SKILL.md is well-written with clear trigger conditions, version pinning docs, common pitfalls, and API lookup guidance. Two bundled .mjs scripts (postinstall and setup-permissions) were skipped by the runner due to .mjs extension but are clean on manual review — proper error handling, no destructive commands, no exfiltration risk.
@simular-ai/simulang-jspostinstall.mjs auto-runs on npm install but has good safety rails (bails if dist/ missing, catches all errors, never non-zero exit). setup-permissions.mjs shells out to /usr/sbin/screencapture but only on macOS and only to trigger TCC permission prompts — legitimate use. No security concerns.