Results for “environment”

Force-links a development or target environment to a Power Platform Pipelines host, overriding any existing association with a previous host. Use when creating a deploymentenvironments record fails with "this environment is already associated with another pipelines host", or when intentionally migrating an environment from one host to another (e.g., Platform Host → Custom Host, or between two Custom Hosts). Calls the documented `ManageEnvironmentStamp` Dataverse action (the API behind the "Force Link" button in the Deployment Pipeline Configuration app). DESTRUCTIVE to the previous host: makers lose access to any pipelines in that host that used this environment. Reversible by running Force Link from the previous host. Use when asked to: "force link environment", "force-link to new host", "switch pipelines host", "environment already associated with another host", "take over pipelines association", "relink environment to host".

The English summary is being prepared. Showing the original description.

Set up and troubleshoot disposable runtime environments that Orca creates for each workspace. Review recipe settings in orca.yaml, scaffold scripts that create and dispose of environments, and investigate failures reported by the recipe diagnostic command.

• Setting up a new environment recipe from start to finish
• Reviewing environmentRecipes settings in orca.yaml
• Scaffolding provider lifecycle scripts

Set up a Python environment inside the project and install its packages. Follow existing environment tools when present, avoid changing the system Python, and provide commands that work from a fresh shell.

• Set up an environment for a new Python project
• Install packages into an existing project environment
• Resolve an externally-managed-environment installation error

Diagnose and fix .NET MAUI development environment problems involving SDKs, Java, Android tools, and platform requirements. The skill discovers required versions from NuGet metadata and checks the environment again after each fix.

• Setting up a .NET MAUI development environment
• Investigating missing SDK or JDK build errors
• Checking the environment after SDK or OS updates

Find available computers and remote environments, then start or continue a task in the requested location. Route work involving files or apps on the user's computer to that computer, and follow progress while preserving the selected environment.

• Start a task on a named remote environment
• Route work involving files on your own computer
• Select your computer for work with a desktop app

Manage environment variables and secrets across development, staging, and production environments. Use when someone needs to audit env vars, sync secrets between environments, detect missing or mismatched variables, rotate credentials, or set up a new environment from an existing one. Trigger words: env vars, environment variables, secrets, .env file, dotenv, config management, secret rotation, missing variable, environment sync.

The English summary is being prepared. Showing the original description.

Create reproducible, cross-platform development environments with Flox — a declarative environment manager built on Nix. ALWAYS use this skill when the user needs to: set up a project with system-level dependencies (compilers, databases, native libraries like openssl, libvips, BLAS, LAPACK); configure reproducible toolchains for Python, Node.js, Rust, Go, C/C++, Java, Ruby, Elixir, PHP, or any language; manage environments that must work identically across macOS and Linux; pin exact package versions for a team; run local services (PostgreSQL, Redis, Kafka) alongside development tools; onboard new developers with a single command; or solve 'works on my machine' problems. Especially valuable for AI-assisted and vibe coding — Flox lets agents install tools into a project-scoped environment without sudo, system pollution, or sandbox restrictions, and the resulting environment is committed to the repo so anyone can reproduce it instantly. Use this skill even if the user doesn't mention Flox — if they describe needing reproducible, declarative, cross-platform dev environments with system packages, this is the right tool. Also use when the user mentions .flox/, manifest.toml, flox activate, or FloxHub.

The English summary is being prepared. Showing the original description.

Add, rename, or review SGLang environment variables using consistent definitions, types, names, and access methods. The skill also guides migration from old names and temporary test overrides that restore the original values afterward.

• Adding a new SGLang environment variable
• Migrating deprecated environment variable names
• Temporarily overriding settings in tests

Manage encrypted API secrets across local, development, staging, and production profiles with dotenvx and Dotenv Armor. Covers storing and rotating credentials, sharing decryption keys, selecting runtime environments, and checking profile consistency with deployed AWS Secrets Manager settings.

• Store an API key in an encrypted environment profile
• Switch local execution between backend environments
• Share or rotate decryption keys

Prepare reproducible setup and removal instructions for software environments on Open-Science SSH hosts, including Slurm clusters. Check available tools, define named activation settings, and validate the environment where jobs run after the user installs it.

• Preparing a remote environment for required packages
• Making job environment activation repeatable
• Checking software and GPU operation on Slurm nodes

Upgrades an MWAA environment to a newer Airflow version — within 2.x, within 3.x, or across the 2.x-to-3.x boundary. Computes the version-jump path, inserting the 2.11.x stepping-stone and Python-transition step when needed. Chooses an approach by whether run history and the same environment (URL/ARN) must be kept: a new-environment upgrade (blue-green), a rehearsed in-place upgrade validated on a test copy, or a direct in-place upgrade. Runs Ruff scanning and deprecation-warning log scans for 3.x moves, plus Docker validation, batched deployment, and switchover. Saves a resumable upgrade plan for multi-session work. Triggers on: upgrade MWAA, upgrade Airflow, migrate to Airflow 3, MWAA Airflow 3, Airflow 2 to 3, preserve Airflow history, keep same MWAA environment, blue-green cutover, validation environment before cutover. Not for authoring new DAGs (authoring-mwaa-workflow), debugging unrelated DAG failures (debugging-mwaa-workflow), or MWAA Serverless YAML workflows (provisioned Python DAGs only).

The English summary is being prepared. Showing the original description.

