harnessloop-secretslisted

# Harnessloop Secrets Manage local-only channel parameters and secret references for Harnessloop. This skill records the keys a channel needs, where values should be resolved from, and whether each value is present, without copying secret values into chat, evidence, or committed files. ## Local Store Use this project-local path for non-committed channel parameters: ```text .harnessloop/local/channel-params.json ``` Initialize these companion files when missing: ```text .harnessloop/local/.gitignore .harnessloop/local/channel-params.example.json ``` `.harnessloop/local/.gitignore` must ignore `channel-params.json`, `*.secret.json`, `*.token`, and other local secret material. The example file may contain keys, provider names, and placeholder values only. ## Input Contract Accept explicit invocations such as: - `$harnessloop-secrets init` - `$harnessloop-secrets add channel <channel-id> key <name>` - `$harnessloop-secrets set channel <channel-id> key <name>` - `$harnessloop-secrets check channel <channel-id>` - `$harnessloop-secrets resolve channel <channel-id>` - `$harnessloop-secrets audit` Useful input includes: - `channel-id`: stable external channel/tool id. - `parameter-key`: endpoint, username, token, API key, account role, project id, job name, region, or other required parameter. - `sensitivity`: public, internal, credential-reference, secret, or unknown. - `storage`: local-file, env, os-keychain, vault, onepassword, manual, or unknown. - `env-name` or `refe