harnessloop-connectivitylisted

# Harnessloop Connectivity Check declared external system/tool connectivity for Harnessloop evidence and validation. This skill tests access only when the channel contract is explicit enough; it must not infer tools, endpoints, credentials, or parameters. ## Input Contract Accept an explicit skill invocation such as `$harnessloop-connectivity`, or natural language asking to check a named system/tool/channel. Treat `harnessloop:connectivity` as a natural-language alias only; `$harnessloop:connectivity` is not a valid skill invocation. Useful input includes: - `target-project`: defaults to the current working directory. - `channel-id` or system/tool name. - `operation`: read, write, read-write, auth-check, metadata-check, dry-run, or unknown. - `verification-method`: exact command/tool/API/MCP call or documented manual check. - `required-tool`: exact tool name and expected capability. - `credential-reference`: name/location only, never a secret value. - `required-parameters`: endpoint/resource, account/role, permission scope, target resource, environment, and failure handling. - `local-parameter-reference`: `.harnessloop/local/channel-params.json` key or external provider reference managed by `$harnessloop-secrets`. - `write-safety`: dry-run, test resource, rollback path, or explicit human confirmation for write checks. If the channel inventory is missing, run or request `$harnessloop-channels` first. If any required field is missing, ask the user a focused question befor