clay-policy-guardrails

Implement credit spending limits, data privacy enforcement, and input validation guardrails for Clay pipelines. Use when enforcing spending caps, blocking PII enrichment, or adding pre-enrichment validation rules. Trigger with phrases like "clay policy", "clay guardrails", "clay spending limit", "clay data privacy rules", "clay validation", "clay controls".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

65%

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 complete executable code, but it is token-heavy due to four full inline implementations and lacks explicit validation feedback loops for its batch operations. Progressive disclosure is weak — content that should be separate is inline and no real bundle references exist.

Suggestions

Add an explicit validation checkpoint workflow for batch operations (e.g., run validateBatch → review rejected rows → fix and re-run before proceeding) to lift workflow clarity.

Move one or more of the full TypeScript implementations into reference files under references/ and link to them from the body to improve progressive disclosure and conciseness.

Tighten the Overview prose and trim redundant inline detail so every token earns its place.

Dimension	Reasoning	Score
Conciseness	Mostly efficient executable code with minimal conceptual padding, but ~320 lines of four full inline TypeScript implementations could be tightened or split to reference files; not lean enough for the top anchor.	2 / 3
Actionability	Provides fully executable, complete, copy-paste-ready TypeScript implementations for each policy area (CreditPolicyEnforcer, checkPrivacy, validateBatch, filterForExport), with concrete types and logic.	3 / 3
Workflow Clarity	Steps are sequenced (Step 1–4) and an error-handling table exists, but batch/destructive operations lack explicit validate→review→fix→retry checkpoints, capping clarity at 2 per the guideline.	2 / 3
Progressive Disclosure	Sections are well-organized, but the four large code implementations are inline rather than split into bundle files, and the only reference (clay-architecture-variants) points to another skill with no real bundle file in this skill.	2 / 3
	Total	9 / 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 well-crafted description: concrete capabilities, explicit 'Use when' triggers, natural trigger phrases, and a distinct Clay-specific niche. Third-person/imperative voice is used correctly with no first/second-person phrasing.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'credit spending limits, data privacy enforcement, and input validation guardrails' — rather than vague language, matching the multiple-specific-actions anchor.	3 / 3
Completeness	Explicitly answers both what ('Implement credit spending limits...') and when ('Use when enforcing spending caps, blocking PII enrichment, or adding pre-enrichment validation rules'), with explicit trigger guidance.	3 / 3
Trigger Term Quality	Provides good coverage of natural phrases a user would actually say ('clay policy', 'clay guardrails', 'clay spending limit', 'clay validation', 'clay controls'), with common variations.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear Clay-specific niche with distinct 'clay policy'/'clay guardrails' triggers, making it unlikely to fire for unrelated skills.	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
Commit: 02d6341

Reviewed: 4 days 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.