Creator · NVIDIA
Last updated · Sep 2, 2026
Launch AutoMagicCalib microservice and web UI from NGC release images via Docker Compose. Use when user says 'deploy auto calibration', 'launch auto calibration', 'launch AMC', 'start MS+UI', or 'set up auto-magic-calib'. Requires NGC API key.
Sandbox only
Install targets
Codex install prompt
Install the "amc-setup-calibration-stack" agent skill from https://github.com/NVIDIA/skills/tree/main/skills/amc-setup-calibration-stack. Read its SKILL.md or equivalent instructions first, install only the files needed for this workspace, and summarize any required setup before using it. Skill purpose: Launch AutoMagicCalib microservice and web UI from NGC release images via Docker Compose. Use when user says 'deploy auto calibration', 'launch auto calibration', 'launch AMC', 'start MS+UI', or 'set up auto-magic-calib'. Requires NGC API key. After the install attempt, report the result to https://www.openagentskill.com/api/agent/outcome with POST JSON {"event_id":"install_<unique-id>","skill_slug":"nvidia-amc-setup-calibration-stack","task":"Install amc-setup-calibration-stack","agent":"codex","outcome":"success","install_used":true}. Replace event_id with a unique value and outcome with success or failed. Report success only after the skill is installed and a minimal verification passes.Supply asset profile
Code review, repo analysis, testing, CI, GitHub, DevOps, and developer workflow skills.
Scenario
GitHub automation
I need my agent to triage GitHub issues, review pull requests, and summarize repository changes.
Agent fit
Claude Code + Browser agents + CLI
Codex, Claude Code, Cursor, CLI, or custom agents.
Install
Ready
npx skills add NVIDIA/skills --skill amc-setup-calibration-stack
Maintenance
fresh
6d since push
Risk
Needs review
Dependency or permission surface needs review
GitHub quality
3.2K
82/100 Quality · 76/100 Trust
Coverage tags
Review notes
Dependency or permission surface needs review · Permission surface may require sandboxing
Agent adoption scorecard
These scores combine public repository metadata, OpenAgentSkill review signals, maintenance freshness, and install readiness. They are a shortlist signal, not a replacement for human review.
Quality
StrongSolid option that is likely worth shortlisting for production workflows.
Trust
Sandbox onlyUseful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.
Audit
Needs reviewA machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
OpenAgentSkill Trust Score v5
Run only in a sandbox and compare close alternatives before using it for real work.
Stars
3.2K GitHub stars
Repo activity
3.2K stars, 370 forks
Maintenance
6d since push
License
Apache-2.0
Install
npx skills add NVIDIA/skills --skill amc-setup-calibration-stack
Install safety
Agent-readable metadata
Use this block or the embedded JSON to decide whether an agent should install this skill, choose an alternative, or ask for human review first.
Suited tasks
Suited agents
Install decision
Trust and risk
Outcome loop
Install command
npx skills add NVIDIA/skills --skill amc-setup-calibration-stackDo not use when
Alternative
175.1K Stars
npx skills add anthropics/skills --skill frontend-design
Alternative
85.2K Stars
npx skills add Leonxlnx/taste-skill --skill design-taste-frontend
Alternative
1.8K Stars
npx skills add Alisa0808/vox-director --skill vox-director
Alternative
175.1K Stars
npx skills add anthropics/skills --skill canvas-design
Agent safety v2
Sparse or mixed signals. Useful for discovery, but not for autonomous installation.
Test manually in an isolated workspace and compare against safer alternatives.
high
Skill metadata references terminal, CLI, shell, subprocess, or command execution workflows.
medium
Skill may drive a browser or interact with web pages.
medium
Skill likely fetches remote pages, APIs, repositories, or external services.
medium
Skill may read or write project files, documents, generated artifacts, or local workspace state.
Agent resolve plan
The Resolve API returns the selected skill, alternatives, safety policy, audit notes, install target, and copy-paste prompt an agent can follow without scraping this page.
Open JSON
/api/agent/resolve?task=Use%20amc-setup-calibration-stack%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Resolve text
/api/agent/resolve?task=Use%20amc-setup-calibration-stack%20for%20an%20agent%20workflow&agent=codex&max_risk=medium&format=text
Install handoff
/api/skills/nvidia-amc-setup-calibration-stack/install
Agent should check
Copy prompt
Task: Use amc-setup-calibration-stack in this workspace.
Resolve first: https://www.openagentskill.com/api/agent/resolve?task=Use%20amc-setup-calibration-stack%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Review install handoff: https://www.openagentskill.com/api/skills/nvidia-amc-setup-calibration-stack/install
Install command: npx skills add NVIDIA/skills --skill amc-setup-calibration-stack
Before running it, summarize audit warnings, required permissions, and the fallback skill if install is risky.Agent handoff
Use the public install endpoint to fetch the command, safety checklist, target prompts, and canonical links for this skill.
Install handoff
/api/skills/nvidia-amc-setup-calibration-stack/install
LLM text format
/api/skills/nvidia-amc-setup-calibration-stack/install?format=text
Find alternatives
/api/skills/search?q=amc-setup-calibration-stack&limit=3
Agent prompt
Use amc-setup-calibration-stack for this task. Review https://www.openagentskill.com/api/skills/nvidia-amc-setup-calibration-stack/install, then install with: npx skills add NVIDIA/skills --skill amc-setup-calibration-stackRegistry metadata
This page exposes the same decision, trust, audit, use-case, and install signals through the Registry API, so agents can rank this skill without scraping the UI.
Manifest
/api/registry/manifest/nvidia-amc-setup-calibration-stack
LLM text
/api/registry/manifest/nvidia-amc-setup-calibration-stack?format=text
Install alias
/api/registry/install/nvidia-amc-setup-calibration-stack
Recommend
/api/registry/recommend?task=Use%20amc-setup-calibration-stack%20in%20an%20agent%20workflow&limit=3
Agent fit
GitHub automation
Use-case tags
Platforms
Claude Code, Browser agents
Audit report
A machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
Agent decision cockpit
Use this as a leading candidate, then validate the README and install path in your own agent stack.
Role in stack
Primary pick
Primary fit
GitHub automation
Trust label
Production-ready
Install path
Command ready
Use when
Evidence
review first
Implementation path
Trust profile
Useful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.
GitHub adoption
PASS3.2K GitHub stars
Stars/forks activity
PASS3.2K stars, 370 forks; issue activity unavailable in current metadata
Recent maintenance
PASS6d since push
License clarity
PASSApache-2.0
Good signals
Review before install
Recommended action
Run only in a sandbox and compare close alternatives before using it for real work.
Quality profile
Solid option that is likely worth shortlisting for production workflows.
Workflow fit
Manage repositories
I need my agent to triage GitHub issues, review pull requests, and summarize repository changes.
Build and ship code
I need a coding agent that can understand a repository, edit code, and review pull requests.
Operate web apps
I need my agent to control a browser, fill forms, and verify web app workflows.
Workflow fit
Inspect, patch, and verify code
A workflow for software agents that inspect repositories, review pull requests, generate tests, and turn findings into shippable patches.
Design, build, test, and ship interfaces
A practical workflow for agents that turn product briefs or Figma designs into polished frontend code, review the result, test it in a browser, and prepare a safe deployment.
Scrape, clean, and reuse web data
A practical workflow for agents that crawl public pages, extract clean content, normalize data, and hand it to downstream research or RAG workflows.
Alternative shortlist
Similar skills that may fit this task.
Guidance for distinctive, intentional UI design, typography, visual direction, and non-template-like product interfaces.
Design and implementation guidance for distinctive landing pages, portfolios, product demos, and purposeful redesigns.
Turn one topic into a narrated Vox-style paper-collage explainer or ad video, from script through captions.
Create original visual art, posters, PNG assets, and PDF documents through a clear design philosophy.
--- name: "amc-setup-calibration-stack" description: "Launch AutoMagicCalib microservice and web UI from NGC release images via Docker Compose. Use when user says 'deploy auto calibration', 'launch auto calibration', 'launch AMC', 'start MS+UI', or 'set up auto-magic-calib'. Requires NGC API key." metadata: author: "NVIDIA CORPORATION" tags: [amc, deepstream, docker, calibration, setup, ngc] owner: "NVIDIA CORPORATION" service: "auto-magic-calib" version: "1.0.0" reviewed: "2026-04-28" license: "Apache-2.0" ---
# Skill: Launch AutoMagicCalib Release Containers
Set up the AutoMagicCalib microservice and UI from release containers: resolve an AMC checkout, authenticate to NGC, optionally download VGGT, configure Docker Compose, launch services, and verify readiness.
## Prerequisites - Docker and Docker Compose installed - NVIDIA Docker Runtime configured (for GPU support) - `auto-magic-calib` repo on disk. Step 0b resolves the current repo, DeepStream `tools/auto-magic-calib`, `DEEPSTREAM_REPO_ROOT`, or `~/auto-magic-calib`; otherwise it asks before cloning `https://github.com/NVIDIA-AI-IOT/auto-magic-calib`. - NGC account with access to NVIDIA container registry - Docker runnable without `sudo`; verify with `docker ps` before continuing.
## Instructions
### Step 0: Verify Docker Runs Without sudo
```bash docker ps ```
- If it succeeds → continue. - If it fails with "permission denied" → the user is not in the `docker` group. Ask the user to run: ```bash sudo usermod -aG docker $USER && newgrp docker ``` Then ask the user to confirm `docker ps` works before continuing.
> **Agent note**: If `docker ps` cannot be run from within the agent sandbox, ask the user to confirm it works (e.g. "Can you confirm `docker ps` runs without sudo?") before proceeding.
### Step 0b: Resolve Repo Checkout
The skill needs AMC repo assets (`compose/`, sample data, and `models/`). Resolve an existing checkout first; ask before cloning into `~/auto-magic-calib`.
```bash REPO_URL="https://github.com/NVIDIA-AI-IOT/auto-magic-calib.git" DEFAULT_CLONE_DIR="$HOME/auto-magic-calib" CURRENT_GIT_ROOT="$(git rev-parse --show-toplevel 2>/dev/null || true)"
is_amc_checkout() { [ -n "$1" ] \ && [ -f "$1/README.md" ] \ && grep -q "AutoMagicCalib" "$1/README.md" 2>/dev/null \ && [ -f "$1/compose/compose.yml" ] \ && grep -q "auto-magic-calib-ms" "$1/compose/ms/compose.yml" 2>/dev/null \ && grep -q "auto-magic-calib-ui" "$1/compose/ui/compose.yml" 2>/dev/null }
REPO_ROOT="" for candidate in \ "$CURRENT_GIT_ROOT" \ "${CURRENT_GIT_ROOT:+$CURRENT_GIT_ROOT/tools/auto-magic-calib}" \ "${DEEPSTREAM_REPO_ROOT:+$DEEPSTREAM_REPO_ROOT/tools/auto-magic-calib}" \ "$PWD/tools/auto-magic-calib" \ "$DEFAULT_CLONE_DIR"; do if is_amc_checkout "$candidate"; then REPO_ROOT="$candidate" echo "✓ Using auto-magic-calib checkout: $REPO_ROOT" break fi done
if [ -z "$REPO_ROOT" ]; then if [ -n "$CURRENT_GIT_ROOT" ] && [ -d "$CURRENT_GIT_ROOT/tools/auto-magic-calib" ]; then echo "Found $CURRENT_GIT_ROOT/tools/auto-magic-calib, but it is not an initialized AMC checkout." echo "If running from the DeepStream repository root:" echo " git submodule update --init tools/auto-magic-calib" fi
# Nothing usable on disk — STOP and ask the user for confirmation using the # host's question mechanism; if none is available, ask in chat and wait. # Do NOT clone silently from this block or clone over a tracked submodule path. echo "No usable auto-magic-calib checkout found. Ask the user for confirmation:" echo " Clone $REPO_URL into $DEFAULT_CLONE_DIR? [y/N]" echo "On 'y' — run: git clone \"$REPO_URL\" \"$DEFAULT_CLONE_DIR\"" exit 1 fi
cd "$REPO_ROOT" export REPO_ROOT echo "REPO_ROOT=$REPO_ROOT" ```
> **Agent note**: never clone silently. Prefer initialized DeepStream `tools/auto-magic-calib`; do not clone over that submodule path. If it exists but is empty, ask the user to run `git submodule update --init tools/auto-magic-calib`. Honour an alternate AMC path if provided.
### Step 0c: Install Python venv (New Systems Only)
On a fresh system, `pip` and `python3-venv` may not be available. Install them first:
```bash # Create a venv for HuggingFace CLI (project-local preferred) REPO_DIR="$(git rev-parse --show-toplevel 2>/dev/null || pwd)" HF_VENV="${REPO_DIR}/venv" python3 -m venv "$HF_VENV" 2>/dev/null || { echo "ERROR: python3-venv not available." >&2 echo "Install it manually: sudo apt install -y python3-venv python3-pip" >&2 exit 1 }
# Install HuggingFace hub (needed for VGGT download) "$HF_VENV/bin/pip" install --upgrade pip huggingface_hub ```
> **Note**: Skip this step if a venv with `hf` already exists (check `venv/bin/hf` in the repo root or `~/venv/amc/bin/hf`).
### Step 1: Login to NGC
Ask the user for their NGC API key using the host's question mechanism; if none is available, ask in chat and wait. Then run:
```bash echo "<NGC_API_KEY>" | docker login nvcr.io --username '$oauthtoken' --password-stdin echo "✓ NGC authentication complete" ```
### Step 2: Download VGGT Model (If Not Already Present)
```bash export REPO_ROOT=$(git rev-parse --show-toplevel) cd "$REPO_ROOT"
if [ -f "models/vggt/vggt_1B_commercial.pt" ]; then echo "✓ VGGT model already present" else echo "✗ VGGT model not found" echo "Options:" echo " 1. Continue without VGGT (AMC only - sufficient for most use cases)" echo " 2. Download VGGT model (~4.7GB, requires HuggingFace account)" fi ```
**To download VGGT**: ask the user to accept the license at https://huggingface.co/facebook/VGGT-1B-Commercial and provide a read token from https://huggingface.co/settings/tokens using the host's question mechanism. Pass it through `HF_TOKEN` so it is not exposed in `ps` output: ```bash REPO_DIR="$(git rev-parse --show-toplevel 2>/dev/null || pwd)" cd "$REPO_DIR"
# Find the HuggingFace CLI binary (named 'hf', not 'huggingface-cli') HF_BIN="$(find "$REPO_DIR/venv" ~/venv/amc -name hf -type f 2>/dev/null | head -1)" { [ -z "$HF_BIN" ] || [ ! -x "$HF_BIN" ]; } && { echo "ERROR: hf binary not found or not executable; install the hf CLI (Step 0c) or set HF_BIN" >&2; exit 1; }
# Do NOT use --token on the command line (leaks via ps/argv). The HF CLI # reads HF_TOKEN from the environment automatically. HF_TOKEN="<HF_TOKEN>" "$HF_BIN" download facebook/VGGT-1B-Commercial \ --local-dir models/vggt/
# Verify ls -lh models/vggt/vggt_1B_commercial.pt # Should show ~4.7GB file ```
> **Important**: Download BEFORE setting `chown 1000:1000` on the models directory — the current user needs write access during download. Set permissions in Step 4 after download completes.
### Step 3: Configure Compose Environment Variables
The Compose environment file controls ports and paths. Update it before launching:
```bash cd $REPO_ROOT/compose
# Find available backend port (8000-8009) for port in {8000..8009}; do if ! lsof -Pi :$port -sTCP:LISTEN -t >/dev/null 2>&1; then MS_PORT=$port echo "Using backend port: $MS_PORT" break fi done [ -z "$MS_PORT" ] && { echo "ERROR: no free backend port in 8000-8009; free one or widen the range." >&2; exit 1; }
# Find available UI port (5000-5009) for port in {5000..5009}; do if ! lsof -Pi :$port -sTCP:LISTEN -t >/dev/null 2>&1; then UI_PORT=$port echo "Using UI port: $UI_PORT" break fi done [ -z "$UI_PORT" ] && { echo "ERROR: no free UI port in 5000-5009; free one or widen the range." >&2; exit 1; }
# Get host IP HOST_IP=$(hostname -I | awk '{print $1}') echo "Host IP: $HOST_IP"
# Preserve existing keys and restrict permissions on the Compose environment file. COMPOSE_ENV_BASENAME="env" ENV_FILE=".${COMPOSE_ENV_BASENAME}" if [ -f "$ENV_FILE" ]; then BACKUP="${ENV_FILE}.bak.$(date +%s)" cp "$ENV_FILE" "$BACKUP" chmod 600 "$BACKUP" fi touch "$ENV_FILE" chmod 600 "$ENV_FILE" set_env_key() { local k="$1" v="$2" if grep -qE "^${k}=" "$ENV_FILE"; then sed -i "s|^${k}=.*|${k}=${v}|" "$ENV_FILE" else echo "${k}=${v}" >> "$ENV_FILE" fi } set_env_key AUTO_MAGIC_CALIB_MS_PORT "${MS_PORT}" set_env_key AUTO_MAGIC_CALIB_UI_PORT "${UI_PORT}" set_env_key PROJECT_DIR "../../projects" set_env_key MODEL_DIR "../../models" set_env_key HOST_IP "${HOST_IP}"
# Keep timestamped Compose environment backups out of git. GITIGNORE="$REPO_ROOT/.gitignore" touch "$GITIGNORE" BACKUP_PATTERN="compose/${ENV_FILE}.bak.*" grep -qxF "$BACKUP_PATTERN" "$GITIGNORE" || echo "$BACKUP_PATTERN" >> "$GITIGNORE"
echo "✓ Compose environment file updated" cat "$ENV_FILE" ```
**Important**: `HOST_IP` must be the machine's network IP (not `localhost`) so the UI container can reach the backend from a browser.
Optional: set `VGGT_MODEL_PATH` only if the VGGT model is mounted at a non-default container path; default is `/tmp/vggt_model/vggt_1B_commercial.pt` inside the MS container.
Optional for RTSP calibration: use `skills/amc-run-rtsp-calibration/SKILL.md` after launch. That skill verifies VIOS reachability and, when needed, relaunches the microservice with a temporary compose override that exports `VIOS_BASE_URL` without changing checked-in compose files.
### Step 4: Set Directory Permissions
The containers run as UID/GID 1000. The `projects` and `models` directories must be owned by this UID for containers to read/write properly:
```bash cd "$REPO_ROOT"
# Create projects directory if it doesn't exist mkdir -p projects
# Set ownership (required for containers to write calibration outputs). # Do this AFTER VGGT download is complete (current user needs write access during download). # Get explicit user confirmation before running sudo chown — it recursively changes # ownership of $REPO_ROOT/projects and $REPO_ROOT/models to UID/GID 1000. [ -d projects ] && [ -d models ] || { echo "ERROR: expected projects/ and models/ under $REPO_ROOT" >&2; exit 1; } echo "About to chown -R 1000:1000 on:" echo " $REPO_ROOT/projects" echo " $REPO_ROOT/models" echo "(required because containers run as UID 1000). Confirm before proceeding." sudo chown 1000:1000 -R projects sudo chown 1000:1000 -R models
echo "✓ Permissions set" ```
### Step 5: Launch Services
Before pulling, fail fast if the NGC key authenticated in Step 1 but cannot actually access a release image — otherwise `docker compose up` aborts partway with a 401/403 after some work is already done.
```bash cd $REPO_ROOT/compose
# Fail-fast image-access check: confirm the NGC key can reach every release # image BEFORE pulling. `docker manifest inspect` checks registry access without # downloading layers, and the image list is read from the resolved compose so it # tracks the release tag automatically. IMAGES=$(docker compose config --images | sort -u) [ -z "$IMAGES" ] && { echo "ERROR: no images resolved from compose — check the Compose environment settings and chosen profile." >&2; exit 1; } for img in $IMAGES; do echo "Checking access: $img" if ! docker manifest inspect "$img" >/dev/null 2>&1; then echo "NGC login succeeded, but this key cannot access the required image:" >&2 echo " $img" >&2 echo "Provide an NGC key with access to this image's namespace, then re-run Step 1 (login) and retry." >&2 exit 1 fi done
# Start all services (images pulled automatically on first run) docker compose up -d
# Check containers are running docker compose ps ```
The exact image tags change by release; read them from the active compose files instead of hardcoding a version.
### Step 6: Verify Services Are Running
```bash # Read ports from the Compose environment file. COMPOSE_ENV_BASENAME="env" COMPOSE_ENV_FILE="$REPO_ROOT/compose/.${COMPOSE_ENV_BASENAME}" MS_PORT=$(grep AUTO_MAGIC_CALIB_MS_PORT "$COMPOSE_ENV_FILE" | cut -d= -f2) UI_PORT=$(grep AUTO_MAGIC_CALIB_UI_PORT "$COMPOSE_ENV_FILE" | cut -d= -f2) HOST_IP=$(grep HOST_IP "$COMPOSE_ENV_FILE" | cut -d= -f2)
# Wait for microservice readiness. Cold image pulls or first startup can need # extra time after
Source provenance
Decision snapshot
3,175 GitHub stars
Audit
Install and adoption review
Agent-proven evidence
Outcome reports after resolve, review, install, and one narrow run.
No agent outcome data yet. The first agent run can report success, setup needs, risk blocks, failure, or not-relevant through /api/agent/outcome.
Install
Free and open source. Review the report before installing into production agents.
Growth loop
Scenario-led draft for amc-setup-calibration-stack, ready for a manual X post.
amc-setup-calibration-stack: Launch AutoMagicCalib microservice and web UI from NGC release images via Docker Compose. Use... 3.2K stars https://www.openagentskill.com/skills/nvidia-amc-setup-calibration-stack?ref=x
Listing + install path for amc-setup-calibration-stack: https://www.openagentskill.com/skills/nvidia-amc-setup-calibration-stack?ref=x Install: npx skills add NVIDIA/skills --skill amc-setup-calibration-stack
Listing source
This listing was indexed from public sources and is not marked official until a maintainer claim is approved.
Attribution links to the public repository or creator profile. Creators can claim the listing to update ownership signals.
Claim this skillOwner claim
This Registry indexed listing is attributed to NVIDIA but is not marked official yet. Claim it to add a verified owner signal and make future launch, install, and audit updates easier to trust.
Creator backlink kit
Show the canonical listing, current trust and audit signals, and real Agent-Proven evidence where developers evaluate the repository.
[](https://www.openagentskill.com/skills/nvidia-amc-setup-calibration-stack?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/nvidia-amc-setup-calibration-stack?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/nvidia-amc-setup-calibration-stack/audit)
[](https://www.openagentskill.com/skills/nvidia-amc-setup-calibration-stack?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)NVIDIA
@nvidia
Share whether this skill looks useful for your agent workflow. Aggregated feedback improves rankings over time.
Sandbox only
Frontend Design
Guidance for distinctive, intentional UI design, typography, visual direction, and non-template-like product interfaces.
175.1K StarsTaste Skill: Anti-Slop Frontend
Design and implementation guidance for distinctive landing pages, portfolios, product demos, and purposeful redesigns.
85.2K StarsVox Director
Turn one topic into a narrated Vox-style paper-collage explainer or ad video, from script through captions.
1.8K StarsCanvas Design
Create original visual art, posters, PNG assets, and PDF documents through a clear design philosophy.
175.1K StarsPermission surface
secrets or environment access, shell or command execution
Agent outcomes
No agent outcome data yet
Docs
Strong README/SKILL.md context
Risk summary
Install readiness