Urdu Translator

v1.0.0

Translates text into fluent Urdu or Roman Urdu, supporting cultural idioms and natural language flow in both scripts.

0· 102·1 current·1 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The skill name, SKILL.md, and index.js implement a translation function that delegates to agent.chat — this is proportionate to an Urdu translator. Minor inconsistency: package.json description claims 'using Google/Gemini API' although the code does not directly call any external API or require credentials; it simply forwards text to the host agent's chat interface. This is likely a documentation/marketing mismatch rather than malicious behavior.
Instruction Scope
SKILL.md and index.js keep scope limited to translating provided content. The runtime uses only agent.chat to produce translations and does not read files, environment variables, system paths, or send data to arbitrary endpoints.
Install Mechanism
No install spec is provided and the skill is instruction/code-only; nothing is downloaded or written during install.
Credentials
The skill declares no required environment variables or credentials and the code does not access any. That is proportionate for a translator that delegates to the agent's LLM.
Persistence & Privilege
The skill is not always-enabled and uses default autonomous invocation settings. It does not attempt to modify other skills or global agent configuration.
Assessment
This skill appears coherent and limited to translation. Before installing: (1) note that translations are produced by the agent's chat model — any text you submit will be sent to that model/provider, so avoid sending sensitive or private data; (2) the package.json mentions Google/Gemini but the code doesn't call that API directly — treat that as a documentation mismatch and prefer skills with clearer provenance if you need an auditable provider; (3) test with non-sensitive inputs to confirm behavior; (4) if provenance/author trust matters, prefer skills with a known homepage or maintainer.

Like a lobster shell, security has layers — review code before you run it.

latestvk975evxdxk0gz702cvecajja9h8367v3

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments