Top-level Linux computer-use skill with a bundled standalone runtime that bootstraps itself without any local Claude installation, private native modules, or extracted app assets.
Installs into .claude/skills of the current project.
Are you the author of Computer Use Linux?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/lord1egypt-computer-use-linux)
---
name: computer-use-linux
version: 0.1.1
description: Top-level Linux 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
- linux
- computer-use
- automation
- mcp
---
# Linux Computer-Use Skill
Use this skill when the task needs a portable Linux computer-use skill bundled with its own standalone runtime and MCP server.
## What this skill does
- uses the bundled `linux-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 Linux-only because the underlying desktop-control backend is Linux-specific
## Default bundled project path
After installation, assume the standalone project lives at:
```bash
~/.codex/skills/computer-use-linux/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-linux/project
npm install
npm run build
```
## Run
```bash
cd ~/.codex/skills/computer-use-linux/project
node dist/cli.js
```
The first real run will automatically create `.runtime/venv` and install the public Python dependencies.
## Validation notes
- Version `0.1.1` fixes the shared system-key blocklist and tool capability typings so Linux builds use Linux-specific shortcut protections instead of a broken copied platform branch.
- This project has been statically validated from macOS for TypeScript build health, bundled project integrity, and Python helper syntax, but still needs end-to-end runtime validation on a real Linux desktop.
## 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.
