REPLACE-WITH-PLATFORM-NAME
/REPLACE-WITH-PLATFORM-NAME
Where and how GPU jobs run on this platform. One-to-three-sentence summary. Use when the user asks to "deploy on REPLACE-PLATFORM", "run on REPLACE-PLATFORM", or mentions the platform's distinctive concepts (e.g., resource shape, instance, node group).
- Author
- nvidia-tao ↗
- Repository
- tao-skill-bank ↗
- Licence
- Apache-2.0
- Last repository change
- 22.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 22.10.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Where and how GPU jobs run on this platform. One-to-three-sentence summary. Use when the user asks to "deploy on REPLACE-PLATFORM", "run on REPLACE-PLATFORM", or mentions the platform's distinctive concepts (e.g., resource shape, instance, node group).
Triggers from the description
Original author description
Where and how GPU jobs run on this platform. One-to-three-sentence summary. Use when the user asks to "deploy on REPLACE-PLATFORM", "run on REPLACE-PLATFORM", or mentions the platform's distinctive concepts (e.g., resource shape, instance, node group).
How it works
- External dependencies
- Authentication
- Preflight
- Quick start
- Platform-specific notes
- Known pitfalls
SKILL.md preview
--- name: REPLACE-WITH-PLATFORM-NAME description: >- Where and how GPU jobs run on this platform. One-to-three-sentence summary. Use when the user asks to "deploy on REPLACE-PLATFORM", "run on REPLACE-PLATFORM", or mentions the platform's distinctive concepts (e.g., resource shape, instance, node group). license: Apache-2.0 compatibility: REPLACE — examples — `Requires the brev CLI and an active brev login.` or `Requires kubectl configured against a GPU cluster and <PLATFORM>_API_TOKEN.` metadata: author: REPLACE-WITH-AUTHOR-NAME version: "0.1.0" allowed-tools: Read Bash --- # Platform Name > **Standalone install?** If this session was not initialized by the TAO skill bank plugin, run the `tao-setup` skill first (host preflight, credentials, cross-skill discovery). Short summary of the platform's execution model. Instance-based or job-based? API-first or docker-first? Single-node or multi-node? Managed or self-hosted? For generic docker conventions, defer to `tao-skill-bank:tao-run-on-docker`. This skill covers the platform-specific layering on top. ## External dependencies | Dependency | Purpose | Install | |---|---|---| | `<cli-name>` | Submit jobs / manage resources | `<install-command>` | ## Authentication | Method | When to use | |---|---| | API token (recommended) | Scripted / automated workflows | | Browser login | Interactive development | Env vars: | Env var | Required | Purpose | |---|---|---| | `<PLATFORM>_API_TOKEN` | Yes (or manual login) | API auth | ## Preflight ```bash # 1. CLI installed which <cli-name> || echo "MISSING: install from <url>" # 2. Logged in <cli-name> ls >/dev/null 2>&1 || echo "NOT LOGGED IN" # 3. Platform-specific checks ``` ## Quick start ### Docker-native workflow ```bash <platform-cli> exec <target> -- docker run --gpus all --rm \ -e <env-vars> \ -v <host-path>:<container-path> \ nvcr.io/... \ <command> ``` ### Execution — the four verbs A platform skill is a **consumer**: it runs a model/data skill's spec-bundle by implementing `submit`/`status`/`logs`/`cancel` over the native CLI, mutating only the job-record. No SDK. See `tao-skill-bank:tao-launch-workflow` for the shared contract and `tao-skill-bank:tao-run-on-docker` for a worked example. - **submit** — stage inputs via `tao-data-io`, lint the command with `redact_secrets.py`, then `tao_job_record.py open` (mints the id + binds `results_dir` *before* launch), launch naming the backend object after the id, and `mark ... --state RUNNING`. - **status / logs** — poll the native backend; map states to the fixed vocab `PENDING RUNNING COMPLETE ERROR CANCELED UNKNOWN`. - **cancel** — native cancel + teardown, then `mark ... --state CANCELED`. ## Platform-specific notes - Storage model (shared NFS/Lustre? S3 only? instance-local?) - Pricing / lifecycle considerations - Known limitations ## Known pitfalls | Symptom | Cause | Fix | |---|---|---| | `<error>` | ... | ... |
Versions
The database has no other skills named REPLACE-WITH-PLATFORM-NAME.
Database snapshot: 13.11.2026 · package version c1569c7a445c (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90REPLACE-WITH-SKILL-NAME
One-to-three-sentence description of what the model does and when to use it. Use when the user asks to "fine-tune REPLACE-WITH-NETWORK", "train REPLACE-WITH-NETWORK on REPLACE-WITH-DATA-TYPE", or mentions REPLACE-WITH-DOMAIN-TERMS. Include literal trigger phrases. - 90REPLACE-WITH-SKILL-NAME
One-to-three-sentence description of what this data transformation does. Use when the user asks to "REPLACE-WITH-INTENT", or mentions REPLACE-WITH-DOMAIN-TERMS. Include literal trigger phrases the user is likely to say. - 95qzcli
Manage GPU compute jobs on the Qizhi (Xinji!) platform using qzcli — a kubectl-style CLI tool. Use when user says "qzcli", "Platform for enlightenment", "submit job", "stop job", "Check Calculator", "avail", "list jobs", "batch submit", or needs to manage distributed training… - 100gpu-resource-optimizer
Optimize gpu resource optimizer operations. Auto-activating skill for ML Deployment. Triggers on: gpu resource optimizer, gpu resource optimizer Part of the ML Deployment skill category. Use when working with gpu resource optimizer functionality. Trigger with phrases like "gpu… - 95modal-serverless-gpu
Serverless GPU cloud platform for running ML workloads. Use when you need on-demand GPU access without infrastructure management, deploying ML models as APIs, or running batch jobs with automatic scaling. - 84modal
Serverless GPU cloud platform for running ML workloads. Use when you need on-demand GPU access without infrastructure management, deploying ML models as APIs, or running batch jobs with automatic scaling.