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".
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
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-structured skill description with excellent trigger term coverage and completeness. The explicit 'Use when' and 'Trigger with phrases' sections provide clear guidance for skill selection. The main weakness is that the capabilities could be more specific about concrete actions beyond 'configure' and 'integrate'.
Suggestions
Add more specific concrete actions like 'create GitHub Actions workflow files', 'configure test runners', or 'set up build triggers' to improve specificity
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Clay CI/CD, GitHub Actions, testing) and some actions (configure integration, setting up automated testing, configuring CI pipelines), but lacks specific concrete actions like 'create workflow files', 'set up test runners', or 'configure build triggers'. | 2 / 3 |
Completeness | Clearly answers both what (configure Clay CI/CD integration with GitHub Actions and testing) and when (setting up automated testing, configuring CI pipelines, integrating Clay tests) with explicit 'Use when' clause and 'Trigger with phrases' guidance. | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger phrases users would say: 'clay CI', 'clay GitHub Actions', 'clay automated tests', 'CI clay'. Also includes terms like 'automated testing', 'CI pipelines', and 'build process' that users would naturally mention. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche combining Clay + CI/CD + GitHub Actions. The explicit trigger phrases with 'clay' prefix make it unlikely to conflict with generic CI/CD skills or other Clay-related skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, actionable skill with excellent conciseness and fully executable code examples. The main weakness is the lack of explicit validation steps in the workflow - there's no guidance on verifying the CI pipeline works correctly after setup or how to debug common setup issues beyond the error table.
Suggestions
Add a validation step after Step 3, such as 'Step 4: Verify Setup - Push a test commit and confirm the workflow runs: `gh run list --workflow=clay-integration.yml`'
Include a troubleshooting feedback loop: 'If the workflow fails on first run, check Actions tab for logs, verify secrets are set correctly with `gh secret list`, then re-run'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, providing only necessary configuration and code without explaining what GitHub Actions or CI/CD is. Every section serves a clear purpose with no padding. | 3 / 3 |
Actionability | Provides fully executable YAML workflows, bash commands, and TypeScript test code that are copy-paste ready. Includes specific file paths, secret configuration commands, and complete workflow examples. | 3 / 3 |
Workflow Clarity | Steps are clearly numbered and sequenced, but lacks explicit validation checkpoints. No feedback loop for verifying the workflow works before merging, and no guidance on what to do if the initial setup fails. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections (Overview, Prerequisites, Instructions, Examples). References external resources appropriately and points to related skill for deployment patterns. Content is appropriately scoped without being monolithic. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Reviewed
Table of Contents
Is this your skill?
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.