๐Ÿ“… let's chat! explore the endless possibilities creating industries that don't exist. click here

perplexity-ci-integration

Configure Perplexity CI/CD integration with GitHub Actions and testing. 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". allowed-tools: Read, Write, Edit, Bash(gh:*) version: 1.0.0 license: MIT author: Jeremy Longshore <jeremy@intentsolutions.io>

Allowed Tools

No tools specified

Provided by Plugin

perplexity-pack

Claude Code skill pack for Perplexity (30 skills)

saas packs v1.0.0
View Plugin

Installation

This skill is included in the perplexity-pack plugin:

/plugin install perplexity-pack@claude-code-plugins-plus

Click to copy

Instructions

# Perplexity CI Integration ## Overview Set up CI/CD pipelines for Perplexity integrations with automated testing. ## Prerequisites - GitHub repository with Actions enabled - Perplexity test API key - npm/pnpm project configured ## Instructions ### Step 1: Create GitHub Actions Workflow Create `.github/workflows/perplexity-integration.yml`: ```yaml name: Perplexity Integration Tests on: push: branches: [main] pull_request: branches: [main] env: PERPLEXITY_API_KEY: ${{ secrets.PERPLEXITY_API_KEY }} jobs: test: runs-on: ubuntu-latest env: PERPLEXITY_API_KEY: ${{ secrets.PERPLEXITY_API_KEY }} steps: - uses: actions/checkout@v4 - uses: actions/setup-node@v4 with: node-version: '20' cache: 'npm' - run: npm ci - run: npm test -- --coverage - run: npm run test:integration ``` ### Step 2: Configure Secrets ```bash gh secret set PERPLEXITY_API_KEY --body "sk_test_***" ``` ### Step 3: Add Integration Tests ```typescript describe('Perplexity Integration', () => { it.skipIf(!process.env.PERPLEXITY_API_KEY)('should connect', async () => { const client = getPerplexityClient(); const result = await client.healthCheck(); expect(result.status).toBe('ok'); }); }); ``` ## Output - Automated test pipeline - PR checks configured - Coverage reports uploaded - Release workflow ready ## Error Handling | Issue | Cause | Solution | |-------|-------|----------| | Secret not found | Missing configuration | Add secret via `gh secret set` | | Tests timeout | Network issues | Increase timeout or mock | | Auth failures | Invalid key | Check secret value | ## Examples ### Release Workflow ```yaml on: push: tags: ['v*'] jobs: release: runs-on: ubuntu-latest env: PERPLEXITY_API_KEY: ${{ secrets.PERPLEXITY_API_KEY_PROD }} steps: - uses: actions/checkout@v4 - uses: actions/setup-node@v4 with: node-version: '20' - run: npm ci - name: Verify Perplexity production readiness run: npm run test:integration - run: npm run build - run: npm publish ``` ### Branch Protection ```yaml required_status_checks: - "test" - "perplexity-integration" ``` ## Resources - [GitHub Actions Documentation](https://docs.github.com/en/actions) - [Perplexity CI Guide](https://docs.perplexity.com/ci) ## Next Steps For deployment patterns, see `perplexity-deploy-integration`.

Skill file: plugins/saas-packs/perplexity-pack/skills/perplexity-ci-integration/SKILL.md