Propose a patch

Evidence

The sandbox observed nothing beyond the static findings; the proposal cites those.

diff --git a/scripts/publish-work.mjs b/scripts/publish-work.mjs
--- a/scripts/publish-work.mjs
+++ b/scripts/publish-work.mjs
@@ -68,1 +68,0 @@
-// readFileSync utf8 会把它带进字符串 → JSON.parse 报 "Unexpected token "（Windows 常见）。
diff --git a/scripts/strip-git-credential.mjs b/scripts/strip-git-credential.mjs
--- a/scripts/strip-git-credential.mjs
+++ b/scripts/strip-git-credential.mjs
@@ -6,1 +6,0 @@
-//   `https://oauth2:[email protected]/<ns>/<repo>.git`）。若不经剥离就随发布把自己打进作品陈列馆，token 会泄露。
@@ -53,1 +52,0 @@
-// 二次剥离（幂等，防止形如 https://a:b:c@ 的残留）

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 1.0.0. If the behavior is intended, declare it (host under permissions.network, a line in the README) instead of removing it; the next crawl scores declarations.

Issue / PR body

Title: huawei-cloud-publish-work-to-gallery: Hidden zero-width characters detected (KillerSkills verdict caution 51)

## What the honeypot observed
KillerSkills ran **[email protected]** in an isolated sandbox (decoy credentials, recording proxy, syscall trace; engine 1.8.1) and scored it **CAUTION 51/100**. Summary: static analysis only — behavior not yet observed.

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/clawhub/huawei-cloud-publish-work-to-gallery/1.0.0

## Findings with a location
- `scripts/publish-work.mjs:68` · Hidden zero-width characters detected — scripts/publish-work.mjs:68 · Hidden zero-width characters detected — may conceal content
- `scripts/strip-git-credential.mjs:6` · URL with embedded credentials — scripts/strip-git-credential.mjs:6 · URL with embedded credentials — may be phishing or credential leaking
- `scripts/strip-git-credential.mjs:53` · URL with embedded credentials — scripts/strip-git-credential.mjs:53 · URL with embedded credentials — may be phishing or credential leaking

## Proposed change
The attached patch removes the 3 lines above. If the behavior is intended, the fix is to declare it instead: list the host under `permissions.network` (or the MCP manifest) and say in the README why the package needs it; the next crawl will re-score it with the declaration taken into account.

## How this will be verified
Nothing is "verified safe" by assertion. When a new version is published, KillerSkills re-runs it in the honeypot and the verdict page updates; you can trigger it early from the verdict page ("Re-scan after I publish a fix"). Reply here or at [email protected] if you believe the verdict is wrong; disputes are reviewed by a person and the outcome is published on the verdict page.

_Proposed through killerskills.ai/threats by a user of the package, under their own GitHub account. The evidence is public; the package was never modified by KillerSkills._