Source profileQuality 85/100

NVIDIA-TAO/tao-skill-bank/templates/skill-skeleton/platform/SKILL.md

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).

Source repository stars
82
Declared platforms
0
Static risk flags
0
Last source update
2026-08-05
Source checked
2026-08-05
DecisionCompatibilityInstallWorkflowPermissionsEvidenceSource

Decision brief

What it does—and where it fits

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).

Best for

  • Use when the user asks to "deploy on REPLACE-PLATFORM", "run on REPLACE-PLATFORM", or mentions the platform's distinctive concepts (e.

Not for

  • Tasks that require unconfirmed production actions or broad system permissions.
  • Environments where the pinned source and install steps cannot be inspected.

Compatibility matrix

Platform support, with evidence labels

PlatformStatusEvidenceWhat to check
CodexNot declaredNo explicit evidencePortability before use
Claude CodeNot declaredNo explicit evidencePortability before use
CursorNot declaredNo explicit evidencePortability before use
Gemini CLINot declaredNo explicit evidencePortability before use
Open the compatibility checker

Installation

Inspect first. Install second.

The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

Source-detected install commandSource
npx skills add https://github.com/NVIDIA-TAO/tao-skill-bank --skill "templates/skill-skeleton/platform"
Safe inspection promptEditorial

Inspect the Agent Skill "REPLACE-WITH-PLATFORM-NAME" from https://github.com/NVIDIA-TAO/tao-skill-bank/blob/ae5e99c2148cf6bab95d150ee243a6da3f2c1fb1/templates/skill-skeleton/platform/SKILL.md at commit ae5e99c2148cf6bab95d150ee243a6da3f2c1fb1. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

Workflow

What the source asks the agent to do

  1. 01

    Quick start

    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…

    submit — stage inputs via tao-data-io, lint the command withstatus / logs — poll the native backend; map states to the fixed vocabcancel — native cancel + teardown, then mark ... --state CANCELED.
  2. 02

    Docker-native workflow

    Review the “Docker-native workflow” section in the pinned source before continuing.

    Review and apply the “Docker-native workflow” source section.
  3. 03

    External dependencies

    Review the “External dependencies” section in the pinned source before continuing.

    Review and apply the “External dependencies” source section.
  4. 04

    Authentication

    Review the “Authentication” section in the pinned source before continuing.

    Review and apply the “Authentication” source section.

Permission review

Static risk signals and limitations

No configured static risk pattern was detected

This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.

Evidence record

Why each signal appears

EvidenceSourceComputedTestedEditorial
SignalValueEvidence typeMeaning
Quality score85/100ComputedDocumentation, specificity, maintenance, and trust rules
Repository stars82SourceRepository attention, not individual Skill quality
Compatibility0 platformsSourceDeclared in the catalog source record
Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

Pinned source

Provenance and original SKILL.md

Repository
NVIDIA-TAO/tao-skill-bank
Skill path
templates/skill-skeleton/platform/SKILL.md
Commit
ae5e99c2148cf6bab95d150ee243a6da3f2c1fb1
License
Apache-2.0
Collected
2026-08-05
Default branch
main
View the original SKILL.md

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

DependencyPurposeInstall
<cli-name>Submit jobs / manage resources<install-command>

Authentication

MethodWhen to use
API token (recommended)Scripted / automated workflows
Browser loginInteractive development

Env vars:

Env varRequiredPurpose
<PLATFORM>_API_TOKENYes (or manual login)API auth

Preflight

# 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

<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

SymptomCauseFix
<error>......

Alternatives

Compare before choosing

Computed 97165

JasonColapietro/suede-creator-skills

suede-instagram-growth

Suede-owned Instagram growth operating system for account-specific audits, Reels, carousels, Stories, conversion mapping, calendars, and daily candidate-production loops. Use when the user names Instagram, IG, Reels, Stories, asks to analyze recent posts, grow a handle, run a daily workflow, create or repurpose Instagram content, or distinguish views from follows, leads, and sales. NOT FOR: multi-platform organic strategy (use suede-social), full video rendering or editing (use suede-video), pai

2026-08-050 platforms
Computed 9723

mission69b/t2000

sui-publish

Publishing, upgrading, and deploying Sui Move packages. Use this skill when the user needs to publish a package, upgrade a published package, deploy to multiple networks, serialize transactions for multisig signing, run a local Sui network (localnet), prepare for Mainnet launch, monitor production deployments, or debug dry run failures. Also use when the user asks about sui client publish, sui client upgrade, UpgradeCap, upgrade policies, Published.toml, --serialize-output, localnet, mainnet lau

2026-08-050 platforms
Computed 9715

eugenelim/agent-ready-repo

release-loop

Use to drive the deployed end-to-end validation outer loop — deploy the integrated whole to an ephemeral environment, run e2e, observe telemetry, feed deployed findings back to work-loop's inner loop, redeploy, and iterate until the deployed whole converges, then stop at the human consent gate for the prod ship. Run by the release-lead agent (a peer of work-loop's supervisor, not a work-loop mode). Triggers on "run the release loop", "deploy the integrated whole and iterate", "ship it to an ephe

2026-08-050 platforms
Computed 9647,530

prisma/prisma

prisma-8-migration-review

Review what Prisma Next migrations will run on merge or deploy, render the migration graph, resolve concurrent / diamond-convergence conflicts, and configure environment refs for CI. Use for "what migrations are going to run", "what runs on deploy", merge conflict, diamond convergence, concurrent migrations, migration status, ref management, staging, production, MIGRATION.DIVERGED, MIGRATION.NO_MARKER, MIGRATION.MARKER_NOT_IN_HISTORY, prisma migrate status, prisma migrate diff, prisma migrate re

2026-08-050 platforms