v1.1.0

Yandex 360 CLI (Disk, Calendar, Mail)

ReviewClawScan verdict for this skill. Analyzed May 1, 2026, 6:35 AM.

Analysis

The skill mostly matches its Yandex Disk and Calendar CLI purpose, but it requests an email-sending OAuth permission even though the documented mail feature is only informational.

GuidanceReview the OAuth scopes before authorizing. If you only need Disk and Calendar, do not grant `mail:smtp`; keep the token and env files private; and approve upload/download paths and calendar event creation carefully.

Findings (3)

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

SeverityLowConfidenceHighStatusNote

src/yax.cjs

`/v1/disk/resources/upload?path=${encodeURIComponent(remotePath)}&overwrite=true`

The upload implementation requests overwrite behavior for the target Yandex Disk path. This is purpose-aligned for a disk CLI, but users should realize uploads may replace an existing remote file.

User impactA mistaken or overly broad upload command could overwrite a file in the authorized Yandex Disk area.

RecommendationConfirm the remote path before upload and consider adding an explicit overwrite flag or confirmation for safer use.

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

SeverityMediumConfidenceMediumStatusConcern

SKILL.md

- **Mail**: ⚠️ Limited — Yandex has no public HTTP API for mail ...
- `mail:smtp` — Mail sending (SMTP only, no HTTP API)
...
# Mail (informational only)

The skill asks the user to grant an OAuth scope that can send mail, while the documented mail command is only informational. That makes the requested account permission broader than the shown functionality.

User impactInstalling and authorizing with the requested scopes could grant the token permission to send email from the Yandex account, even though the documented CLI does not clearly provide a mail-sending workflow.

RecommendationRemove `mail:smtp` from the required OAuth scopes unless the skill actually implements and clearly documents mail sending; users should create the OAuth app with the least scopes they need.

Identity and Privilege Abuse

SeverityLowConfidenceHighStatusNote

src/yax.cjs

const TOKEN_FILE = path.join(process.env.HOME, ".openclaw/yax-token.json"); ... fs.writeFileSync(TOKEN_FILE, JSON.stringify(data, null, 2), { mode: 0o600 });

The CLI stores a reusable OAuth token locally. The restrictive mode is a good mitigation, but the token still represents access to the user's Yandex account within the granted scopes.

User impactAnyone who can read the token file could potentially use the authorized Yandex permissions until the token expires or is revoked.

RecommendationKeep `~/.openclaw/yax-token.json` private, revoke the OAuth token if the skill is no longer used, and avoid granting unnecessary scopes.