Direct Analysis
PassAudited by ClawScan on May 1, 2026.
Overview
This instruction-only skill is coherent for Yandex Direct campaign analysis, but users should notice it relies on a Yandex token and client login that are not declared in the registry credential metadata.
Before installing, confirm you are comfortable letting the agent use a Yandex Direct token and client login to read advertising performance data. Prefer a scoped reporting token, verify the target account, and require explicit approval before any campaign, bid, or budget changes.
Findings (2)
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.
The agent may access advertising account statistics such as spend, CTR, CPC, conversions, ads, and keywords.
The skill expects a Yandex token and client login to access campaign statistics. This is expected for Yandex Direct analysis, but users should notice that the registry metadata lists no required env vars or primary credential.
Использовать YANDEX_TOKEN и CLIENT_LOGIN
Use a least-privilege Yandex Direct token where possible, confirm which account CLIENT_LOGIN refers to, and do not allow campaign changes unless explicitly reviewed.
If misused, broad API access could retrieve more account data than the user expected.
The skill requires curl, implying direct API calls. This is coherent with retrieving Yandex Direct statistics, but curl is a broad tool and should be limited to the intended reporting workflow.
requires:\n bins: ["curl"]
Keep curl/API use limited to user-requested Yandex Direct reporting calls and require explicit user confirmation before any action that could modify campaigns, budgets, or bids.