clay-reference-architecture

Design production Clay enrichment pipelines with table schemas, waterfall patterns, and CRM sync. Use when architecting new Clay integrations, reviewing data flow design, or establishing enrichment pipeline standards. Trigger with phrases like "clay architecture", "clay best practices", "clay pipeline design", "clay reference", "clay data flow".

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

65%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 body is highly actionable with executable formulas and configs and a clear step sequence, but it is verbose, lacks validation checkpoints for risky operations, and under-uses the available reference bundle files.

Suggestions

Add explicit validation checkpoints (e.g., verify enrichment coverage and test CRM dedup on a sample row) before proceeding to full CRM push in Step 5.

Move the large ASCII integration-pattern diagram and detailed schema into implementation-guide.md and link to it from the body, reducing inline token weight.

Reference implementation-guide.md and implementation.md explicitly in the body so the bundle is discoverable, rather than only pointing Next Steps to an unrelated skill.

Dimension	Reasoning	Score
Conciseness	Content is mostly efficient with concrete configs, but the large ASCII integration-pattern diagrams, full ICP formula, and detailed waterfall YAML pad length beyond what is strictly necessary; could be tightened without losing clarity.	2 / 3
Actionability	Provides copy-paste-ready guidance — a complete Clay ICP Score LET formula, waterfall YAML with providers/credits/coverage, and a CRM sync YAML with explicit field mapping and dedup key — all executable.	3 / 3
Workflow Clarity	Steps 1–5 are clearly sequenced, but for risky batch/destructive operations like CRM push and enrichment there are no validation checkpoints or validate-fix-retry feedback loops, which caps clarity at 2.	2 / 3
Progressive Disclosure	Bundle reference files exist (implementation-guide.md, implementation.md) but the body never signals or links to them, while detailed schema and config content that could live in references remains inline; structure is present but not well navigated.	2 / 3
	Total	9 / 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.

The description is strong: it states concrete capabilities, provides natural trigger phrases, and covers both what and when. It uses third person and stays concise without fluff.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions — 'table schemas, waterfall patterns, and CRM sync' — matching the level-3 anchor listing several specific concrete actions.	3 / 3
Completeness	Explicitly answers both what (design Clay enrichment pipelines) and when ('Use when architecting new Clay integrations, reviewing data flow design...') with explicit triggers.	3 / 3
Trigger Term Quality	'Trigger with phrases like clay architecture, clay best practices, clay pipeline design, clay reference, clay data flow' gives good coverage of natural terms a user would actually say.	3 / 3
Distinctiveness Conflict Risk	Clear Clay-enrichment niche with distinctive clay-prefixed triggers; unlikely to fire for an unrelated skill.	3 / 3
	Total	12 / 12 Passed

Validation

87%

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 — 14 / 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

	Total	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/saas-packs/clay-pack/skills/clay-reference-architecture/SKILL.md
Commit: 0540a62

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.