Pre-install eval
cuda-to-xpu-migration Eval report.
A machine-readable install decision for agents: task fit, Trust Score, Audit Score, install safety, permission surface, and a concrete validation plan before this skill touches a workspace.
do not auto install
Trust score: Sparse or weak trust signals. Treat this as an experimental candidate.
Required gates
Checks an agent must pass before install
Task fit
94
Task wording matches this skill metadata.
- Evaluate cuda-to-xpu-migration before installing it in an agent workflow
- research
- Research agents workflows; Claude Code teams; builders willing to evaluate younger projects
Install path
92
Install handoff is available.
- npx skills add intel/gpu-ai-skills --skill cuda-to-xpu-migration
Install command safety
92
standard package or runtime install path
- npx skills add intel/gpu-ai-skills --skill cuda-to-xpu-migration
Trust score
56
Sparse or weak trust signals. Treat this as an experimental candidate.
- High review required
- 21 GitHub stars
- Apache-2.0
Audit score
66
Risky
- Dependency or permission surface needs review
Agent safety gate
22
This skill should not be selected by an agent without explicit human security review.
- Do not auto-install. Inspect the source, dependencies, and permission surface first.
- Audit risk exceeds the requested agent policy
License clarity
86
Apache-2.0
- Apache-2.0
Permission surface
18
secrets or environment access, shell or command execution
- Shell or command execution: high
- Network access: medium
- Filesystem access: medium
Validation plan
What the agent should do next
- 1Inspect repository, README/SKILL.md, license, and recent commits before production use.
- 2Install in an isolated workspace or sandbox with no production secrets available.
- 3Run the smallest representative task and record files touched, commands run, network access, and outputs.
- 4Compare the selected skill against at least one alternative when the eval status is review or failed.
- 5Promote only after the agent reports a successful verification result and unresolved warnings are accepted.
Do not use when
Conditions that require another skill
- teams that need a vendor-supported SLA
- production agents without a repository review
- Low GitHub adoption signal
- The skill references several sibling skills by name (xpu-port, torch-xpu-run, xpu-container-run, etc.) but does not document how an agent should discover, load, or confirm availability of those skills before routing to them.
- Audit risk risky exceeds max_risk=medium
- High-risk permission hints: Shell or command execution, Secrets or environment access
Supporting checks
Trust signals behind the decision
README/SKILL.md completeness
warn76
Public metadata needs stronger README/SKILL.md context
Recent maintenance
pass88
2mo since push
Alternatives available
pass82
Alternative skills are available for comparison.