!
Purpose & Capability
The name/description claim Perplexity-powered, multi-tier web/academic/news/YouTube/Reddit search and the code indeed calls Perplexity's API. However registry metadata declares no required environment variables while SKILL.md and the script require a Perplexity API key (PERPLEXITY_API_KEY or PPLX_API_KEY) and will also try to read ~/.openclaw/openclaw.json for keys. The mismatch between declared requirements and actual behavior is incoherent and should be corrected.
!
Instruction Scope
SKILL.md instructs running the provided Python script which is consistent with the purpose. The runtime script however: (1) attempts to read the user's OpenClaw config at ~/.openclaw/openclaw.json (not documented in the registry metadata), (2) sets default Langfuse environment keys inside the process (hardcoded secrets), and (3) will attempt to use an optional langfuse client to trace observations — which may transmit query text and results to a tracing endpoint. Reading the user's config file and sending traces are beyond the narrow 'search' description unless explicitly disclosed.
ℹ
Install Mechanism
This is instruction + bundled script only (no install spec), which is low install-risk. The script requires third-party Python packages (requests; optionally langfuse) but these dependencies are not declared in the manifest. No external archive downloads or installers are used.
!
Credentials
The SKILL.md and code expect a Perplexity API key (PERPLEXITY_API_KEY or PPLX_API_KEY), but the registry metadata lists none — a concerning omission. The script also unilaterally sets LANGFUSE_SECRET_KEY and LANGFUSE_PUBLIC_KEY defaults (hardcoded secrets) and LANGFUSE_HOST to http://langfuse-web:3000; these embedded keys could enable telemetry/tracing to a third-party Langfuse instance without the user's explicit configuration or consent. The skill also searches for credentials in a local OpenClaw config file (~/.openclaw/openclaw.json), which increases the scope of local data access.
✓
Persistence & Privilege
The skill does not request always: true, does not modify system-wide settings, and does not persistently write configuration. It only sets process-level environment defaults and attempts to read a local config file for an API key. That read is scoped to a single file path (the OpenClaw config) rather than broad filesystem access.
What to consider before installing
Before installing or running this skill:
- Expect to supply a Perplexity API key (PERPLEXITY_API_KEY or PPLX_API_KEY); the registry metadata should state this but currently does not — ask the publisher to correct the manifest.
- Review the bundled script locally. It will try to read ~/.openclaw/openclaw.json for keys — if you don't want that, either remove that code or ensure the file contains no sensitive data.
- The script contains hardcoded Langfuse keys and a default LANGFUSE_HOST. These could cause your queries/results to be sent to a tracing/observability endpoint controlled by the publisher (or by the embedded host). If you are concerned about telemetry or data leakage, remove or override those env defaults before running, or run the skill in an isolated environment.
- Ensure you trust the author (agxntsix) and the included langfuse tracing behavior; request clarification on why default secret keys are embedded and what data is sent to Langfuse.
- Consider running the script in an ephemeral container or VM, or inspect network traffic, until you are satisfied the tracing endpoint and keys are safe.
If the publisher can (a) remove embedded keys, (b) update registry metadata to declare required env vars and dependencies, and (c) clearly document tracing behavior and opt-out, the incoherence and privacy concerns would be largely resolved.
