Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Skill from xixu-me/skills
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-17 | ✗→✓ | ▲ Improved | — | — |
| case-06 | ✗→✗ | ＝ Same ✗ | — | — |
| case-09 | ✗→✗ | ＝ Same ✗ | — | — |
| case-11 | ✗→✗ | ＝ Same ✗ | — | — |
| case-16 | ✗→✗ | ＝ Same ✗ | — | — |
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:
XGET_BASE_URL from the environmentset temporarily for the current shell/session or persistently for future shells
https://xget.example.com only as a clearly labeled placeholder for docsor 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.
applied now
template without applying it yet
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
XGET_BASE_URL, open the reference guide and:
temporary or persistent commands directly when the environment allows it
the exact command with the missing value clearly called out
by default:
node scripts/xget.mjs topics --format json--match or fetch a specific section withnode scripts/xget.mjs snippet --base-url https://xget.example.com --heading "Docker Compose Configuration" --format text
like Use in Project is ambiguous, fetch its parent section instead.
example commands
switch, migrate, test, or otherwise perform the change
not just explanation
rewrite
verification step when practical
node scripts/xget.mjs platforms --format json when the answer depends on current prefixes, and use convert for exact URL rewrites.
example, pair a package-manager section with container, deployment, or .env guidance when the user's project needs more than one integration point.
the right Xget path shape:
/{prefix}/.../crates/... rather than /crates/api/v1/crates/.../ip/{provider}/.../cr/{registry}/...platform, say so explicitly and fall back to the stable guidance in references/REFERENCE.md instead of inventing a prefix.
| Case | Status | Duration (ms) | Turns | Tokens | Tool calls | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Without | With | Δ | Without | With | Δ | Without | With | Δ | Without | With | Δ | ||
case-06 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-09 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-11 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-16 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-18 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-01 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-13 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-12 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-02 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-04 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-21 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-08 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-10 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-14 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-22 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-19 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-17 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-15 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-07 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-03 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-05 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-20 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
DecimalAI ran this skill against gemini-3.6-flash twice over the same eval suite — once with the skill loaded and once without — and compared the two runs case by case. 22 cases were attempted, and 2 counted toward the lift figure. The other 20 produced results that are not comparable between the two arms, so they are excluded from the headline rather than averaged into it. The headline lift of +5 percentage points is the difference between those two pass rates over the 2 comparable cases. 8 cases got worse with the skill loaded, and they are included in that figure.
The per-case answers from this run were removed by the retention sweep, so the case table below shows the verdicts without the text either arm produced. The counts above were recorded at the time and are unaffected. Answers are now kept for 180 days.
Other measured skills in the registry, with their headline benchmark lift.