xget
Originally fromxixu-me/xget
Installation
Summary
URL rewriting and acceleration for package managers, registries, containers, APIs, and CI/CD workflows.
- Rewrites download URLs across npm, PyPI, crates.io, Docker registries, Git repositories, and inference APIs to route through a single Xget base URL for caching and acceleration
- Integrates with package managers, container builds, Git, CI/CD systems, and AI SDKs via environment variables, config files, and command-line prefixes
- Supports self-hosting and deployment patterns with live README guidance for Docker, Kubernetes, and shell configuration
- Resolves base URLs from environment or user input, then applies rewrites end-to-end across your project's build and deployment pipeline
SKILL.md
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_URLfrom 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.comonly 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.