Perplexity Wrapped Search

The skill's name, description, CLI, and code all implement a Perplexity-based web search (sonar, search, agentic). That capability coheres with the required binary (node) and the network calls to api.perplexity.ai. However, the skill obviously needs a Perplexity API key at runtime (scripts/config.mjs reads PERPLEXITY_API_KEY) but the registry metadata lists no required env vars or primary credential — this is an important metadata omission/incoherence.

Runtime instructions and the bundled scripts stay within the declared purpose: they accept queries, call Perplexity endpoints, and wrap external content in untrusted-content boundaries. The code sanitizes boundary markers to mitigate prompt injection and prompts for confirmation on expensive 'deep' queries. The Agentic mode allows selecting third-party model names but sends them to Perplexity's endpoint (it does not request additional third-party credentials). There is no code that reads arbitrary files or other unrelated environment variables.

This is an instruction-only skill with small JS scripts and no install spec or external downloads. It requires node on PATH (declared). No installers or archive downloads are present, so install risk is low.

The runtime code requires a Perplexity API key (scripts/config.mjs reads PERPLEXITY_API_KEY and the main script exits if apiKey is missing). Yet requires.env and primary credential in the registry metadata are empty. Additionally, an error message mentions 1Password, but the included code does not implement 1Password access — another inconsistency. Requesting an API key for the service is proportionate, but failing to declare it in metadata is a mismatch that can confuse permission/configuration and is worth flagging.

The skill does not request persistent or privileged presence (always:false). It does not modify other skills or system-wide settings. It does not create background services or write persistent credentials; it only reads an environment variable at runtime.