Skip to content
Back to skills

Gpu Allocation Fallback

ASecurity

Track typed GPU placement failures in the NPA agent and offer a consent-gated on-demand-to-preemptible fallback after repeated failures or deterministic preflight. Use when quota, capacity, Unschedulable GPU, or compatible-product placement blocks an allocation.

  • 33 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 8, 2026
testingpythonbashapibackend

Works with

  • cli
  • api

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned October 4, 2026

npx -y skills add nebius/nebius-physical-ai --skill gpu-allocation-fallback --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Gpu Allocation Fallback?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Gpu Allocation Fallback
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/nebius-gpu-allocation-fallback/badge)](https://www.skillsdirectory.com/skills/nebius-gpu-allocation-fallback)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: gpu-allocation-fallback
description: Track typed GPU placement failures in the NPA agent and offer a consent-gated on-demand-to-preemptible fallback after repeated failures or deterministic preflight. Use when quota, capacity, Unschedulable GPU, or compatible-product placement blocks an allocation.
---

# GPU Allocation Fallback

Send typed results to `POST /api/agent/gpu-allocation/attempt` with a stable
`logical_allocation`, the requested compatibility/execution/disk invariants,
typed failure evidence, and the identical compatible preemptible candidate.
The grounded route uses zero model tokens.

The optional `success` field must be a literal JSON boolean. Omitting it records
the attempt as unsuccessful, the same as `"success": false`; only
`"success": true` resets the tracked allocation as succeeded. Strings, numbers,
`null`, arrays, and objects are rejected with HTTP 400 without changing fallback
or confirmation-token state.

Only quota/capacity exhaustion, insufficient GPU or Unschedulable, and no
compatible product/affinity count. Auth, RBAC, network, image-pull, checkpoint,
application, runtime, cancellation, and timeout failures never count. The
default prompt occurs on the third qualifying failure, or immediately when
deterministic preflight proves on-demand cannot succeed and compatible
preemptible capacity is available.

Never switch automatically. Present the returned question and proposed action.
Accept through `POST /api/agent/gpu-allocation/consent` with its single-use,
action-digest-bound `confirm_token`; decline with `accept: false`. A decline
keeps on-demand and suppresses the same evidence until materially new evidence
arrives.

Preserve GPU family/product/count, image/digest, SM and RT-core requirements,
backend, model, workload tier, execution mode, and boot-disk count/bytes. The
state record contains only redacted digests, classification, selected pool, and
consent outcome. Success or a changed logical allocation resets attempt state.

Verify changes with:

```bash
npa/.venv/bin/python -m pytest \
  npa/tests/cli/test_agent_gpu_allocation_fallback.py \
  npa/tests/cli/test_agent_backend_render.py -q
```

Files in this skill

  • SKILL.md1.8 KB
  • agents/openai.yaml233 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.