ClawHub
Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

Pinecone

v1.0.0

Pinecone vector database — manage indexes, upsert vectors, query similarity search, manage namespaces, and track collections via the Pinecone API. Build sema...

⭐ 0· 327·6 current·6 all-time
by@aiwithabidi
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Suspicious
View report →
OpenClawOpenClaw
Suspicious
medium confidence
ℹ
Purpose & Capability
Name, description, and declared PINECONE_API_KEY requirement align with a Pinecone CLI. However, the implementation contains many incorrect HTTP methods/paths (e.g., upsert/query using GET, unusual /index vs /indexes usage) suggesting the code is buggy or not the official Pinecone API shape. These are coherence/quality issues but do not by themselves imply malicious intent.
!
Instruction Scope
SKILL.md states requests go directly to Pinecone and that nothing is stored locally, but the script will try to read a local .env file at WORKSPACE or ~/.openclaw/workspace/.env to extract PINECONE_API_KEY if the environment variable is absent. That local-file access is not declared in the metadata and is a scope mismatch (it reads user files to obtain credentials).
✓
Install Mechanism
No install spec is provided (instruction-only with an included script). This is low-risk from an installation perspective because nothing arbitrary is downloaded or written by an installer.
ℹ
Credentials
The only declared credential is PINECONE_API_KEY, which is appropriate. However, the script also reads WORKSPACE (to locate a .env file) and will parse that file for PINECONE_API_KEY if the env var is missing; those additional environment/config accesses are not declared in requires.env and may expose or depend on local files containing secrets.
✓
Persistence & Privilege
The skill does not request always:true, does not modify other skills, and does not attempt to persist or enable itself. It runs as a normal, user-invoked CLI script.
What to consider before installing
This skill's purpose (Pinecone CLI) is reasonable and the single required secret (PINECONE_API_KEY) matches the purpose — but the script reads a local .env file at WORKSPACE or ~/.openclaw/workspace/.env to find that key if the environment variable is missing. That local-file access is not documented in SKILL.md. Actionable steps before installing or using: 1) Inspect or run the script in an isolated environment (container/VM). 2) If you store secrets in ~/.openclaw/workspace/.env, be aware the skill will read it; consider rotating the Pinecone key or removing it from that file. 3) Ask the publisher to declare the .env fallback in SKILL.md (or remove the fallback) and to fix the HTTP method/path bugs — the current implementation appears buggy and may fail or behave unexpectedly. 4) If you don't trust the author, avoid installing; else test with a limited-scoped Pinecone key and monitor network requests. If you want, I can point out the exact lines to change to remove the .env fallback and to correct the API calls.

Like a lobster shell, security has layers — review code before you run it.

latestvk97a7hyr8kvvf8npwt1mwkvyj582dzyz

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Runtime requirements

🌲 Clawdis
EnvPINECONE_API_KEY
Primary envPINECONE_API_KEY

Comments