Sci Translation Polish
v1.0.1Convert Chinese academic papers to native-level publication-ready English. Supports Nature/IEEE/ACM/APA styles. Uses a three-layer decoupling method (semanti...
⭐ 0· 74·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
Capability signals
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
OpenClaw
Benign
medium confidencePurpose & Capability
Name, description and the included documents (workflow, examples, style guides) align with a translation/polishing skill. There are no unexpected binaries, credentials, or config paths requested — nothing disproportionate to the stated purpose.
Instruction Scope
SKILL.md is explicit and prescriptive about a 6-step workflow for converting Chinese academic writing to publication-ready English and contains many examples and reference guides. One runtime instruction asks the agent to 'Use this skill whenever the user mentions academic paper translation, SCI paper writing, journal submission, research paper polishing, or needs to convert Chinese academic content to English for international publication, even if they don't explicitly ask for "translation" or "polishing".' That broad trigger guidance can lead to unsolicited activation in loosely related conversations — this is scope creep (behavioral, not code-level) and worth reviewing for privacy/consent implications. Otherwise the instructions do not request system files, env vars, or external endpoints beyond normal text processing.
Install Mechanism
No install spec, no downloads or executables — instruction-only skill. This is the lowest-risk install profile: nothing is written to disk or fetched at install time.
Credentials
The skill requires no environment variables, credentials, or config paths. All declared resources (none) are proportional to a text-only translation/polishing task.
Persistence & Privilege
Flags show always:false and normal autonomous invocation allowed. There is no request for permanent presence or to modify other skills/config. The only notable runtime policy is the broad auto-trigger instruction inside SKILL.md, but that is a usage instruction rather than a platform-level privilege escalation.
Assessment
This skill is internally coherent for its stated purpose: it's a text-only academic translation/polishing guide with many examples and no code, no installs, and no credential access. Before installing, consider: (1) provenance — the source/homepage is missing and owner identity is opaque, so if you require auditable origin prefer skills with known authors. (2) Consent and activation scope — SKILL.md tells the agent to activate on a wide range of user mentions (even when users don't explicitly ask for translation); if you are uncomfortable with automatic activation, configure the agent to require explicit user invocation. (3) Data sensitivity — the skill will process whatever text you provide; do not submit unpublished, proprietary, or personally identifying data unless you trust the deployment environment. (4) Quality checks — outputs can rewrite meaning when restructuring; always verify technical facts, numerical values, and citations in the produced English, and check that coined terminology/definitions are acceptable for your field. If you want higher assurance, ask the skill author for a public homepage, contact info, or a provenance record before adoption.Like a lobster shell, security has layers — review code before you run it.
latestvk970fhzvfgw5y5xn1z9x6efpcx84gwtt
License
MIT-0
Free to use, modify, and redistribute. No attribution required.