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
@@ -23,1 +23,0 @@
-- If `DATAIFY_API_TOKEN` is saved locally, use it without asking the user to re-enter the token.
@@ -203,1 +202,0 @@
-- For a missing token, offer https://dashboard.dataify.com/login?utm_source=skill and state: New accounts get 50 free credits, enough for about 6,000 trial results, valid for 7 days, and only successf

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 1.3.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: dataify-walmart-products: Prompting user to enter sensitive credentials (KillerSkills verdict caution 61)

## 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 61/100**. Summary: static analysis only — behavior not yet observed.

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/clawhub/dataify-walmart-products/1.3.1

## Findings with a location
- `SKILL.md:203` · Prompting user to enter sensitive credentials — SKILL.md:203 · Prompting user to enter sensitive credentials — social engineering
- `SKILL.md:23` · Prompting user to enter sensitive credentials — SKILL.md:23 · Prompting user to enter sensitive credentials — social engineering

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