Propose a patch

Evidence

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

diff --git a/SKILL.md b/SKILL.md
--- a/SKILL.md
+++ b/SKILL.md
@@ -171,1 +171,0 @@
-| 🧑‍⚖️ 结果性质 | **🚨 禁止**做"营养不良 / 黑斑病 / 黑变病 / 寄生虫 / 应激综合征 / 缺乏类胡萝卜素"等具体疾病诊断 |
@@ -179,1 +178,0 @@
-| 🧑‍⚖️ 结果性质 | **必须**做白平衡校正与光照归一化（基于白参考估算光照色温 K），**未做白平衡的评分一律视为不可信** → 返回 `color_signal_unreliable` |
@@ -181,1 +179,0 @@
-| 🧑‍⚖️ 结果性质 | **必须**在白参考未检出 / 分割置信度 < 0.7 / 光照过暗或过曝 / 鱼体姿态侧面不可见时返回 `color_signal_unreliable` 并建议重拍/补光/放置白卡 |

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 1.0.13. 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: smyx-fish-color-brightness-assessment-analysis: Hidden zero-width characters detected (KillerSkills verdict caution 62)

## 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 62/100**. Summary: static analysis only — behavior not yet observed.

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/clawhub/smyx-fish-color-brightness-assessment-analysis/1.0.13

## Findings with a location
- `SKILL.md:171` · Hidden zero-width characters detected — SKILL.md:171 · Hidden zero-width characters detected — may conceal content
- `SKILL.md:181` · Hidden zero-width characters detected — SKILL.md:181 · Hidden zero-width characters detected — may conceal content
- `SKILL.md:179` · Hidden zero-width characters detected — SKILL.md:179 · Hidden zero-width characters detected — may conceal content

## 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._