clay-ci-integration

Configure CI/CD pipelines for Clay integrations with automated testing and validation. Use when setting up automated tests for Clay webhook handlers, validating enrichment data quality in CI, or integrating Clay checks into your build process. Trigger with phrases like "clay CI", "clay GitHub Actions", "clay automated tests", "CI clay", "test clay integration".

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

85%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable with executable code and clear sequenced validation checkpoints, but it is a monolithic file that embeds large complete artifacts inline rather than splitting them into referenced bundle files, slightly hurting conciseness and progressive disclosure.

Suggestions

Move the full workflow YAML, unit-test file, and schema validator into a references/ or scripts/ bundle and replace the inline blocks with concise excerpts plus links, improving both conciseness and progressive_disclosure.

Trim the Overview framing that restates what Claude can infer (e.g., the 'Since Clay is a web platform...' preamble) to keep the body lean.

Verify the referenced sibling skill 'clay-deploy-integration' exists or mark it as a planned/optional companion so the single cross-skill pointer is clearly signaled.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with executable code, but it includes some unnecessary padding Claude already knows (e.g., "Since Clay is a web platform (not a local service), CI focuses on:" framing and a restated overview), and inline full workflow YAML plus full test files could be tightened or referenced.	2 / 3
Actionability	It provides fully executable, copy-paste-ready GitHub Actions YAML, shell commands (gh secret set), complete TypeScript unit tests, and a runnable zod schema validator, matching the anchor for specific, complete examples.	3 / 3
Workflow Clarity	Steps are clearly sequenced (Step 1–5) with explicit validation checkpoints — the PII grep guard, schema validation, MAX_ROWS credit-budget guard, webhook connectivity check, and the error-handling table provide feedback loops for the batch/CI operations.	3 / 3
Progressive Disclosure	The skill is a single monolithic SKILL.md with no references/, scripts/, or assets/ bundle, and large inline blocks (full workflow YAML, full test file, full validator) that could be split out; navigation is limited to a terminal "Next Steps" pointer to a sibling skill, so it is not at the top anchor.	2 / 3
	Total	10 / 12 Passed

Description

100%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, well-structured description that names concrete actions, provides explicit use-when triggers, and uses a distinctive Clay-scoped vocabulary. It fully answers what and when with minimal fluff.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions — "setting up automated tests for Clay webhook handlers", "validating enrichment data quality in CI", and "integrating Clay checks into your build process" — matching the anchor for several specific concrete actions.	3 / 3
Completeness	It explicitly states what it does ("Configure CI/CD pipelines for Clay integrations with automated testing and validation") and provides an explicit "Use when..." clause plus "Trigger with phrases like...", clearly answering both what and when.	3 / 3
Trigger Term Quality	Trigger phrases like "clay CI", "clay GitHub Actions", "clay automated tests", "CI clay", and "test clay integration" are natural terms a user would say, giving good coverage; it is just below the broadest examples only because the set is somewhat narrow, but clearly meets the top anchor.	3 / 3
Distinctiveness Conflict Risk	The Clay-specific niche and Clay-prefixed trigger phrases make it clearly distinguishable from other CI/testing skills and unlikely to fire for the wrong skill, fitting the clear-niche anchor.	3 / 3
	Total	12 / 12 Passed

Validation

81%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 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
referenced_paths_exist	Referenced path issues: 2 missing	Warning

	Total	13 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/saas-packs/clay-pack/skills/clay-ci-integration/SKILL.md
Commit: 4c47e33

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.