perplexity-ci-integration
Configure CI/CD for Perplexity Sonar API integrations with GitHub Actions. Use when setting up automated testing, configuring CI pipelines, or integrating Perplexity tests into your build process. Trigger with phrases like "perplexity CI", "perplexity GitHub Actions", "perplexity automated tests", "CI perplexity pipeline". '
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill perplexity-ci-integration --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Perplexity CI Integration ## Overview Set up CI/CD pipelines for Perplexity Sonar API integrations. Key CI concerns: live API calls cost money (use mocks for unit tests, reserve live calls for integration tests), API keys must be in GitHub Secrets, and rate limits apply even in CI. ## Prerequisites - GitHub repository with Actions enabled - Perplexity API key for CI (separate from production) -
What does the perplexity-ci-integration skill do?
Configure CI/CD for Perplexity Sonar API integrations with GitHub Actions. Use when setting up automated testing, configuring CI pipelines, or integrating Perplexity tests into your build process. Trigger with phrases like "perplexity CI", "perplexity GitHub Actions", "perplexity automated tests", "CI perplexity pipeline". '
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill perplexity-ci-integration --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
