xpu-port SKILL.md skillA
xpu-port from intel/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add intel/skills/xpu-port@git:20260903.b1ad034Pins git:20260903.b1ad034 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- intel/skills
- Path
skills/xpu-port/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260903.b1ad034, committed Sep 3, 2026
- Size
- 9,620 bytes
- Repository stars
- 29
- License
- Apache-2.0
Execute a single-target CUDA-to-XPU port of a PyTorch repo with libcst-based scan, mechanical rewrite, and CPU FP64 vs target-dtype correctness verify on one forward pass. Use when the request says "port" — "port my repo to XPU", "port my repo at <path> to XPU", "rewrite the CUDA calls to XPU", "apply the mechanical transforms", "run the scan and rewrite", "make the port changes now". Not for the "migrate" verb ("migrate my repo", "migrate this repo to XPU") or a bare whole-repo workflow…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# xpu-port
Three deterministic scripts; the agent drives the loop.
```
scripts/
├── xpu_port_scan.py # libcst, classifies sites mechanical/semantic/escalate
├── xpu_port_rewrite.py # libcst, named transforms, --check previews diff
└── xpu_port_verify.py # CPU FP64 reference vs target dtype, one forward
```
```sh
pip install libcst
```
## Targets
**Single-target XPU only.** After the port, the codebase runs on
Intel XPU. CUDA call sites are rewritten, not dual-gated. If the
user wants both CUDA and XPU at runtime (dual-target), stop and
say so — that's a different problem (per-call-site guards,
device-aware factories) and this skill produces broken
half-ported code if used for it.
## Backstop — wrong entry point
This skill executes; it does not assess or route. One redirect
exists, pointing one way. If the request is really an assessment
or a whole-repo migration ("migrate this repo", "what would it
take to run on XPU" — scope not yet set), hand it to
**cuda-to-xpu-migration** and stop; its report's Next steps lead
back here for the Python surface.
The same backstop covers mis-scoped ports. This skill reads
…Read the whole file at its exact version.
How to install
mdr add intel/skills/xpu-port@sha256:9a302ca94299c57fThe line at the top of this page pins the label git:20260903.b1ad034, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_d5wfxwypazzyxegl)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Sep 3, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (9620 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
intel/skills · 29 stars · license Apache-2.0 · pushed 2026-11-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_d5wfxwypazzyxegl GET https://markdownregistry.com/api/v1/resolve?ref=intel/skills/xpu-port GET https://markdownregistry.com/api/v1/blob/9a302ca94299c57f881d96a866b1c549bf1916025edb72bc15672bceb6fd9434
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.