Propose a patch

Evidence

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

diff --git a/skills/encode-skill/SKILL.md b/skills/encode-skill/SKILL.md
--- a/skills/encode-skill/SKILL.md
+++ b/skills/encode-skill/SKILL.md
@@ -26,1 +26,0 @@
-…t","format":"json"},"headers":{"Accept":"application/json"}}` - `{"base_url":"https://www.encodeproject.org","path":"search/","params":{"type":"Experiment","assay_term_name":"RNA-seq","limit":10,"format":"json"},"record_path":"@graph","headers":{"Accept":"application/json"},"max_items":10}` ## Output - Suc…
@@ -35,1 +34,0 @@
-…with `error.code` and `error.message`. ## Execution ```bash echo '{"base_url":"https://www.encodeproject.org","path":"search/","params":{"type":"Experiment","assay_term_name":"RNA-seq","limit":10,"format":"json"},"record_path":"@graph","headers":{"Accept":"application/json"},"max_items":10}' | python scripts…

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: life-science-database-query: URL with embedded credentials (KillerSkills verdict caution 65)

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

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/clawhub/life-science-database-query/1.0.0

## Findings with a location
- `skills/encode-skill/SKILL.md:35` · URL with embedded credentials — skills/encode-skill/SKILL.md:35 · URL with embedded credentials — may be phishing or credential leaking
- `skills/encode-skill/SKILL.md:26` · URL with embedded credentials — skills/encode-skill/SKILL.md:26 · URL with embedded credentials — may be phishing or credential leaking

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