Configures environment variables for Power Pages site settings to support ALM across environments. Creates environment variable definitions in Dataverse, guides the user through linking site settings to those variables via the Power Pages Management app, adds the variables to the solution, and generates a deployment-settings.json file with per-stage override values. Use when asked to: "configure environment variables", "add env vars", "set up deployment variables", "make site settings environment-specific", "configure ALM variables", "set up env-specific settings", "add deployment settings", "configure per-environment settings".

The English summary is being prepared. Showing the original description.

Design environment strategy for testing across dev, CI, preview, staging, and production — Docker Compose test infrastructure, multi-stage Dockerfiles, seed-data lifecycle, per-PR preview environments, production parity, and external-dependency stubbing at the HTTP boundary. Use when: "set up test environment," "docker-compose for tests," "per-PR preview environment," "staging parity," "spin up test infra," "environment tiers." Not for: choosing mock-vs-stub-vs-fake per dependency — use service-virtualization; factory and fixture data patterns — use test-data-management; pipeline/Actions config — use ci-cd-integration. Related: test-data-management, ci-cd-integration, contract-testing, service-virtualization.

The English summary is being prepared. Showing the original description.

Document development environment requirements for team consistency and AI agent understanding during PRD v0.6 Architecture. Triggers on requests to define environment setup, document tooling, create dev setup guide, or when user asks "what tools do I need?", "environment setup", "dev environment", "CLI requirements", "project setup", "onboarding setup". Consumes TECH- (stack selections), ARC- (architecture decisions). Outputs ENV- entries for development, CI/CD, and infrastructure environments. Feeds v0.7 Build Execution.

The English summary is being prepared. Showing the original description.

Expert knowledge for environment art in games - modular design, visual hierarchy, color scripting, environmental storytelling, optimization, and world-building. From blockout to final art pass, creating immersive, performant, and readable spaces. Use when "environment art, level art, world art, modular kit, kit-bashing, set dressing, prop placement, biome design, visual hierarchy, color script, hero prop, trim sheet, environment composition, skybox, atmosphere, environment, level-art, world-building, modular, kit-bashing, set-dressing, visual-design, game-art, composition, optimization" mentioned.

The English summary is being prepared. Showing the original description.

Drafts and revises U.S. environmental indemnity agreements for real estate lending and acquisition transactions, allocating contamination and environmental-law liability to protect lenders, secured parties, or buyers. Covers indemnity scope, reps/warranties, covenants, remediation rights, escrows, insurance, survival, and assignment aligned to loan or acquisition documents. Use when drafting an environmental indemnity agreement, environmental liability allocation, lender environmental rider, or Phase I/II ESA-driven risk terms.

The English summary is being prepared. Showing the original description.

Human modification of Earth's systems and the geographic dimensions of environmental change. Covers climate change science (greenhouse effect, feedback loops, projections), deforestation and land use change, desertification and soil degradation, water resource management, biodiversity loss and conservation geography, pollution and environmental justice, and sustainability frameworks. Use when reasoning about human impacts on the environment, environmental policy, conservation planning, climate adaptation, or the spatial distribution of environmental risks.

The English summary is being prepared. Showing the original description.

Distributional analysis of environmental benefits and burdens across communities. Covers the historical origins of environmental justice in the U.S. civil rights tradition, siting and exposure disparities, indigenous rights and land stewardship, climate justice at global and intergenerational scales, procedural vs. distributional vs. recognition justice, and the environmental justice screening tools used by regulators. Use when analyzing who bears environmental harm and who receives environmental benefit, or when designing interventions whose distributional consequences matter.

The English summary is being prepared. Showing the original description.

Prepare a local LangBot environment for development and browser testing. The skill covers service startup, shared connection settings, browser access, proxy troubleshooting, and reusable login profiles, with guidance for Linux and WSL environments.

• Prepare a local Linux or WSL development environment
• Start services and verify WebUI access
• Choose Computer Use or Playwright MCP for browser control

Prepare an isolated Python environment for SageMaker deployments and AWS automation. The skill selects a supported Python version, installs current AWS packages, and checks versions so installation and execution use the same environment.

• Prepare a Python environment for SageMaker deployment
• Separate AWS automation dependencies from system Python
• Check installed AWS package versions

Investigate how credentials can be exposed in CI/CD, the systems that build and deploy software. Covers environment variables, logs, credential stores, cloud trust settings, and runner tokens, with methods to assess access scope and defensive controls.

• Review secret exposure in build environments
• Search build logs and caches for leaked credentials
• Assess trust settings between pipelines and cloud services

Deploy an application to an environment that has already been configured. Use it when the destination is established and the next task is to put the application into that environment.

• Deploying an application to a configured environment
• Putting an application into its established destination
• Requesting deployment after environment configuration

Check the SenseNova-Skills installation, Python dependencies, and environment variables before using other skills. Prompt for missing configuration, save supplied values to a .env file, and reload settings or suggest restarting the agent.

• Checking setup before using SenseNova-Skills
• Finding missing Python dependencies
• Entering and saving missing API configuration

Replace C# static calls for time, files, or environment values with existing abstractions that tests can substitute. Update construction and affected tests within a defined scope, while preserving read counts, evaluation order, date-time semantics, and existing static callers.

• Migrating DateTime.UtcNow calls to TimeProvider
• Replacing File calls with an existing IFileSystem
• Replacing disk or environment access in unit tests with fakes