v1.0.0

Hik Cloud Device Channel Management

ReviewClawScan verdict for this skill. Analyzed May 1, 2026, 8:11 AM.

Analysis

This Hik Cloud skill is purpose-aligned, but it should be reviewed carefully because it can use Hik credentials to change cloud device channel data and can send credentialed requests to a configurable base URL.

GuidanceInstall only if you trust the publisher and intend the agent to manage Hik Cloud device channels. Before using mutating commands, confirm the exact device serial, channel number, new channel name, and sync option. Keep Hik credentials and the token cache protected, and avoid custom base URLs unless they are trusted Hik Cloud environments.

Findings (4)

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

Abnormal behavior control

Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.

Tool Misuse and Exploitation

SeverityMediumConfidenceHighStatusConcern

SKILL.md

- 同步设备下通道
- 修改通道名称
- 同步设备通道名称

These are mutating device/account operations, not just read-only queries. The artifacts document the operations but do not show a required confirmation or bounded approval step before sync or rename actions.

User impactIf invoked unintentionally or with the wrong parameters, the agent could alter Hik Cloud device channel names or synchronize channel state on the user's account/devices.

RecommendationRequire explicit user confirmation before `sync`, `rename`, or `sync-names`; show the exact deviceSerial, channelNo, channelName, and syncLocal values; and document recovery or rollback expectations.

Agentic Supply Chain Vulnerabilities

SeverityLowConfidenceHighStatusNote

metadata

Source: unknown
Homepage: none

The skill is credentialed and can mutate cloud device data, but the registry metadata does not provide a source repository or homepage for provenance review.

User impactUsers have less external provenance information to verify the publisher or audit the skill outside the supplied artifacts.

RecommendationVerify the publisher before installing, and prefer a version with a public source URL, release history, and documented maintenance ownership.

Permission boundary

Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.

Identity and Privilege Abuse

SeverityHighConfidenceMediumStatusConcern

scripts/hik_open_device_channel_management.py

env_base_url = os.getenv(BASE_URL_ENV_VAR)
if env_base_url:
    return normalize_base_url(env_base_url)
...
url=base_url.rstrip("/") + TOKEN_PATH,
...
"client_secret": client_secret,

The script can take the API base URL from an environment variable and then sends the client secret to that base URL's token endpoint. The visible code only normalizes the string and does not show an allowlist or scheme/host restriction.

User impactA misconfigured or malicious base URL could receive Hik client credentials or bearer-token-authenticated requests.

RecommendationDefault to the official Hik Cloud host, restrict custom base URLs to trusted allowlisted domains, warn before using non-default hosts, and avoid sending client secrets to arbitrary URLs.

Identity and Privilege Abuse

SeverityLowConfidenceHighStatusNote

SKILL.md

脚本会自动读取凭证、获取 token、缓存 token ... `--token-cache-file`：token 缓存文件，默认 `~/.cache/hik_open/token.json`

The skill intentionally reads Hik credentials and stores an access token cache locally. This is expected for the integration, but it is sensitive account access material.

User impactAnyone or any process that can read the token cache may be able to use the cached access token until it expires.

RecommendationStore credentials through OpenClaw or a secret manager, keep the token cache path private with restrictive file permissions, and rotate credentials if the cache is exposed.