clay-ci-integration
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".
When & Why to Use This Skill
This Claude skill automates the configuration of CI/CD pipelines for Clay integrations using GitHub Actions. It streamlines the setup of automated testing environments, secure secret management, and robust deployment workflows to ensure code quality and reliable integration with Clay's API.
Use Cases
- Automating the creation of GitHub Actions workflows to run Clay integration tests on every push or pull request.
- Securely configuring Clay API keys and environment secrets across development and production environments using the GitHub CLI.
- Implementing branch protection rules that require successful Clay integration test passes before code can be merged.
- Setting up automated release pipelines that verify Clay production readiness before publishing packages or deploying updates.
| name | clay-ci-integration |
|---|---|
| description | | |
| allowed-tools | Read, Write, Edit, Bash(gh:*) |
| version | 1.0.0 |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
Clay CI Integration
Overview
Set up CI/CD pipelines for Clay integrations with automated testing.
Prerequisites
- GitHub repository with Actions enabled
- Clay test API key
- npm/pnpm project configured
Instructions
Step 1: Create GitHub Actions Workflow
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:integration
Step 2: Configure Secrets
gh secret set CLAY_API_KEY --body "sk_test_***"
Step 3: Add Integration Tests
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');
});
});
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
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 publish
Branch Protection
required_status_checks:
- "test"
- "clay-integration"
Resources
Next Steps
For deployment patterns, see clay-deploy-integration.