translation

Security checks across static analysis, malware telemetry, and agentic risk

Overview

The provided artifacts show an instruction-only translation guide, with the main thing to notice being its optional use of local project context files for terminology and style.

This looks safe to use as an instruction-only translation aid. Before relying on it, make sure any `.claude/project-context.md` or `.cursor/project-context.md` files in your project contain only appropriate brand, market, and terminology information.

Static analysis

No static analysis findings were reported for this release.

VirusTotal

VirusTotal findings are pending for this skill version.

View on VirusTotal

Risk analysis

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.

#
ASI06: Memory and Context Poisoning
Low
What this means

Project context files may shape translation recommendations and outputs; incorrect or injected content there could lead to poor terminology or style choices.

Why it was flagged

The skill instructs the agent to consult persistent project context files. This is relevant and narrowly scoped for translation quality, but those files can influence the agent’s terminology, tone, and market assumptions if they contain stale or untrusted content.

Skill content
If `.claude/project-context.md` or `.cursor/project-context.md` exists, read it for brand voice, target markets, and product terminology.
Recommendation

Keep project context files reviewed and project-owned, and avoid placing secrets or unrelated instructions in them.