Skip to content
Back to skills

Computer Use Macos

ASecurity

Top-level macOS computer-use skill with a bundled standalone runtime that bootstraps itself without any local Claude installation, private native modules, or extracted app assets.

  • 3 stars
  • 0 votes
  • 0 copies
  • 4 views
  • Added September 9, 2026
toolspythonrustbashnoderailsbackend

Works with

  • cli
  • mcp

Security analysis

A96/100
  • mediumInstalls packages at runtime which could introduce malicious dependencies

Pro shows the line behind each finding and how to fix it

Scanned September 9, 2026

npx -y skills add Lord1Egypt/awesome-skill-forge --skill computer-use-macos --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Computer Use Macos?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Computer Use Macos
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/lord1egypt-computer-use-macos/badge)](https://www.skillsdirectory.com/skills/lord1egypt-computer-use-macos)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: computer-use-macos
version: 0.2.2
description: Top-level macOS computer-use skill with a bundled standalone runtime that bootstraps itself without any local Claude installation, private native modules, or extracted app assets.
tags:
  - skill
  - macos
  - computer-use
  - automation
  - mcp
---

# macOS Computer-Use Skill

Use this skill when the task needs a portable macOS computer-use skill bundled with its own standalone runtime and MCP server.

## What this skill does

- uses the bundled `macos-computer-use-skill` project under the installed skill directory
- builds the standalone MCP server
- lets the server auto-bootstrap its Python runtime on first launch
- avoids any dependency on local Claude binaries, `.node` modules, or extracted app assets
- stays explicitly macOS-only because the underlying desktop-control backend is macOS-specific

## Default bundled project path

After installation, assume the standalone project lives at:

```bash
~/.codex/skills/computer-use-macos/project
```

If the user installed the skill under a custom `CODEX_HOME`, use that equivalent path instead.

## Build

Always build from the bundled project:

```bash
cd ~/.codex/skills/computer-use-macos/project
npm install
npm run build
```

## Run

```bash
cd ~/.codex/skills/computer-use-macos/project
node dist/cli.js
```

The first real run will automatically create `.runtime/venv` and install the public Python dependencies.

## Validation notes

- On real macOS hosts, prefer validating typing through the MCP `type` tool path, not only low-level helper calls.
- Version `0.2.2` routes ordinary macOS text input through clipboard paste when available, avoiding IME/input-source corruption seen with per-key typing under Chinese input methods.

## Guardrails

- Treat this host as trusted-local only.
- Do not tell the user to search their local Claude install for binaries or hidden assets.
- Be explicit that this runtime is standalone and uses public dependencies only.
- Mention that the current runtime reports `screenshotFiltering: none`, so action gating is handled at the MCP layer.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in tools →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.