setup

Create disposable sandbox environments for OCI starter packs with Terraform variables.

3|2|Updated Sep 25, 2025
One-click install
npx skills add https://github.com/oci-ai-incubations/ai-accelerator-starter-packs --skill setup-oci-ai-incubations
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup
Source: https://github.com/oci-ai-incubations/ai-accelerator-starter-packs/tree/main/.claude/skills/setup
Command: npx skills add https://github.com/oci-ai-incubations/ai-accelerator-starter-packs --skill setup-oci-ai-incubations

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creates an isolated sandbox environment for deploying and testing a specific starter pack without modifying the repository. Everything from tool installations to generated Terraform variables stays inside the sandbox, ensuring reproducibility and safety.

Core Features & Use Cases

  • Isolated sandbox: All packages, temporary files, and state live under /tmp/dat-sandbox-<timestamp>/
  • Automatic variable population: Extracts OCI config values and populates terraform.tfvars and env.sh for quick starter-pack deployment.
  • Guided setup workflow: Step-by-step process including OCI CLI bootstrap, venv creation, Playwright setup, and pack-specific variable collection for testing.

Quick Start

Run the setup tool to create a sandbox and auto-generate env.sh and terraform.tfvars for your chosen starter pack.

Frequently Asked Questions about setup

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

FAQPage Schema
How do I create an isolated sandbox environment for testing an OCI starter pack?

To create an isolated sandbox environment for an OCI starter pack, this tool generates a disposable directory under /tmp/dat-sandbox-<timestamp>/, ensuring all packages and temporary files stay separated from your main repository for safe testing.

How do I automatically populate terraform.tfvars for OCI-based starter packs?

Automatically populate terraform.tfvars by extracting OCI config values during the guided setup workflow, which prepares environment variables and Terraform configurations for specific packs like vss, cuopt, and enterprise_rag.

What is the best way to test a starter pack without modifying the main repository?

The best way to test a starter pack without modifying the repository is using a disposable sandbox, which isolates tool installations, generated Terraform variables, and state files within a temporary directory to ensure reproducibility.

Does the sandbox setup include configuring the OCI CLI and Python venv?

Yes, the sandbox setup includes a guided workflow that bootstraps the OCI CLI, creates a Python venv, and configures Playwright, ensuring all necessary tools are installed within the isolated environment.

Can I use this setup tool with enterprise_rag or paas_rag starter packs?

Yes, you can use this setup tool with enterprise_rag, enterprise_rag_aiq, and paas_rag starter packs, as it specifically applies OCI config extraction and pack-specific variable collection for these deployments.

Why do my generated env.sh and terraform variables need to stay in a sandbox?

Generated env.sh and terraform variables stay in a sandbox to ensure reproducibility and safety, preventing temporary state files and package installations from polluting or modifying your primary code repository.