Japanese

v1.0.0

Write Japanese that sounds human. Not formal, not robotic, not AI-generated.

2· 952·2 current·2 all-time
byIván@ivangdavila
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 name and description (make Japanese sound human/casual) match the SKILL.md content. There are no unrelated requirements (no env vars, binaries, or external services) that would be unnecessary for the stated purpose.
Instruction Scope
The runtime instructions are confined to stylistic guidance for generating Japanese (formality, particles, contractions, slang, etc.). They do not instruct the agent to read files, access environment variables, call external endpoints, or collect unrelated system data. Note: the guidance explicitly encourages colloquial and potentially coarse language (slang, swear words, gendered speech), so outputs should be reviewed for appropriateness.
Install Mechanism
No install spec is present (instruction-only). Nothing is written to disk or fetched during install, which minimizes execution risk.
Credentials
The skill requests no environment variables, credentials, or config paths. This is proportional to its stated purpose of providing stylistic instructions for text generation.
Persistence & Privilege
always is false and the skill is user-invocable; it does not request permanent presence or elevated platform privileges. Autonomous invocation is allowed by default but is not combined with other concerning indicators.
Assessment
This skill is internally consistent and low-risk from a technical standpoint. Practical advice before installing or using it: (1) Test outputs with native speakers for tone and naturalness, (2) Review results for offensive or inappropriate slang (the guide encourages informal and coarse language), (3) Avoid using this skill for formal/legal/medical/official communications where politeness and accuracy matter, and (4) If you need strict neutrality or adherence to formal registers, prefer a different skill or explicit instructions to stay formal.

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

latestvk970s2sg7hqnyvdy0rqhyngxw180xtbf

License

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

Comments