← tencentcloud-tke-skill@1.0.0

Propose a patch

A fix the maintainer can act on, with the evidence attached. It opens under your GitHub account in your browser; KillerSkills holds no token and never modifies the package. The fix is verified the only way we verify anything: the next crawl re-runs the new version in the honeypot. 78 · Caution

Evidence

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

Diff · removes 10 caught lines

Download .patch
diff --git a/k8s_cli.py b/k8s_cli.py
--- a/k8s_cli.py
+++ b/k8s_cli.py
@@ -52,1 +52,0 @@
-4. ~/.kube/config 默认路径
@@ -75,1 +74,0 @@
-# 4. ~/.kube/config 默认路径
@@ -76,1 +74,0 @@
-default_path = os.path.expanduser("~/.kube/config")
@@ -84,1 +81,0 @@
-"  4. 将 kubeconfig 放到 ~/.kube/config",
@@ -377,1 +373,0 @@
-target = getattr(args, 'kubeconfig', None) or os.getenv("KUBECONFIG") or os.path.expanduser("~/.kube/config")
diff --git a/SKILL.md b/SKILL.md
--- a/SKILL.md
+++ b/SKILL.md
@@ -26,1 +26,0 @@
-4. `~/.kube/config` 默认路径
@@ -342,1 +341,0 @@
-python {baseDirectory}/k8s_cli.py context-list --kubeconfig ~/.kube/config
@@ -347,1 +345,0 @@
-> 注意:此命令会修改 kubeconfig 文件中的 current-context 字段。仅适用于持久化的 kubeconfig 文件(--kubeconfig / KUBECONFIG 环境变量 / ~/.kube/config),不适用于通过 --cluster-id 自动获取的临时 kubeconfig。
@@ -351,1 +348,0 @@
-python {baseDirectory}/k8s_cli.py context-use production-context --kubeconfig ~/.kube/config
@@ -357,1 +353,0 @@
-python {baseDirectory}/k8s_cli.py context-current --kubeconfig ~/.kube/config

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: tencentcloud-tke-skill: References a credential file in the home directory (KillerSkills verdict caution 78)

## What the honeypot observed
KillerSkills ran **[email protected]** in an isolated sandbox (decoy credentials, recording proxy, syscall trace; engine 1.9.2) and scored it **CAUTION 78/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/tencentcloud-tke-skill/1.0.0

## Findings with a location
- `k8s_cli.py:52` · References a credential file in the home directory — k8s_cli.py:52 · References a credential file in the home directory
- `k8s_cli.py:76` · References a credential file in the home directory — k8s_cli.py:76 · References a credential file in the home directory
- `SKILL.md:357` · References a credential file in the home directory — SKILL.md:357 · References a credential file in the home directory
- `SKILL.md:26` · References a credential file in the home directory — SKILL.md:26 · References a credential file in the home directory
- `k8s_cli.py:377` · References a credential file in the home directory — k8s_cli.py:377 · References a credential file in the home directory
- `SKILL.md:342` · References a credential file in the home directory — SKILL.md:342 · References a credential file in the home directory
- `k8s_cli.py:75` · References a credential file in the home directory — k8s_cli.py:75 · References a credential file in the home directory
- `k8s_cli.py:84` · References a credential file in the home directory — k8s_cli.py:84 · References a credential file in the home directory
- `SKILL.md:347` · References a credential file in the home directory — SKILL.md:347 · References a credential file in the home directory
- `SKILL.md:351` · References a credential file in the home directory — SKILL.md:351 · References a credential file in the home directory

## Proposed change
The attached patch removes the 10 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._
No GitHub source is recorded for this package, so there is nothing to open; paste the body into the registry's support channel.

We count proposals opened, not merged: a merge shows up as a new version that the crawl re-runs. Disputes: the maintainer can contest the verdict from its page; a person reviews it and the outcome is published.