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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

85%

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

A well-structured, mostly executable CI/CD guide with clear sequencing and real validation checkpoints. Its main weakness is the schema-validation script being a no-op stub, which undercuts the actionability of the data-validation step it backs.

Suggestions

Make scripts/validate-clay-schemas.ts actually run the zod schemas against the test fixtures (e.g. parse each fixture and exit 1 on a parse error) instead of unconditionally logging 'All schemas valid.'

Add a brief note clarifying that the integration-tests job posts a CI marker payload (_ci_test) so reviewers know live tests are non-destructive, reinforcing the credit-safety rationale.

Dimension	Reasoning	Score
Conciseness	The body is lean and code-forward — a one-sentence overview, then executable workflow YAML, shell commands, tests, and schemas — with no padding explaining what CI or Clay is, so every token earns its place.	3 / 3
Actionability	Most blocks are copy-paste ready (workflow YAML, `gh secret set`, vitest tests, credit guard), but `validate-clay-schemas.ts` is a non-functional stub that defines schemas then merely logs 'All schemas valid.' without validating fixtures, leaving a key detail incomplete.	2 / 3
Workflow Clarity	Steps 1–5 are clearly sequenced with explicit validation checkpoints — `needs: [unit-tests]` gating, an HTTP-code assertion that exits 1 on failure, a PII grep guard, and a MAX_ROWS credit guard — plus an error-handling table for recovery.	3 / 3
Progressive Disclosure	The skill is self-contained with well-organized sections (Overview, Prerequisites, Steps, Error Handling, Resources, Next Steps) and only one-level external links; no bundle files exist to require deeper splitting.	3 / 3
	Total	11 / 12 Passed

Description

100%

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, specific description that clearly states capabilities, gives explicit 'Use when' triggers, and lists natural trigger phrases, all scoped to a distinct Clay CI/CD niche. It uses appropriate third-person/infinitive voice with no fluff.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Configure CI/CD pipelines for Clay integrations with automated testing and validation' and 'setting up automated tests for Clay webhook handlers, validating enrichment data quality in CI, or integrating Clay checks into your build process' — rather than vague language.	3 / 3
Completeness	Explicitly answers both what ('Configure CI/CD pipelines for Clay integrations with automated testing and validation') and when (an explicit 'Use when...' clause plus a 'Trigger with phrases like' list), matching the top anchor.	3 / 3
Trigger Term Quality	Provides natural, varied trigger phrases a user would actually say — 'clay CI', 'clay GitHub Actions', 'clay automated tests', 'CI clay', 'test clay integration' — with good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	Targets a clear niche (the Clay enrichment platform) with Clay-qualified triggers, making it unlikely to fire for generic CI/CD or testing skills.	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
Commit: 02d6341

Reviewed: 21 minutes 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.