hap-cli-environments

To prevent HAP CLI from executing commands against the wrong production environment, the skill inspects authorized profiles and matches user intent to profile metadata. It requires confirmation before running destructive actions when the target environment is ambiguous.

Yes, you can scope a single HAP CLI command to a specific profile without switching your entire session. The skill enables safe profile switching by allowing you to choose a profile for one command or an entire session without manually moving credentials.

Safeguards for destructive HAP CLI operations like publishing changes or modifying permissions include built-in guardrails that require explicit clarification. The skill ensures safe execution by requesting confirmation when high-impact operations have an ambiguous target environment.

To switch HAP CLI accounts safely across multiple staging and production profiles, the skill identifies the active environment, account, and organization. It matches your request to available profiles and confirms the target before running any commands.

You need to verify your HAP CLI profile before running bulk writes whenever multiple profiles are authorized. The skill prevents accidental bulk writes to incorrect environments by inspecting authorized profiles and matching user intent to profile metadata.

Yes, the HAP CLI environments skill supports identifying the active organization and login address. It inspects authorized HAP profiles to display the current environment, account, organization, and login address before executing any targeted commands.