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
@@ -93,1 +93,0 @@
-| 9 | SSH Private Key | User input (path to key file, default: ~/.ssh/id_rsa) | — |
@@ -129,1 +128,0 @@
-- **SSH Private Key**: Path to private key file (e.g., `~/.ssh/id_rsa`).

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.0.1-beta.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: alibabacloud-network-connect-with-ipsec-vpn: References a credential file in the home directory (KillerSkills verdict caution 76)

## 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 76/100**. Summary: no network, touches nothing outside the project, writes no memory.

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/clawhub/alibabacloud-network-connect-with-ipsec-vpn/0.0.1-beta.1

## Findings with a location
- `SKILL.md:93` · References a credential file in the home directory — SKILL.md:93 · References a credential file in the home directory
- `SKILL.md:129` · References a credential file in the home directory — SKILL.md:129 · References a credential file in the home directory

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