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.
3 stars
0 votes
0 copies
0 views
Added September 9, 2026
toolspythonrustshellbashnoderails
Works with
cli
mcp
Security analysis
A96/100
mediumInstalls packages at runtime which could introduce malicious dependencies
Installs into .claude/skills of the current project.
Sponsors
SSkills DirectorySkills Directory
Know which skills are safe — weekly.
SSkills DirectorySkills Directory
Is that skill safe to install?
Are you the author of Deskuse?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/lord1egypt-deskuse)
---
name: deskuse
version: 0.1.0
description: 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.
tags:
- skill
- computer-use
- automation
- mcp
- macos
- windows
- linux
---
# 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:
```bash
~/.codex/skills/deskuse
```
The bundled projects are stored under:
```bash
~/.codex/skills/deskuse/project/platforms/macos
~/.codex/skills/deskuse/project/platforms/windows
~/.codex/skills/deskuse/project/platforms/linux
```
## Platform selection
Use the helper script from the installed skill root to resolve the active platform project:
```bash
bash ~/.codex/skills/deskuse/scripts/current-project.sh
```
On PowerShell:
```powershell
powershell -ExecutionPolicy Bypass -File $HOME/.codex/skills/deskuse/scripts/current-project.ps1
```
## Build
Always build the selected platform project, not all three at once:
```bash
cd "$(bash ~/.codex/skills/deskuse/scripts/current-project.sh)"
npm install
npm run build
```
## Run
```bash
cd "$(bash ~/.codex/skills/deskuse/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.