Propose a patch

Evidence

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

diff --git a/README.md b/README.md
--- a/README.md
+++ b/README.md
@@ -228,1 +228,0 @@
-<summary><b>Alternative: Configuration for Conda/Mamba/Micromamba</b></summary> If you installed with conda/mamba/micromamba, use the `run` command: ```json { "
@@ -254,1 +253,0 @@
-<summary><b>Alternative: Configuration for uv</b></summary> If you installed with uv, use `uv run`: ```json { "mcpServers": { "arangodb": { "command": "uv", "ar
diff --git a/docs/getting-started/quickstart.md b/docs/getting-started/quickstart.md
--- a/docs/getting-started/quickstart.md
+++ b/docs/getting-started/quickstart.md
@@ -121,1 +121,0 @@
-<summary><b>If you installed with Conda/Mamba/Micromamba</b></summary> Use: - `"command": "conda|mamba|micromamba"` - `"args": ["run", "-n", "mcp-arango", "maa"
@@ -131,1 +130,0 @@
-<summary><b>If you installed with uv</b></summary> Use: - `"command": "uv"` - `"args": ["run", "--directory", "/path/to/project", "maa", "server"]`

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.5.4. 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: mcp-arangodb-async: Collapsed <details> block carrying instructions (KillerSkills verdict caution 68)

## 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 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/pypi/mcp-arangodb-async/0.5.4

## Findings with a location
- `README.md:254` · Collapsed <details> block carrying instructions — README.md:254 · Collapsed <details> block carrying instructions
- `docs/getting-started/quickstart.md:131` · Collapsed <details> block carrying instructions — docs/getting-started/quickstart.md:131 · Collapsed <details> block carrying instructions
- `docs/getting-started/quickstart.md:121` · Collapsed <details> block carrying instructions — docs/getting-started/quickstart.md:121 · Collapsed <details> block carrying instructions
- `README.md:228` · Collapsed <details> block carrying instructions — README.md:228 · Collapsed <details> block carrying instructions

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