Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Perplexity AI Search - security-hardened version (bash-based)
v1.0.1Use Perplexity API for web-grounded AI search. Use when user needs up-to-date information with source citations, factual queries about current events, or research-style answers. Default when user mentions Perplexity or needs current information with references.
⭐ 0· 826·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
high confidencePurpose & Capability
The skill's stated purpose is Perplexity web-grounded search and the code indeed implements a Perplexity API client. However the registry metadata claims no required environment variables or binaries, while the script requires an API key (PERPLEXITY_API_KEY or config.json) and depends on bash, curl, and python3. This mismatch between what the skill needs and what the registry declares is an incoherence a user should be aware of.
Instruction Scope
SKILL.md and the script keep behavior within the stated purpose: they build a JSON body, POST to the configured Perplexity endpoint, and parse citations. The runtime instructions do not ask the agent to read unrelated system files or other credentials. The skill documents mitigations for command-injection and process-list leakage, and the script largely follows those mitigations (passing user input via environment variables into python, validating inputs). Minor risks remain (temporary file use for the Authorization header; reliance on parsing response structure), but overall the instructions stay within scope.
Install Mechanism
No install spec is provided (instruction-only with an included script). That is low-risk from an installation perspective — nothing is downloaded or executed automatically beyond the provided script. The included code is readable and present in the package.
Credentials
The skill requires an API key (documented in SKILL.md and enforced by the script) and depends on curl and python3, but the registry metadata lists no required env vars or required binaries. The missing declaration of a sensitive credential (PERPLEXITY_API_KEY or config.json with apiKey) is the primary proportionality issue. The number of secrets requested is small and appropriate for the purpose, but it is not declared where the platform expects it.
Persistence & Privilege
The skill does not request permanent/force-included presence (always:false), does not modify other skills or global agent settings, and does not require elevated OS privileges. It writes a short-lived temp file for curl config (mode 600) and removes it; this is normal operational behavior, not a persistence privilege escalation.
What to consider before installing
This package is functionally consistent with a Perplexity API client and shows attention to common shell security issues, but pay attention to three things before installing/using it:
1) Metadata mismatch: the registry claims no required env vars or binaries, but the script needs an API key (PERPLEXITY_API_KEY or config.json) and requires bash, curl, and python3. Treat the API key as sensitive and do not provide it without confirming where the platform will store/use it.
2) Temporary auth file: the script writes the Authorization header to a temp file (mode 600) and deletes it; this reduces exposure but is not risk-free (race conditions, leftover files if the process is killed in unusual ways). If you are highly sensitive, review the script and consider running it in a sandbox or modifying it to use a more secure secret mechanism your environment provides.
3) Verify origin and endpoint: source and homepage are unknown. Confirm the endpoint (https://api.perplexity.ai/chat/completions) and the included code align with the published API and trustworthiness of the package owner. If you do not trust the publisher, run the script in an isolated environment or prefer an officially supported integration.
If you plan to install this skill: request the publisher update registry metadata to declare the required env var(s) and binaries, inspect the code yourself (or ask a colleague), and avoid supplying production API keys until you are confident in provenance.Like a lobster shell, security has layers — review code before you run it.
latestvk9709a0sq24t7gke3zqp1h7x8n8135nr
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
