EWCCLI

Use this skill for European Weather Cloud (EWC) CLI workflows: installing ewccli, validating the ewc command, preparing login profiles, handling OpenStack application credentials safely, listing/showing/deploying Community Hub items, using infrastructure commands, testing custom catalogues, or troubleshooting ewc errors.

This skill is grounded in ewccli 0.3.1 and the upstream ewcloud/ewccli main branch inspected on 2026-04-29. Install that exact version (ewccli==0.3.1); a newer release may change the registered command surface, so revalidate this skill before recommending one. Prefer installed ewc --help output and official EWC upstream docs when exact flags, item metadata, or service behavior matter.

Operating Rules

1. Never print, commit, or log OpenStack application credential IDs, application credential secrets, private SSH keys, encoded SSH key material, tokens, cloud account details, or private profile files.
2. Read-only commands (ewc version, ewc --help, ewc hub list, ewc hub show, ewc infra list, ewc infra show) are safe to run without confirmation when the user asks for a check. They still need a working profile or catalogue source.
3. State-changing commands (ewc login, ewc hub deploy, ewc infra create, ewc infra delete) require explicit user confirmation before execution. Confirm target federee, profile, tenant, item/server name, and dry-run expectations first, and prefer --dry-run where supported.
4. Do not overwrite or delete profiles in $HOME/.ewccli/profiles, SSH keys under $HOME/.ewccli/.ssh, OpenStack clouds.yaml, or generated deployment outputs unless the user explicitly requests it.
5. Never invent EWC-specific values: tenant names, portal or Horizon URLs, OpenStack CLI alternatives, DNS commands, service paths, or support processes. Use official-links.md for links and auth-profiles.md for the tenant-name convention and the credential-request process; otherwise ask the user.
6. ewc login consumes an existing credential source (clouds.yaml, sourced openrc, environment variables, or its interactive prompt) and writes only the ewccli profile. It does not create or configure clouds.yaml or openrc. See auth-profiles.md.
7. If credentials are missing, provide commands with placeholders or explain the interactive prompt path instead of inventing values.
8. For exact command flags, run ewc --help or ewc <group> --help locally before finalizing examples. Some ewc infra <command> --help calls initialize profile/OpenStack configuration, so treat them as configured-environment checks.
9. Locate the CLI with command -v ewc before anything else. Never assume a project .venv, a personal virtualenv directory, or a repository-specific path; install per install.md into standard user-tool locations or an environment the user names.
10. For ewc infra, place --profile <profile-name> immediately after infra, before the subcommand.