From perplexity-pack
Create a minimal working Perplexity example. Use when starting a new Perplexity integration, testing your setup, or learning basic Perplexity API patterns. Trigger with phrases like "perplexity hello world", "perplexity example", "perplexity quick start", "simple perplexity code".
How this skill is triggered — by the user, by Claude, or both
Slash command
/perplexity-pack:perplexity-hello-worldThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Minimal working example demonstrating core Perplexity functionality.
Minimal working example demonstrating core Perplexity functionality.
perplexity-install-auth setupCreate a new file for your hello world example.
import { PerplexityClient } from '@perplexity/sdk';
const client = new PerplexityClient({
apiKey: process.env.PERPLEXITY_API_KEY,
});
async function main() {
// Your first API call here
}
main().catch(console.error);
Success! Your Perplexity connection is working.
| Error | Cause | Solution |
|---|---|---|
| Import Error | SDK not installed | Verify with npm list or pip show |
| Auth Error | Invalid credentials | Check environment variable is set |
| Timeout | Network issues | Increase timeout or check connectivity |
| Rate Limit | Too many requests | Wait and retry with exponential backoff |
import { PerplexityClient } from '@perplexity/sdk';
const client = new PerplexityClient({
apiKey: process.env.PERPLEXITY_API_KEY,
});
async function main() {
// Your first API call here
}
main().catch(console.error);
from perplexity import PerplexityClient
client = PerplexityClient()
# Your first API call here
Proceed to perplexity-local-dev-loop for development workflow setup.
npx claudepluginhub aiminnovations/claude-code-plugins-plus --plugin perplexity-packGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Synthesizes the current conversation into a structured spec (PRD) and publishes it to the project issue tracker with a ready-for-agent label, without interviewing the user.
7plugins reuse this skill
First indexed Jul 11, 2026
Showing the 6 earliest of 7 plugins