perplexity-multi-env-setup
A configuration strategy for managing Perplexity API keys and model routing across environment tiers.
Install
mkdir -p .claude/skills/perplexity-multi-env-setup && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/2755" && unzip -o skill.zip -d .claude/skills/perplexity-multi-env-setup && rm skill.zipInstalls to .claude/skills/perplexity-multi-env-setup
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Configure Perplexity Sonar API across development, staging, and productionKey capabilities
- →Define environment-specific configurations for Perplexity API
- →Control allowed models (sonar vs sonar-pro) per environment
- →Set rate limits and cost caps for development, staging, and production
- →Integrate with secret managers for production API keys
- →Route models based on query depth (quick or deep)
How it works
The skill uses an environment resolver to load configurations based on the current environment. It then applies environment-specific settings for API keys, models, rate limits, and cost caps.
Inputs & outputs
When to use perplexity-multi-env-setup
- →Isolate Perplexity API keys by environment
- →Apply model cost caps per environment
- →Configure environment-specific search limits
- →Standardize API integration across deployment stages
About perplexity-multi-env-setup
This skill defines an environment-based configuration structure for Perplexity Sonar API. It helps manage API keys, rate limits, and model access for development, staging, and production.
Configure Perplexity across development, staging, and production environments. Use when setting up multi-environment deployments, configuring per-environment secrets, or implementing environment-specific Perplexity configurations. Trigger with phrases like "perplexity environments", "perplexity staging", "perplexity dev prod", "perplexity environment setup", "perplexity config by env".
When not to use it
- →When only a single environment is used for Perplexity API integration
- →When Perplexity API keys and configurations do not need to be isolated
Prerequisites
Limitations
- →The skill requires separate Perplexity API keys for each environment
- →The skill requires setting deepModel: "sonar" in dev config to restrict models
- →The skill requires ensuring NODE_ENV=development is set to avoid high dev costs
How it compares
This skill provides a structured approach to manage Perplexity API configurations across multiple environments, unlike a single, hardcoded configuration.
Compared to similar skills
perplexity-multi-env-setup side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| perplexity-multi-env-setup (this skill) | 2 | 2mo | Review | Intermediate |
| deepgram-performance-tuning | 3 | 2mo | Review | Intermediate |
| graphql | 6 | 8mo | No flags | Advanced |
| guidewire-sdk-patterns | 2 | 2mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by jeremylongshore
View all by jeremylongshore →You might also like
deepgram-performance-tuning
jeremylongshore
Optimize Deepgram API performance for faster transcription and lower latency. Use when improving transcription speed, reducing latency, or optimizing audio processing pipelines. Trigger with phrases like "deepgram performance", "speed up deepgram", "optimize transcription", "deepgram latency", "deepgram faster".
graphql
davila7
GraphQL gives clients exactly the data they need - no more, no less. One endpoint, typed schema, introspection. But the flexibility that makes it powerful also makes it dangerous. Without proper controls, clients can craft queries that bring down your server. This skill covers schema design, resolvers, DataLoader for N+1 prevention, federation for microservices, and client integration with Apollo/urql. Key insight: GraphQL is a contract. The schema is the API documentation. Design it carefully.
guidewire-sdk-patterns
jeremylongshore
Master Guidewire SDK patterns including Digital SDK, REST API Client, and Gosu best practices. Use when implementing integrations, building frontends with Jutro, or writing server-side Gosu code. Trigger with phrases like "guidewire sdk", "digital sdk", "jutro sdk", "guidewire patterns", "gosu best practices", "rest api client".
groq-performance-tuning
jeremylongshore
Optimize Groq API performance with caching, batching, and connection pooling. Use when experiencing slow API responses, implementing caching strategies, or optimizing request throughput for Groq integrations. Trigger with phrases like "groq performance", "optimize groq", "groq latency", "groq caching", "groq slow", "groq batch".
openrouter-streaming-setup
jeremylongshore
Implement streaming responses with OpenRouter. Use when building real-time chat interfaces or reducing time-to-first-token. Trigger with phrases like 'openrouter streaming', 'openrouter sse', 'stream response', 'real-time openrouter'.
serving-llms-vllm
davila7
Serves LLMs with high throughput using vLLM's PagedAttention and continuous batching. Use when deploying production LLM APIs, optimizing inference latency/throughput, or serving models with limited GPU memory. Supports OpenAI-compatible endpoints, quantization (GPTQ/AWQ/FP8), and tensor parallelism.