Can I customize the guardrails for different environments?

Yes, the skill provides Open Policy Agent (OPA) templates and runtime checks that allow you to enforce different security logic for development, staging, and production environments.

How does this skill prevent Clay API key leaks?

It implements custom ESLint rules and pre-commit hooks that scan your code for Clay secret patterns (like sk_live_ strings) to block them from being committed to your repository.

What tools are required to use Clay Policy Guardrails?

The skill leverages standard development tools including ESLint, Pre-commit framework, TypeScript, and CI/CD platforms like GitHub Actions.

What kind of runtime protections are included?

It includes safeguards to block dangerous operations like 'deleteAll' in production and rate-limiting monitors to prevent your application from exceeding Clay API quotas.

Clay Policy & Guardrails

Name: Clay Policy & Guardrails
Author: jeremylongshore

byjeremylongshore

•

982

Security & Testing

Enforces security standards, linting rules, and automated guardrails for Clay integrations to prevent secret leaks and configuration errors.

About

Clay Policy & Guardrails is a specialized capability designed to harden Clay API integrations through automated policy enforcement. It provides a comprehensive framework for securing Clay-based applications by implementing custom ESLint rules to detect hardcoded keys, pre-commit hooks for secret scanning, and Policy-as-Code (OPA) for environmental compliance. Useful for teams needing to standardize Clay client initialization, prevent dangerous production operations, and maintain strict type safety, this skill ensures that Clay integrations follow industry best practices throughout the entire development lifecycle.

Key Features

Policy-as-Code (OPA) integration for environment-aware access control
Custom ESLint plugin for Clay-specific linting and secret detection
Runtime guardrails to prevent high-risk operations in production environments
Automated pre-commit hooks to block hardcoded API keys before they reach Git
CI/CD workflow templates for automated Clay configuration validation
982 GitHub stars

Use Cases

Validating Clay integration schemas within GitHub Actions or CI/CD pipelines
Enforcing standardized singleton client initialization patterns across large teams
Automating the detection and prevention of hardcoded Clay API keys in source code

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add jeremylongshore/claude-code-plugins-plus-skills clay-policy-guardrails

For use in Claude.ai and ChatGPT

Download Skill

GitHub