OpenParable
Skip to content
← Back to skills

Xlings Quickstart

Apps & Automation
xlings-quickstart

Xlings Quickstart is an Agent Skill for apps & automation published in the openxlings/xlings repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

使用 xlings (XLINGS Quickstart) 进行工具安装、版本管理、包索引扩展和 subos 环境隔离的操作指南。When tasks involve `xlings`/`xim` package install-search-update-remove flows, namespace package handling, self-hosted/custom index repo setup, or multi-version/subos troubleshooting, use this skill.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/openxlings/xlings/blob/HEAD/.agents/skills/xlings-quickstart/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/xlings-quickstart, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

XLINGS Quickstart

Overview

Use this skill to handle the full operational lifecycle of xlings:

  • Install xlings and verify runtime.
  • Install/search/remove/update tools and env presets via xlings/xim.
  • Work with namespace packages and version selectors.
  • Add custom/self-hosted package index repos and refresh index.
  • Diagnose multi-version switching and subos environment isolation behavior.

Installation Workflow

1) Install xlings

Linux/macOS:

curl -fsSL https://raw.githubusercontent.com/openxlings/xlings/refs/heads/main/tools/other/quick_install.sh | bash

Windows PowerShell:

irm https://raw.githubusercontent.com/openxlings/xlings/refs/heads/main/tools/other/quick_install.ps1 | iex

2) Verify installation

xlings help
xim -h

If xlings/xim is not found, reload shell profile (source ~/.bashrc) and retry.

Common Usage and Scenarios

Use these commands first for daily operations:

xlings install gcc@15
xlings remove gcc
xlings search gcc
xlings update gcc

Use xim directly when you need lower-level package-index operations:

xim -s gcc
xim -l
xim --update index

Scenario guide:

  • Need one tool quickly: xlings install <name> or xlings install <name>@<version>.
  • Need to inspect candidates first: xlings search <keyword> / xim -s <keyword>.
  • Need to cleanup: xlings remove <name>.
  • Need to refresh package metadata: xim --update index.

Namespace and Custom Index

Package name forms to support:

  • <name>
  • <name>@<version>
  • <namespace>:<name>
  • <namespace>:<name>@<version>

For custom or self-hosted index repos, register sub-indexrepo with namespace binding:

xim --add-indexrepo <namespace>:<git-repo-url>
xim --update index

For ad-hoc package file onboarding:

xim --add-xpkg /path/to/your.xpkg.lua
# or
xim --add-xpkg https://your-host/path/to/your.xpkg.lua

Multi-Version and Subos Isolation

Use xvm through xlings for version switching:

xlings use <tool>
xlings use <tool> <version>

Use subos commands when workloads need isolated env views:

xlings subos list
xlings subos new <env-name>
xlings subos use <env-name>

Operational model to remember:

  • Package store can be shared globally.
  • Active tool mapping/version visibility is managed per subos via xvm metadata.
  • Namespace + version selector avoids collisions for similarly named packages.

References