paper-rewriter@5.14.0
CAUTION· static onlyPublisher claims: "Academic writing style toolkit, bilingual CN/EN: paper rewriting with AI-flavor self-check and style naturalization (scan reports are detection only), deterministic cleanup (model artifacts, punctuation, filler phrases), integrity guardrails (numbers, DOIs, PMIDs, terminology must survive untouched), and agent-guided revision for clearer, more natural academic prose. Built for scholars whose formal writing reads stiff, templated or machine-flavored — especially non-native (ESL) authors. Skip when: pure grammar polish, full-text translation, or rewriting unrelated to academic writing — use a dedicated tool. Includes AIGC-disclosure compliance checks (China 2025-09 labeling rules) and academic-integrity guardrails: this tool improves writing quality for self-review; it does not help misrepresent authorship, conceal required AI disclosure, or defeat integrity review. 100% local, zero upload, Python stdlib only. Related: paper-polisher-pro (broad polishing), pubmed-verifier, cite-holmes, academic-figures." Observed in sandbox: static analysis only — behavior not yet observed.
Coverage
Static only; nothing was run yet.The label rests on the code, the instruction files and the publisher. The honeypot run replaces this verdict when it completes.
What changed since 5.11.0
vet-skills diff paper-rewriter 5.11.0 5.14.0In the sandbox, this version reached for nothing 5.11.0 did not. Compared from the two recorded runs, not from source.
5.14.0 was not run in the sandbox (static only); the comparison covers what static analysis recorded only.
The guard can hold an update like this until someone approves it (runtime.on_change: hold). A change that only shows with a real credential, or on a path the run did not reach, is not in a trace and so not in this comparison.
Is [email protected] safe to install?
KillerSkills analysed it statically (a sandbox run is pending) on 2026-11-17 and scored it 69/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Summary: static analysis only — behavior not yet observed.
Behavior trace
Queued for honeypot run · static analysis onlyThis version has not been detonated yet. The score above counts behavior as unknown (50/100), so it cannot read Verified until the honeypot run completes and replaces this verdict.
Static findings
_DASHES = "\u2010\u2012\u2013\u2014\u2015\u2212" # hyphen bullet / figure / en / em / horizontal bar / math minusFix: Put hosts, commands and strings in plain source. Decoding at runtime looks identical to malware and costs points on its own.No other findings across 12,213 lines in 48 files.
Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.
What would make this Verified
11 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim docsor1212: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Unicode escape sequence detected≈ +2 on the totalPut hosts, commands and strings in plain source. Decoding at runtime looks identical to malware and costs points on its own.