Linux installer

v1.0.0

Installs, launches, and uninstalls Linux desktop apps by resolving the safest supported source first, then running a local helper CLI. Use when the user asks...

0· 137·0 current·0 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for baladoodle/linux-installer.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Linux installer" (baladoodle/linux-installer) from ClawHub.
Skill page: https://clawhub.ai/baladoodle/linux-installer
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install linux-installer

ClawHub CLI

Package manager switcher

npx clawhub@latest install linux-installer
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description match the included code and catalog: the CLI resolves install candidates and runs package-manager commands. The helper reads a local OpenClaw config (~/.openclaw/openclaw.json) to check the unsafe-community setting, which is coherent with the documented opt-in behavior.
Instruction Scope
SKILL.md restricts actions to resolving candidates, asking for confirmation, and then running explicit install/uninstall/launch commands. The code implements validations and will call local package tools (flatpak, snap, apt/dnf/pacman/zypper, nix, aur helpers, wine) and may bootstrap tooling via sudo when confirmed — this matches the documentation. It does not instruct broad system scans or exfiltration.
Install Mechanism
No remote downloads or obscure install URLs: the intended install is 'pip install -e .' from the skill directory (setup.py is included). The skill is instruction-plus-code (console entry points) and does not pull arbitrary archives from unknown hosts during install. The runtime may execute package-manager network actions, but those are expected for installing OS packages.
Credentials
The skill declares no secrets or required env vars. It does read ~/.openclaw/openclaw.json (to honor unsafeCommunityInstalls) and expands environment variables in catalog entries. It will run sudo and system package commands when performing installs/uninstalls — this is proportionate to the purpose but requires giving those commands elevated privileges at runtime (user confirmation is required per the docs).
Persistence & Privilege
always is false and the skill does not request to be force-enabled. It only reads local config and the bundled catalog; there is no sign it modifies other skills or system configurations beyond performing package installs when explicitly confirmed by the user.
Assessment
This skill appears internally consistent for resolving and installing Linux desktop apps, but check these before you install/use it: 1) Inspect the bundled catalog.json for any apps you care about (it will run package-manager commands that install software with sudo). 2) The helper reads ~/.openclaw/openclaw.json to allow unreviewed installs if you opt in — do not enable unsafeCommunityInstalls unless you understand the risk. 3) Installing the helper requires running pip install -e . from your skills folder; review the code (main.py, validate_catalog.py, setup.py) if you don't trust the publisher. 4) When the helper bootstraps tooling it will run sudo apt/dnf/pacman/zypper commands and systemctl/ln as documented — expect to be prompted for your password. 5) Because the registry 'Source' and homepage are missing, prefer obtaining this skill from a known repository or verifying the code locally before pip-installing it.

Like a lobster shell, security has layers — review code before you run it.

latestvk9747dhxpnj84p3r9ryqa6mz0s83nmgm
137downloads
0stars
1versions
Updated 1mo ago
v1.0.0
MIT-0

Linux Installer

What This Skill Does

Resolves the best supported install path for a Linux desktop app, explains the recommendation briefly, asks for confirmation before any system change, performs the install, and returns the exact launch or uninstall command.

If the chosen source needs missing tooling like snapd, flatpak, wine, or winetricks, the helper can bootstrap that tooling first through the host's native package manager.

It can also return curated community workarounds when no official Linux package exists. These must be clearly labeled and require an extra explicit confirmation before install.

When no curated or official path exists, the helper may surface unreviewed community suggestions from public package metadata. These are research results, not trusted install metadata.

Default source preference is:

  1. Flatpak
  2. Snap
  3. Native package manager
  4. openSUSE zypper
  5. Arch pacman
  6. Native Arch AUR helper
  7. Nix profile install
  8. AppImage
  9. Curated official manual/archive fallback
  10. Curated Wine/manual fallback

Community workarounds are only allowed when they are explicitly curated in the catalog.

Unreviewed community suggestions may be installed only when:

  1. skills.entries.linux-installer.unsafeCommunityInstalls is enabled in openclaw.json
  2. the user explicitly confirms the unreviewed install
  3. the install command includes --allow-unsafe

Prerequisites

Before using this skill, ensure the helper CLI is installed:

cd ~/.openclaw/skills/linux-installer
pip install -e .

Workflow

If you are expanding curated coverage, use CATALOG_GUIDE.md to decide which apps belong in catalog.json and which should rely on dynamic discovery.

When the user asks to install an app:

  1. Resolve the best path:
linux-installer resolve "gimp"
  1. Summarize the result:

    • chosen source
    • package id
    • whether it is an official package, fallback, or community workaround
    • whether it is curated or unreviewed
    • missing tooling, if any
    • tooling bootstrap command, if any
    • source URL, if available
    • public summary and any best-effort review note
    • exact install command
    • launch command
    • warnings or fallbacks
  2. Ask for confirmation before installing.

  3. If the selected result is a community workaround, ask for a second explicit confirmation that acknowledges it is unofficial/community-maintained.

  4. If the selected result is an unreviewed suggestion, explain that:

    • it was discovered dynamically from public package metadata
    • it is not maintainer-reviewed
    • opt-in support for unreviewed suggestions must be enabled first
    • it requires a separate unreviewed-install confirmation
  5. After confirmation, run:

linux-installer install "gimp" --source flatpak --package org.gimp.GIMP --yes

For a community workaround, include --allow-community:

linux-installer install "roblox" --source flatpak --package org.vinegarhq.Sober --yes --allow-community

For an unreviewed suggestion, include --allow-unsafe and ensure opt-in support for unreviewed suggestions is enabled in openclaw.json.

  1. Return the launch command:
linux-installer run-info "gimp" --source flatpak --package org.gimp.GIMP
  1. Optionally launch the installed app:
linux-installer run "gimp" --source flatpak --package org.gimp.GIMP
  1. For removal, prefer the helper's uninstall command. If the result is a manual or unsafe removal path, return the command or manual steps instead of improvising:
linux-installer uninstall "gimp" --source flatpak --package org.gimp.GIMP --yes

Rules

  • Never install anything before the user confirms.
  • Never install a community workaround without a second explicit confirmation.
  • Never install an unreviewed suggestion unless opt-in support is enabled and the user explicitly accepts the unreviewed path.
  • Prefer the helper CLI output over ad hoc shell reasoning.
  • If resolve says no safe automated path was found, do not invent install steps.
  • Manual/archive fallbacks may surface curated manual_steps, but the helper must not auto-download or auto-run them.
  • Manual/archive and other unsafe removal flows may surface manual_steps, but the helper must not auto-delete them unless the uninstall path is explicitly curated and safe.
  • Wine/manual flows are higher risk and should be presented as fallback options, not defaults.
  • Community workarounds must be presented as unofficial, curated alternatives.
  • Unreviewed suggestions must be presented as research findings, not trusted recommendations.
  • Always tell the user the exact command to launch the app after install.

Comments

Loading comments...