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
@@ -851,1 +851,0 @@
-- `--npm` writes a `//{host}{path}/:_authToken` entry to `~/.npmrc`; you must still configure `registry=` or `@scope:registry=` to point npm at the registry.
@@ -881,1 +880,0 @@
-…ME/.docker}/config.json`, `~/.m2/settings.xml`, `~/.gradle/gradle.properties`, `~/.npmrc`, `~/.yarnrc.yml`, or the sbt destination files listed above (or the explicit `…
@@ -1382,1 +1380,0 @@
-Pass credentials by their supported file flags, or by an already securely provisioned environment; never put values in argv, shell assignments captured in history, or output:
@@ -1898,1 +1895,0 @@
-…fig access The snap uses the manual-connect `dot-kube-config` plug, scoped to `~/.kube/config` and `~/.kube/config.lock`, rather than the whole `.kube` directory. A differen…
@@ -2374,1 +2370,0 @@
-… not apply `NO_PROXY`, while Cargo does. Review the actual destination and keep proxy credentials out of argv/output. Maven downloads through a mirror are matched against known…
@@ -4544,1 +4539,0 @@
-- Do not pass credentials manually on the command line or in logs.
@@ -6685,1 +6679,0 @@
-- ✅ Public keys: `~/.ssh/id_rsa.pub`, `~/.ssh/id_ed25519.pub` (`.pub` extension)

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 1.13.39. 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: gitlab-cli-skills: References a credential file in the home directory (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: no network, touches nothing outside the project, writes no memory.

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/clawhub/gitlab-cli-skills/1.13.39

## Findings with a location
- `SKILL.md:851` · References a credential file in the home directory — SKILL.md:851 · References a credential file in the home directory
- `SKILL.md:881` · References a credential file in the home directory — SKILL.md:881 · References a credential file in the home directory
- `SKILL.md:4544` · Credential pass-through configuration — SKILL.md:4544 · Credential pass-through configuration — agent relays sensitive credentials
- `SKILL.md:1898` · References a credential file in the home directory — SKILL.md:1898 · References a credential file in the home directory
- `SKILL.md:2374` · Credential pass-through configuration — SKILL.md:2374 · Credential pass-through configuration — agent relays sensitive credentials
- `SKILL.md:6685` · References a credential file in the home directory — SKILL.md:6685 · References a credential file in the home directory
- `SKILL.md:1382` · Credential pass-through configuration — SKILL.md:1382 · Credential pass-through configuration — agent relays sensitive credentials

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