How do I install the Compuse skill?

Run npx skillmds@latest add lord1egypt/compuse in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Compuse safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: FAIL. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Compuse?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Compuse free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Compuse?

Lord1Egypt (@lord1egypt) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Compuse by lord1egypt — Agent Skill

Name: Compuse
Rating: 4.2 (5 reviews)
Author: Lord1Egypt

File contents

Cross-Platform Computer-Use Skill

Use this skill when the task needs a top-level portable computer-use skill that works across macOS, Windows, and Linux without depending on any local Claude installation, private native modules, or extracted app assets.

What this skill does

bundles standalone platform runtimes for macOS, Windows, and Linux
installs one top-level skill that contains all three platform payloads
selects the correct project for the current host platform
preserves the standalone bootstrap model: each platform runtime creates its own virtualenv and installs public Python dependencies on first real run
keeps platform-specific limitations explicit instead of pretending the hosts behave identically

Installed layout

After installation, assume the top-level skill lives at:

~/.codex/skills/compuse

The bundled projects are stored under:

~/.codex/skills/compuse/project/platforms/macos
~/.codex/skills/compuse/project/platforms/windows
~/.codex/skills/compuse/project/platforms/linux

Platform selection

Use the helper script from the installed skill root to resolve the active platform project:

bash ~/.codex/skills/compuse/scripts/current-project.sh

On PowerShell:

powershell -ExecutionPolicy Bypass -File $HOME/.codex/skills/compuse/scripts/current-project.ps1

Build

Always build the selected platform project, not all three at once:

cd "$(bash ~/.codex/skills/compuse/scripts/current-project.sh)"
npm install
npm run build

Run

cd "$(bash ~/.codex/skills/compuse/scripts/current-project.sh)"
node dist/cli.js

Validation notes

macOS has been real-device validated in this workspace, including GUI typing round-trip through the MCP type tool.
Windows and Linux are implemented, built, packaged, and published, but still need end-to-end runtime validation on real hosts.
Linux currently targets X11 first; Wayland can restrict screenshots, focus inspection, clipboard, and synthetic input.

Guardrails

Treat this host as trusted-local only.
Do not tell the user to search a local Claude install for binaries or hidden assets.
Be explicit about the current host platform and its validation status before claiming something is verified.
Mention that current runtimes report screenshotFiltering: none, so action gating is handled at the MCP layer.

---name: compusedescription: Top-level cross-platform computer-use skill that bundles standalone macOS, Windows, and Linux runtimes with zero local Claude dependency and selects the correct platform payload at install/use time.---# Cross-Platform Computer-Use SkillUse this skill when the task needs a top-level portable computer-use skill that works across macOS, Windows, and Linux without depending on any local Claude installation, private native modules, or extracted app assets.## What this skill does- bundles standalone platform runtimes for `macOS`, `Windows`, and `Linux`- installs one top-level skill that contains all three platform payloads- selects the correct project for the current host platform- preserves the standalone bootstrap model: each platform runtime creates its own virtualenv and installs public Python dependencies on first real run- keeps platform-specific limitations explicit instead of pretending the hosts behave identically## Installed layoutAfter installation, assume the top-level skill lives at:```bash~/.codex/skills/compuse```The bundled projects are stored under:```bash~/.codex/skills/compuse/project/platforms/macos~/.codex/skills/compuse/project/platforms/windows~/.codex/skills/compuse/project/platforms/linux```## Platform selectionUse the helper script from the installed skill root to resolve the active platform project:```bashbash ~/.codex/skills/compuse/scripts/current-project.sh```On PowerShell:```powershellpowershell -ExecutionPolicy Bypass -File $HOME/.codex/skills/compuse/scripts/current-project.ps1```## BuildAlways build the selected platform project, not all three at once:```bashcd "$(bash ~/.codex/skills/compuse/scripts/current-project.sh)"npm installnpm run build```## Run```bashcd "$(bash ~/.codex/skills/compuse/scripts/current-project.sh)"node dist/cli.js```## Validation notes- `macOS` has been real-device validated in this workspace, including GUI typing round-trip through the MCP `type` tool.- `Windows` and `Linux` are implemented, built, packaged, and published, but still need end-to-end runtime validation on real hosts.- `Linux` currently targets `X11` first; Wayland can restrict screenshots, focus inspection, clipboard, and synthetic input.## Guardrails- Treat this host as trusted-local only.- Do not tell the user to search a local Claude install for binaries or hidden assets.- Be explicit about the current host platform and its validation status before claiming something is verified.- Mention that current runtimes report `screenshotFiltering: none`, so action gating is handled at the MCP layer.

Frequently asked questions

Compuse