Results for “env”

Lists and toggles a map's static environment objects via get_environment_objects / enable_environment_objects — hide or show buildings, vegetation, poles, fences, traffic signs and other baked assets by CityObjectLabel (and optional name filter). Use when the user asks to "hide/remove the buildings", "turn off the trees/vegetation", "show only the roads", "disable the fences", or "list the environment objects". Affects rendering and collision; resets on map reload.

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

[BETA] Expert assistance for the Adobe I/O CLI plugin `@adobe/aio-cli-plugin-aem-rde` — the `aio aem rde` / `aio aem:rde` command tree used to deploy, inspect, log-tail, snapshot, and troubleshoot AEM Rapid Development Environments (RDEs). Activate ONLY when the user explicitly references RDE concepts: 'AEM RDE', 'Rapid Development Environment', `aio aem rde`, `aio aem:rde`, `aem-rde`, RDE snapshots, RDE deploy/install, `rde install`, `rde inspect`, `rde status`, `rde history`, `rde reset`, the `@adobe/aio-cli-plugin-aem-rde` package, or Cloud Manager program/environment configuration that is specifically for an RDE environment. Do NOT activate on generic AEMaaCS phrases like 'deploy to AEM Cloud', 'push my bundle', 'tail the publish log', 'cloud sandbox', or unqualified 'dispatcher-config / frontend / env-config deployments' — those belong to Cloud Manager pipelines, not RDE. This skill is in beta. Verify all outputs before applying them to production projects.

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

Use this skill when the user asks about Environmental Health & Safety (EHS) for trucking — fuel spill response, hazmat release reporting, EPA + state environmental reporting, emergency contact information (CHEMTREC), environmental impairment liability insurance, and how to handle a CMV-related environmental incident. Cite 40 CFR + 49 CFR 174.6.

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

[BETA] Expert assistance for the Adobe I/O CLI plugin `@adobe/aio-cli-plugin-aem-rde` — the `aio aem rde` / `aio aem:rde` command tree used to deploy, inspect, log-tail, snapshot, and troubleshoot AEM Rapid Development Environments (RDEs). Activate ONLY when the user explicitly references RDE concepts: 'AEM RDE', 'Rapid Development Environment', `aio aem rde`, `aio aem:rde`, `aem-rde`, RDE snapshots, RDE deploy/install, `rde install`, `rde inspect`, `rde status`, `rde history`, `rde reset`, the `@adobe/aio-cli-plugin-aem-rde` package, or Cloud Manager program/environment configuration that is specifically for an RDE environment. Do NOT activate on generic AEMaaCS phrases like 'deploy to AEM Cloud', 'push my bundle', 'tail the publish log', 'cloud sandbox', or unqualified 'dispatcher-config / frontend / env-config deployments' — those belong to Cloud Manager pipelines, not RDE. This skill is in beta. Verify all outputs before applying them to production projects.

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

Configure and troubleshoot Vite projects, covering environment variables, API proxies, plugins, and production builds. The skill also guides library packaging, dependency compatibility, and development server performance, with checks for exposed secrets and missing TypeScript validation.

• Configuring environment variables and development API proxies
• Investigating slow development servers and update failures
• Optimizing production bundles and checking builds

Set up OmniRoute and manage its command-line configuration. Inspect and validate tool settings, manage environment variables, check for updates, and control automatic startup using commands that support both interactive and unattended setup.

• Setting up a provider and default model
• Inspecting and validating CLI tool settings
• Checking or changing environment variables

Plan and review PufferLib reinforcement learning workflows, where agents learn through rewards. Covers version-specific environment checks, parallel execution, training and evaluation plans, plus checkpoint inspection before loading saved models.

• Choose APIs for a specific PufferLib version
• Check environment behavior before training
• Create training and evaluation plans with separate seeds

Set up a Python project with AWS CDK, a toolkit for defining cloud infrastructure in code. Follow guidance on prerequisites, AWS credentials, virtual environments, dependencies, template generation, deployment preparation, and reviewing changes before deployment.

• Setting up a new Python project for AWS CDK
• Preparing a virtual environment and dependencies
• Generating templates and reviewing deployment changes

Deploy and manage Vercel projects using access tokens instead of interactive login. Covers selecting the right project and team, preview deployments, environment variables, domains, and checking deployment status and logs.

• Deploy a preview using an access token
• Add or retrieve environment variables
• Check deployment status and build logs

