Air gapped setup

[r2dedios]

Summary

Pack(s) affected

• rh-sre
• rh-developer
• ocp-admin
• rh-virt
• rh-ai-engineer
• Other / repo-wide

Change type

• New skill
• New agent
• New pack
• Update existing skill / agent
• MCP server config (mcps.json)
• Docs / README
• CI / tooling

CLAUDE.md compliance

• Agents orchestrate skills; no direct MCP/tool calls in agents
• Skills are single-purpose task executors
• Skills encapsulate all tool access (MCP tools invoked only inside skills)
• Document consultation: file is read with the Read tool, then declared to the user
• No credentials hardcoded; env vars used via ${VAR} references
• Human-in-the-loop confirmation added for any destructive or critical operations

Validation

• make validate passes locally
• New/changed skills have valid YAML frontmatter (name, description)
• New/changed agents have valid YAML frontmatter (name, description)

[dmartinol]

My 2 cents:
Just add a small AIRGAPPED.md file to the main README with the findings in terms of validated environments, like: RHOAI version and configuration, validated model with ad-hoc notes if required (e.g., any functional or system issues detected?), main system specification (GPUs, etc) and move all the other files to a dedicated repo

[r2dedios]

Moving this PR and its content to a separate repository