AdClaw

The name/description, README, and SKILL.md all describe searching ad creative assets via the AdClaw API (ad.h5.miaozhisheng.tech). The primary credential (ADCLAW_API_KEY) is appropriate for this purpose. Minor inconsistency: registry metadata lists no required env vars while SKILL.md and metadata block specify ADCLAW_API_KEY as primaryEnv.

SKILL.md gives explicit, narrow runtime instructions: parse user parameters (using the included references/param-mappings.md), confirm params with the user, check that $ADCLAW_API_KEY is set, call the documented API via curl, and return only the H5 page link. It does not instruct reading unrelated system files or exfiltrating data beyond the API service.

This is an instruction-only skill with no install spec and no code files — lowest risk for supply-chain installs. README references installation via npx clawhub, which is an installation instruction but not an automated install spec in the skill itself.

The single credential requested (ADCLAW_API_KEY) is appropriate and used only to authenticate requests to the declared API. Note that the registry's 'required env vars' list is empty while the skill metadata and instructions rely on ADCLAW_API_KEY; this is a minor metadata mismatch that could confuse users. Also: when the skill runs it will send the API key to ad.h5.miaozhisheng.tech in an HTTP header (expected behavior for an API key).

The skill does not request always:true and does not modify other skills or system-wide configs. Autonomous invocation is allowed (platform default) and appropriate for a conversational search skill.