physical-ai-defect-image-generation

Orchestrate end-to-end defect-image generation pipelines for AOI datasets using NVIDIA OSMO.

Updated May 29, 2026
One-click install
npx skills add https://github.com/rblake2320/vigil --skill physical-ai-defect-image-generation-rblake2320
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: physical-ai-defect-image-generation
Source: https://github.com/rblake2320/vigil/tree/main/.claude/skills/physical-ai-defect-image-generation
Command: npx skills add https://github.com/rblake2320/vigil --skill physical-ai-defect-image-generation-rblake2320

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires osmo, jq, curl, wget, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This skill orchestrates end-to-end defect-image generation workflows for AOI datasets using NVIDIA OSMO, enabling deterministic coordination of data ingestion, rendering, augmentation, and anomaly labeling across multiple use-cases and flows.

Core Features & Use Cases

It supports Day 0 texture defects, Day 0 good-image generation, Day 0 structural defects, Day 1 real-photo alignment, Day 1 manual ROI, and Finetune options, covering PCBA, metal surface, and glass use-cases with a unified orchestration layer. It coordinates multiple components (usd2roi, image-edit, anomalygen) and per-board cookbooks, enabling scalable pipeline execution, artifact management, and output organization under a single OSMO root.

Quick Start

Submit the Day 0 texture_defect_generation.yaml with the required dig_url_root, board, image_edit_endpoint, and anomaly_types_json to start an end-to-end defect-image workflow.

Frequently Asked Questions about physical-ai-defect-image-generation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate defect-image generation pipelines for PCB AOI datasets?

Automate defect-image generation pipelines for PCB AOI datasets by orchestrating end-to-end workflows with NVIDIA OSMO, coordinating data ingestion, rendering, augmentation, and labeling deterministically across multiple flows.

What is the difference between Day 0 and Day 1 flows in AI defect-image generation?

Day 0 flows in AI defect-image generation cover texture defects, good images, and structural defects, while Day 1 flows handle real-photo alignment and manual ROI operations for refined anomaly labeling.

Does OSMO defect-image orchestration support use cases beyond PCBA?

OSMO defect-image orchestration supports PCBA, metal surface, and glass use cases, applying unified pipeline execution and artifact management across these distinct anomaly generation workflows.

How do I submit a Day 0 texture defect generation workflow using OSMO?

Submit the Day 0 texture_defect_generation.yaml file with required parameters including dig_url_root, board, image_edit_endpoint, and anomaly_types_json to start the end-to-end OSMO workflow.

What prerequisites are needed to run an OSMO anomaly generation pipeline?

Running an OSMO anomaly generation pipeline requires preflight checks for credentials, pod template, and URL artifacts, along with memory stamping and explicit osmo submit knobs for deterministic outputs.

Can I coordinate multiple components like image-edit and anomalygen in a single defect-image pipeline?

Coordinate multiple components including usd2roi, image-edit, and anomalygen alongside per-board cookbooks in a single defect-image pipeline to enable scalable execution and organized output under a designated OSMO root.