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".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill clay-ci-integration91
Quality
88%
Does it follow best practices?
Impact
100%
1.58xAverage score across 3 eval scenarios
GitHub Actions CI workflow setup
Correct workflow file path
100%
100%
Push and PR triggers on main
66%
100%
CLAY_API_KEY at workflow level
0%
100%
CLAY_API_KEY at job level
28%
100%
ubuntu-latest runner
100%
100%
Node.js version 20
100%
100%
npm cache enabled
100%
100%
npm ci for install
100%
100%
Tests with coverage flag
25%
100%
Separate integration test step
62%
100%
gh secret set command
37%
100%
skipIf API key pattern
20%
100%
getClayClient usage
0%
100%
Without context: $0.2856 · 1m 4s · 20 turns · 20 in / 3,800 out tokens
With context: $0.3511 · 1m 20s · 21 turns · 177 in / 3,787 out tokens
Release workflow with production secrets
Tag-based trigger
100%
100%
ubuntu-latest runner
100%
100%
Node.js version 20
100%
100%
CLAY_API_KEY_PROD secret name
0%
100%
Production key in env block
50%
100%
Integration tests before build
100%
100%
Build before publish
100%
100%
npm ci for install
100%
100%
Correct trigger documented
100%
100%
Production secret name documented
0%
100%
Without context: $0.1713 · 39s · 12 turns · 13 in / 2,175 out tokens
With context: $0.2017 · 48s · 15 turns · 171 in / 2,210 out tokens
Branch protection and repository configuration
Status check: 'test'
100%
100%
Status check: 'clay-integration'
0%
100%
Both checks present
20%
100%
Targets main branch
100%
100%
Uses gh CLI
100%
100%
branch-protection.yml present
100%
100%
Check names explained
66%
100%
Without context: $0.3471 · 1m 26s · 23 turns · 24 in / 4,689 out tokens
With context: $0.3894 · 1m 16s · 24 turns · 56 in / 4,240 out tokens
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.