Propose a patch

Evidence

• Contacted release-assets.githubusercontent.com: not declared and not needed for the documented job.

diff --git a/SKILL.md b/SKILL.md
--- a/SKILL.md
+++ b/SKILL.md
@@ -61,1 +61,0 @@
-| Recall, freshness, verified write-back, source ingest | `references/active-memory.md` |

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: using-lwc: Contacted release-assets.githubusercontent.com: not declared and not needed for the documented job (KillerSkills verdict caution 68)

## 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 68/100**. Summary: sends data to release-assets.githubusercontent.com.

- Contacted release-assets.githubusercontent.com: not declared and not needed for the documented job.

Full trace and findings: https://killerskills.ai/skills/clawhub/using-lwc/1.0.0

## Findings with a location
- `SKILL.md:61` · Instructs the agent to modify its persistent memory or instruction files — SKILL.md:61 · Instructs the agent to modify its persistent memory or instruction files

## Proposed change
The attached patch removes the 1 line 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._