A missing shared dependency triggers a generator with undocumented file scope
Source references: 2The prerequisite says to run `gws generate-skills` when the adjacent shared Skill is missing, but the supplied source does not identify which files that command creates or updates, nor require confirmation for this generation step.
An agent may make persistent local Skill-file changes even though the immediate task is to create a cloud template. The available evidence does not establish the target scope or whether existing content can be overwritten.
If the adjacent shared Skill is missing, the prerequisite explicitly directs the agent to run `gws generate-skills`. The supplied source does not identify which files it creates or updates, and the only confirmation warning is presented for the template-creation command. This supports a potential file-change risk, but not that execution occurred. A user can require a list of generated paths and overwrite rules, plus a preview and approval before execution.
> **PREREQUISITE:** Read `../gws-shared/SKILL.md` for auth, global flags, and security rules. If missing, run `gws generate-skills` to create it.Show 1 other places
> [!CAUTION]> This is a **write** command — confirm with the user before executing.