Configure .conductor/settings.toml, migrate legacy conductor.json, and set up local/cloud Conductor workspace scripts, env vars, files, and caches.
Install
npx skills add https://github.com/biw/skills --skill conductor-setupSKILL.md
Conductor Setup
Use this skill when configuring a repository for Conductor workspaces. When invoked directly, audit the setup against the conventions below and either apply the changes or report that none are needed.
Workflow
- Inspect
.conductor/settings.toml,.conductor/settings.local.toml, legacyconductor.json,.worktreeinclude,.conductor/*.sh, legacy root-levelconductor-*.sh, package scripts, and repo docs. CheckCONDUCTOR_IS_LOCALand decide whether each script supports local workspaces, cloud workspaces, or both. - Read only the references needed for the task:
references/settings-and-migration.mdfor settings layers, schemas, supported repository fields, orconductor.jsonmigration.references/scripts-and-environment.mdfor setup/run/archive scripts, shells, variables, concurrency, Spotlight, or caches.references/files-layouts-and-troubleshooting.mdfor Files to copy,.worktreeinclude, monorepos, linked repositories, MCP/privacy, or diagnosis. Read more than one only when the task crosses those concerns.
- Apply the selected reference's documented contract. Prefer team settings over machine-local configuration; preserve an existing deliberate script layout; use Conductor variables instead of hard-coded workspace paths, resources, and local ports.
- Keep secrets and machine-specific credentials out of committed settings. Change MCP/privacy configuration only when asked or required by repository policy.
- Validate TOML and run the narrowest relevant check for every script changed. Report when the existing setup already satisfies the requested outcome.
Resources
references/settings-and-migration.md: settings scope, precedence, fields, schemas, and legacy migration.references/scripts-and-environment.md: script roles, local/cloud shells and variables, run behavior, caches, and cleanup.references/files-layouts-and-troubleshooting.md: copied files, repository layouts, privacy boundaries, and diagnosis.
Related skills
azure-diagnosticsmicrosoft608KDebug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe triage. WHEN: debug production issues, troubleshoot app service, app service high CPU, app service deployment failure, troubleshoot container apps, troubleshoot functions, troubleshoot AKS, VM RDP, Linux SSH, VM black screen, can't connect to VM, reset VM password, NSG or firewall blocking, kubectl cannot connect, kube-system/CoreDNS failures, pod pending, crashloop, node not ready, upgrade failures, aazure-preparemicrosoft608KPrepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles for the Azure Developer CLI (azd) workflow. USE ONLY when the user explicitly wants to use azd as the deployment tool, or the project already has an azure.yaml file. DO NOT USE FOR: non-azd deployments, Python App Service code-only deploys (use python-appservice-deploy), or cross-cloud migration (use azure-cloud-migrate). WHEN: prepare app for azd, create azure.yaml, set up azazure-aimicrosoft608KUse for Azure AI: Search, Speech, OpenAI, Document Intelligence. Helps with search, vector/hybrid search, speech-to-text, text-to-speech, transcription, OCR. WHEN: AI Search, query search, vector search, hybrid search, semantic search, speech-to-text, text-to-speech, transcribe, OCR, convert text to speech.azure-deploymicrosoft607KExecute Azure deployments for ALREADY-PREPARED applications that have existing .azure/deployment-plan.md and infrastructure files. DO NOT use this skill when the user asks to CREATE a new application — use azure-prepare instead. This skill runs azd up, azd deploy, terraform apply, and az deployment commands with built-in error recovery. Requires .azure/deployment-plan.md from azure-prepare and validated status from azure-validate. WHEN: \"run azd up\", \"run azd deploy\", \"execute deployment\",