Propose a patch

Evidence

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

diff --git a/readme.md b/readme.md
--- a/readme.md
+++ b/readme.md
@@ -134,1 +134,0 @@
-<summary><b>Q：运行报错，提示无权限 / 退出码 3？</b></summary> A：环境变量未配置或 Token 格式不对（需 16–256 位，仅字母、数字、下划线、连字符）。 ```bash # Windows set GUAIKEI_API_TOKEN=你的TOKEN # macOS / Linu
@@ -171,1 +170,0 @@
-<summary><b>Q：报错 `PLAN_LIMIT` / 提示包月受限？</b></summary> A：技能侧硬上限仍是 10000 条/次（按量 Token）。**包月 Token** 搜索/作品最多 30、评论最多 40，超限返回 `PLAN_LIMIT`（退出码 1），不要当网络错误同参重试。可降 `--
@@ -185,1 +183,0 @@
-<summary><b>Q：会不会泄露我的 Token？</b></summary> A：Token 只从环境变量读取，不会出现在 stdout、日志文件或错误信息中。调用时会随请求头发送到数据服务 `www.guaikei.com`（这是数据获取的必要环节）。

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 1.1.1. 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: tiktok-record-organizer: Collapsed <details> block carrying instructions (KillerSkills verdict caution 64)

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

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/clawhub/tiktok-record-organizer/1.1.1

## Findings with a location
- `readme.md:134` · Collapsed <details> block carrying instructions — readme.md:134 · Collapsed <details> block carrying instructions
- `readme.md:171` · Collapsed <details> block carrying instructions — readme.md:171 · Collapsed <details> block carrying instructions
- `readme.md:185` · Collapsed <details> block carrying instructions — readme.md:185 · Collapsed <details> block carrying instructions

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