CtrlK
BlogDocsLog inGet started
Tessl Logo

physical-ai-infrastructure-setup-and-resilient-scaling

Use when the user wants to set up, scale, validate, or harden NVIDIA physical AI infrastructure for synthetic data generation workflows across local MicroK8s or Azure AKS, including Kubernetes clusters, inference endpoint deployment, OSMO deployment, workload submission readiness, and infrastructure failure recovery. Trigger keywords: physical ai infrastructure, resilient scaling, SDG infrastructure, microk8s, azure aks, NVCF deployment, NIM Operator, OSMO deploy, workflow scaling. Don't trigger for: OSMO log summarization or workload-only operations unless infrastructure setup, scaling, validation, or recovery is requested.

77

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

The canonical home for this skill is physical-ai-infrastructure-setup-and-resilient-scaling in NVIDIA/skills

SKILL.md
Quality
Evals
Security

Quality

Content

100%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a tight, table-driven overview that respects Claude's intelligence, gives executable commands and exact paths, sequences a multi-stage deploy with explicit validation gates and retry discipline, and pushes detail one level deep into well-signaled component references. The only caveat is that the referenced component bundle files are not present on disk to verify.

DimensionReasoningScore

Conciseness

Lean, table-driven body with no explainer prose about what Kubernetes/OSMO/PDF-style concepts are; every section assumes Claude's competence and earns its tokens. Not the level-2 case because there is no padded library/format explanation.

3 / 3

Actionability

Concrete executable references throughout: 'scripts/preflight.sh', 'preflight_credentials.sh', 'pre_submit_guard.py with resolved --set values', 'osmo workflow query <id>', NIM '/v1/health/ready' readiness, and exact component paths. Copy-paste-ready guidance, not pseudocode.

3 / 3

Workflow Clarity

Setup flow is an explicit 8-step sequence with hard gates ('stop on red preflight', 'Nothing else starts until the cluster gate is green'), a mandatory Verification Gates table, and feedback loops for failures ('do not resubmit blindly', investigate scheduling/storage/credentials 'before retry'). Not level 2 because validation checkpoints are explicit and wired into error recovery.

3 / 3

Progressive Disclosure

SKILL.md is an overview pointing one level deep to components/*/reference.md via a concern→Load→Assets table, with second-level OSMO CLI support files in a separate 'Read when' table — clearly signaled and well-organized. Note: the referenced components/ bundles are not present on disk alongside the skill, so file existence could not be verified, but the disclosure structure itself is exemplary.

3 / 3

Total

12

/

12

Passed

Description

100%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is concise yet comprehensive: third person, concrete actions across named NVIDIA/SDG stack components, explicit 'Use when' triggers, an enumerated keyword list, and a negative trigger for disambiguation. It hits every anchor at the top of the scale.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('set up, scale, validate, or harden') across named subsystems (MicroK8s, Azure AKS, inference endpoints, OSMO), matching the anchor for listing multiple specific concrete actions.

3 / 3

Completeness

Opens with 'Use when the user wants to set up, scale, validate, or harden…' (what+when) and adds an explicit 'Don't trigger for: OSMO log summarization or workload-only operations…' exclusion, clearly answering both what and when.

3 / 3

Trigger Term Quality

Explicit 'Trigger keywords: physical ai infrastructure, resilient scaling, SDG infrastructure, microk8s, azure aks, NVCF deployment, NIM Operator, OSMO deploy, workflow scaling' gives strong natural-term coverage a user would actually say.

3 / 3

Distinctiveness Conflict Risk

The explicit negative trigger ('Don't trigger for: OSMO log summarization… unless infrastructure setup, scaling, validation, or recovery is requested') carves a clear niche unlikely to fire for adjacent OSMO/workload skills.

3 / 3

Total

12

/

12

Passed

Validation

75%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation12 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

12

/

16

Passed

Repository
openai/plugins
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.