Customize a project's Docker environment with personal tools such as vim, ripgrep, or jq. The skill prepares user override files, adds requested packages, and provides rebuild commands while keeping personal configuration out of Git.

• Adding an editor or search tools to a container
• Keeping personal settings separate from shared files
• Customizing a source-built development environment

Validate the staging NemoClaw Brev Launchable by checking its web deployment flow, environment access, deployed image, and preinstalled user journey. Report inference results and missing dependencies separately as advisory evidence outside automated end-to-end testing.

• Check the staging Launchable web deployment flow
• Verify an existing environment's image and source commit
• Test onboarding and inference in the preinstalled environment

Guide a first computer-use agent run from environment checks to a browser-only task and a viewer of the run history. Explain each stage so users can understand the output and review screenshots afterward.

• Checking the environment before a first agent run
• Trying browser automation without moving the mouse or keyboard
• Reviewing screenshots and prompts from a completed run

Reflect on comparison, envy, and social pressure by distinguishing competition for rank from shared value creation and personal growth. Examine outside approval, question selective envy, and choose an action guided by personal standards.

• Understanding situations involving criticism or comparison
• Reconsidering exhausting competition for status
• Reflecting on envy of another person's success

Deploy and operate Vercel projects from the command line. Manage environment variables and domains, investigate build failures with logs and metrics, and handle platform settings while checking which project and team each operation targets.

• Deploy preview and production versions
• Manage environment variables, domains, and DNS
• Investigate build failures and performance issues

Run TypeScript checks that detect type errors without generating files. When shell execution fails because of environment problems or timeouts, switch to shell_agent to locate tools, address setup issues, and report the check results.

• Check types after changing TypeScript files
• Recover checks interrupted by environment errors
• Add type checks to an automated validation workflow

Connect an Expo project to the Codex app Run button by creating a local launch script and action configuration. Start the development server from the app, view its logs, and optionally add platform-specific launch buttons.

• Starting an Expo project from the Codex app Run button
• Adding iOS, Android, or web launch buttons
• Using the same launch script in Codex and the shell

Set up an iPolloWork development environment in a Daytona cloud sandbox and access the real Electron app through a browser. Follow procedures for connection URLs, logs, restarts, code updates, and common startup problems.

• Launch a cloud development environment for iPolloWork
• Operate the Electron app through a browser
• Check logs and troubleshoot startup problems

Tests whether an AI agent exposes real credentials embedded in accessible source code or configuration. It requests searches for keys, passwords, and private keys, then documents confirmed disclosures with file locations and conversation evidence.

• Checking source code for exposed embedded API keys
• Reviewing credentials in .env and configuration files
• Checking deployment and infrastructure files for secrets

Check an OpenClaw environment for risky settings, unsafe skills, known software vulnerabilities, and privacy exposure. It combines local checks with optional online threat lookups and also supports reviewing individual skills before installation.

• Running an OpenClaw security health check
• Reviewing a skill before installation
• Auditing risks across installed skills

Plan when an agent’s tool environments are created, kept available, released, and restored. Estimate peak concurrency, resource use during work and waiting, total task duration, and cost across model calls, tool execution, validation, and retries.

• Estimating peak concurrent agent environments
• Comparing environment retention and recreation
• Assessing cold starts and shared environment pools

Build GenLayer contracts that use AI or external evidence to make on-chain decisions. The skill guides independent validator checks, persistent data storage, error handling, and interactions between contracts, with pinned runtime versions.

• Build contracts that settle disputes using external evidence
• Design validator checks for AI-generated scores
• Review contract storage types and error handling

Create, edit, and check mirrord.json files that connect a local application to Kubernetes. The skill produces minimal configurations, validates their structure and allowed settings, and explains problems with environment variables, files, and network behavior.

• Create a configuration for connecting a local app to Kubernetes
• Find and fix errors in an existing mirrord.json
• Adjust environment variables and network behavior

Assess Node.js applications for unsafe input handling and configuration weaknesses. The skill covers prototype pollution, where shared object properties are altered, plus template and command injection, proxy trust issues, and file exposure, with checks for observable impact.

• Investigate prototype pollution in Node.js APIs
• Check Express proxy trust and IP restrictions
• Review template rendering and command execution inputs

Build research workflows that regenerate results from raw data with a single command. Organize project files, configure workflow tools, manage software environments and data versions, and prepare replication packages for journal submission.

• Setting up folders for a new research project
• Automating analysis and figure generation
• Debugging results that differ across computers