secret-wrapperlisted
Install: claude install-skill trocho/secret-wrapper
# Secret Wrapper
Use `secret-wrapper run` as the common launcher. Every provider uses the same runtime contract: provider, one or more binds, optional scope, and command. When a supported local provider confirms a value is missing, `run` opens a one-time local browser form, saves the submitted values, and then starts the command.
## Standard
- Keep the secret out of TOML, `.env`, shell history, and chat.
- Use `--bind 'ENV_NAME=RECORD.FIELD[TRANSFORMS][.JSON_PROPERTY[TRANSFORMS]...]'` for every target variable. `[base64]` decodes text and `[json]` parses JSON text; transforms run from left to right and `[json]` is required before a JSON property. Escape literal `.`, `\`, `[` and `]` as `\.`, `\\`, `\[` and `\]` and quote the whole bind so the shell preserves the escape. Bitwarden and 1Password may omit `FIELD` only for their default `password`; prefer the explicit field in shared configuration.
- Use `--scope NAME=VALUE` only for provider context such as a 1Password vault or Infisical environment.
- Do not bind `PATH`, `NODE_OPTIONS`, or dynamic-loader variables; the launcher rejects process-control names.
- Launch the target through the CLI, not directly.
- In compacted task summaries and handoffs, do not repeat secret values, bind expressions, provider record locators, or scopes. At most state that the target is launched through Secret Wrapper and point to the local configuration file when one exists.
- For a deliberate first setup or change, use `secret-wrapper authoriz