# Accelerate Downloads and Registry URLs with Xget

Developers spend time rewriting package, container, and API endpoints for Xget deployments. This skill fetches current Xget guidance and applies matching URL and configuration changes.

## Install

```bash
npx skillstore add xixu-me/xget
```

## Metadata

- Status: approved
- Slug: xixu-me-xget
- Skillstore revision: r1
- Version status: missing
- Tree hash: 0c8742b82d38d1867c74acda6990391860b3aa14afd4808391ae54fcb64d8e87
- Author: xixu-me
- GitHub username: xixu-me
- License: MIT
- Repository: https://github.com/xixu-me/skills/tree/main/skills/xget/
- Ref: 64ca8af0f54a325752f08bd54e52151061ea659a
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: confirmation\_required
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network, filesystem, env\_access
- Quality score: 38
- Quality tier: warning
- Public page: https://skillstore.pages.dev/skills/xixu-me-xget
- Manifest: https://skillstore.pages.dev/api/skills/xixu-me-xget/manifest

## Capabilities

- Resolve an Xget base URL from user input, command options, or XGET\_BASE\_URL.
- Convert supported upstream URLs to Xget path prefixes using the live platform catalog.
- Fetch README Use Cases sections and rewrite examples to a chosen base URL.
- List supported platforms and matching README headings through the included Node helper.
- Adapt Xget configuration for package managers, containers, CI/CD, and AI SDKs.

## Use Cases

- Convert Project Download URLs: Rewrite repository, release, or package URLs so a project can route downloads through an Xget deployment.
- Configure CI and Container Builds: Apply Xget registry and download endpoints inside Dockerfiles, compose files, and automation workflows.
- Route AI SDK Requests: Update SDK base URLs for supported inference providers while preserving existing authentication behavior.

## Prompt Templates

### Convert One URL

```
Convert this upstream URL to my Xget base URL: [URL]. Use [BASE_URL] and explain the matched platform.
```

### Configure a Package Manager

```
Update this project to use Xget for [npm, pip, cargo, or another tool]. Inspect relevant config files and make minimal changes.
```

### Wire CI and Containers

```
Adapt my Dockerfile and CI workflow to use Xget. Keep current build behavior and summarize the changed files.
```

### Plan a Repository Migration

```
Review this repository for download, registry, and AI SDK endpoints. Replace safe targets with my Xget deployment and list any risks.
```

## Limitations

- Requires network access to GitCode raw URLs for the latest platform map and README.
- Can modify shell profiles or project configuration when the user requests execution.
- Does not verify that a custom Xget deployment is reachable.
- Live upstream content changes can alter generated guidance.

## Best Practices

- Provide the real Xget base URL before requesting file or shell changes.
- Review changes to files that can contain credentials before committing them.
- Refresh the platform list before converting unfamiliar upstream URLs.

## Anti Patterns

- Using xget.example.com in live commands or production configuration.
- Applying persistent shell profile edits without confirming the target shell.
- Copying whole live README sections when one focused subsection is enough.

## Security Audit

- Audited at: 2026-07-08T10:17:22.015\+00:00
- Summary: Most script command-execution alerts are false positives from JavaScript template literals, and most placeholder URL alerts are benign documentation. Real risks remain because the skill fetches live remote guidance, encourages execution-first behavior, writes persistent shell profiles, and targets credential-bearing config files. Publication should require confirmation gates and stronger source-trust controls.

## Stats

- Views: 64
- Downloads: 13
- Favorites: 0
- Popularity score: 0