tessl install github:jeremylongshore/claude-code-plugins-plus-skills --skill clay-ci-integrationgithub.com/jeremylongshore/claude-code-plugins-plus-skills
Configure Clay CI/CD integration with GitHub Actions and testing. Use when setting up automated testing, configuring CI pipelines, or integrating Clay tests into your build process. Trigger with phrases like "clay CI", "clay GitHub Actions", "clay automated tests", "CI clay".
Review Score
88%
Validation Score
11/16
Implementation Score
88%
Activation Score
90%
Set up CI/CD pipelines for Clay integrations with automated testing.
Create .github/workflows/clay-integration.yml:
name: Clay Integration Tests
on:
push:
branches: [main]
pull_request:
branches: [main]
env:
CLAY_API_KEY: ${{ secrets.CLAY_API_KEY }}
jobs:
test:
runs-on: ubuntu-latest
env:
CLAY_API_KEY: ${{ secrets.CLAY_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:integrationgh secret set CLAY_API_KEY --body "sk_test_***"describe('Clay Integration', () => {
it.skipIf(!process.env.CLAY_API_KEY)('should connect', async () => {
const client = getClayClient();
const result = await client.healthCheck();
expect(result.status).toBe('ok');
});
});| 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 |
on:
push:
tags: ['v*']
jobs:
release:
runs-on: ubuntu-latest
env:
CLAY_API_KEY: ${{ secrets.CLAY_API_KEY_PROD }}
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: '20'
- run: npm ci
- name: Verify Clay production readiness
run: npm run test:integration
- run: npm run build
- run: npm publishrequired_status_checks:
- "test"
- "clay-integration"For deployment patterns, see clay-deploy-integration.