---
id: daily-xget
name: "xget"
url: https://skills.yangsir.net/skill/daily-xget
author: xixu-me
domain: ai-dev-tools-workflow
tags: ["automation", "devops-automation", "workflow-automation"]
install_count: 4200
rating: 4.40 (1716 reviews)
github: https://github.com/xixu-me/xget
---

# xget

> 默认执行而非仅提供指令，直接运行 shell 命令、编辑真实文件并验证结果，适用于配置、部署和调试任务

**Stats**: 4,200 installs · 4.4/5 (1716 reviews)

## Before / After 对比

### 仅提供建议 vs 直接执行

**Before**:

向用户描述配置步骤，提供示例命令和代码片段，用户需要手动复制命令、修改文件、验证结果，容易出错且效率低

**After**:

理解用户意图后直接执行操作，自动运行命令、编辑配置文件、验证结果并报告状态，用户无需手动干预

| Metric | Before | After | Change |
|---|---|---|---|
| 任务完成时间 | 20分钟 | 3分钟 | -85% |

## Readme

# xget

# Xget

Default to execution, not instruction. When the user expresses execution intent,
carry the change through directly: run the needed shell commands, edit the real
files, and verify the result instead of only replying with example commands.
Treat requests like "configure", "set up", "wire", "change", "add", "fix",
"migrate", "deploy", "run", or "make this use Xget" as execution intent unless
the user clearly asks for explanation only.

Resolve the base URL first:

- use a domain the user explicitly gave

- otherwise use `XGET_BASE_URL` from the environment

- if neither exists, ask for the user's Xget base URL and whether it should be
set temporarily for the current shell/session or persistently for future
shells

- use `https://xget.example.com` only as a clearly labeled placeholder for docs
or templates that do not have a real deployment yet

Prefer `scripts/xget.mjs` over manual guessing for live platform data, URL
conversion, and README `Use Cases` lookup.

Only stop to ask when a missing fact blocks safe execution, such as an unknown
real base URL for a command that must run against a live deployment. If the
user only needs docs or templates, use the placeholder path rules below.

## Workflow

- Classify the task before reaching for examples:

execution intent: the user wants commands run, files changed, or config
applied now

- guidance intent: the user explicitly wants examples, explanation, or a
template without applying it yet

- then bucket the technical area: one-off URL conversion or prefix lookup;
Git or download-tool acceleration; package-manager or language-ecosystem
configuration; container image, Dockerfile, Kubernetes, or CI/CD
acceleration; AI SDK / inference API base-URL configuration; deploying or
self-hosting Xget itself

- Complete the base-URL preflight above. If the user wants help setting
`XGET_BASE_URL`, open [the reference guide](https://github.com/xixu-me/xget/blob/HEAD/skills/xget/references/REFERENCE.md) and:

when the user asked you to set or wire it, run the shell-appropriate
temporary or persistent commands directly when the environment allows it

- when you cannot safely execute, ask the smallest blocking question or give
the exact command with the missing value clearly called out

- Pull live README guidance in two steps instead of loading the whole section
by default:

list candidate headings with `node scripts/xget.mjs topics --format json`

- narrow with `--match` or fetch a specific section with
`node scripts/xget.mjs snippet --base-url https://xget.example.com --heading "Docker Compose Configuration" --format text`

- Prefer the smallest relevant live subsection. If a repeated child heading
like `Use in Project` is ambiguous, fetch its parent section instead.

- Adapt the live guidance to the user's real task:

for execution intent, apply the change end-to-end instead of stopping at
example commands

- run commands yourself when the request is to install, configure, rewrite,
switch, migrate, test, or otherwise perform the change

- edit the actual config or source files when the user wants implementation,
not just explanation

- keep shell commands aligned with the user's OS and shell

- preserve existing project conventions unless the user asked for a broader
rewrite

- after changing files or running commands, perform a lightweight
verification step when practical

- Refresh the live platform map with
`node scripts/xget.mjs platforms --format json` when the answer depends on
current prefixes, and use `convert` for exact URL rewrites.

- Combine multiple live sections when the workflow spans multiple layers. For
example, pair a package-manager section with container, deployment, or `.env`
guidance when the user's project needs more than one integration point.

- Before finishing, sanity-check that every command, file edit, or example uses
the right Xget path shape:

repo/content: `/{prefix}/...`

- crates.io HTTP URLs: `/crates/...` rather than `/crates/api/v1/crates/...`

- inference APIs: `/ip/{provider}/...`

- OCI registries: `/cr/{registry}/...`

- If the live platform fetch fails or an upstream URL does not match any known
platform, say so explicitly and fall back to the stable guidance in
[references/REFERENCE.md](https://github.com/xixu-me/xget/blob/HEAD/skills/xget/references/REFERENCE.md) instead of inventing a
prefix.

Weekly Installs289Repository[xixu-me/xget](https://github.com/xixu-me/xget)GitHub Stars7.8KFirst Seen3 days agoSecurity Audits[Gen Agent Trust HubFail](/xixu-me/xget/xget/security/agent-trust-hub)[SocketWarn](/xixu-me/xget/xget/security/socket)[SnykWarn](/xixu-me/xget/xget/security/snyk)Installed ongithub-copilot289codex289warp289kimi-cli289gemini-cli289cursor289

---
*Source: https://skills.yangsir.net/skill/daily-xget*
*Markdown mirror: https://skills.yangsir.net/api/skill/daily-xget/markdown*