New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Clay Deploy Integration

by jeremylongshore in jeremylongshore/tons-of-skills-marketplace

Deploy Clay-powered applications to Vercel, Cloud Run, or Docker with proper secrets management.

MITAuto-check passedDevOps & Cloud

Install Clay Deploy Integration

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill clay-deploy-integration -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace clay-deploy-integration --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/clay-deploy-integration .claude/skills/clay-deploy-integration && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
clay-deploy-integration
GitHub stars
2.8k
Token cost
~1.8k tokens
SKILL.md length
362 words
Files
1
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Deploy Clay-powered applications to Vercel, Cloud Run, or Docker with proper secrets management.

  • Works in 6 steps: Vercel Deployment (Serverless) → Cloud Run Deployment (Container) → Docker Compose (Self-Hosted) → …
  • Deploying Clay webhook receivers
  • SKILL.md covers Overview, Prerequisites, Instructions and Error Handling, plus 4 more sections
  • Calls vercel and gcloud; reaches clay-handler.vercel.app; needs CLAY_WEBHOOK_SECRET and CLAY_API_KEY

What it does

Clay Deploy Integration is an agent skill from jeremylongshore/tons-of-skills-marketplace. Deploy Clay-powered applications to Vercel, Cloud Run, or Docker with proper secrets management. Use when deploying Clay webhook receivers, enrichment pipelines, or CRM sync services to production infrastructure. Trigger with phrases like "deploy clay", "clay Vercel", "clay production deploy", "clay Cloud Run", "clay Docker", "host clay integration".

Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: Designed for Claude Code

It sits in DevOps & Cloud, covering Webhooks, Containers and Deployment. It works with Cloud Run, Vercel and Docker. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.

When your agent uses it

  • Deploying Clay webhook receivers
  • Enrichment pipelines
  • CRM sync services to production infrastructure
  • With phrases like deploy clay

Example prompts

  • “deploy clay”
  • “clay Vercel”
  • “clay production deploy”
  • “/clay-deploy-integration”

Requirements

  • Docker
  • A credential in CLAY_API_KEY
  • A credential in CLAY_WEBHOOK_SECRET
  • Compatibility (from SKILL.md): Designed for Claude Code
  • Pre-approved tools (allowed-tools): Read, Write, Edit, Bash(vercel:*), Bash(gcloud:*), Bash(docker:*)

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Vercel Deployment (Serverless)
  2. Cloud Run Deployment (Container)
  3. Docker Compose (Self-Hosted)
  4. Configure Clay to Call Your Deployed Endpoint
  5. Health Check Endpoint
  6. Production Environment Variables

What it can do on your machine

Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Write
    • Edit
    • Bash(vercel:*)
    • Bash(gcloud:*)
    • Bash(docker:*)

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • vercel
    • gcloud

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • clay-handler.vercel.app

    Also links to:

    • vercel.com
    • cloud.google.com
    • university.clay.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • CLAY_WEBHOOK_SECRET
    • CLAY_API_KEY
    • CRM_API_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Designed for Claude Code

    From compatibility in the SKILL.md frontmatter.

Context cost

Clay Deploy Integration loads about 1.8k tokens when it runs. Until then it costs about 94 tokens; SKILL.md has 362 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~94
When it runs · the whole SKILL.md, loaded when a task matches
~1.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 362 words, ~1,752 tokens.

Download SKILL.mdSave it as .claude/skills/clay-deploy-integration/SKILL.md (or your agent's skills folder).
name
clay-deploy-integration
description
Deploy Clay-powered applications to Vercel, Cloud Run, or Docker with proper secrets management. Use when deploying Clay webhook receivers, enrichment pipelines, or CRM sync services to production infrastructure. Trigger with phrases like "deploy clay", "clay Vercel", "clay production deploy", "clay Cloud Run", "clay Docker", "host clay integration".
allowed-tools
Read, Write, Edit, Bash(vercel:*), Bash(gcloud:*), Bash(docker:*)
compatibility
Designed for Claude Code
version
1.14.0
license
MIT
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
saas, clay, deployment

Clay Deploy Integration

Overview

Deploy applications that integrate with Clay (webhook receivers, enrichment processors, CRM sync services) to production platforms. Clay itself is a hosted SaaS -- you deploy the code that interacts with Clay, not Clay itself. The critical requirement is a publicly accessible HTTPS endpoint for Clay's HTTP API columns to call back to.

Prerequisites

  • Application code that handles Clay webhooks or HTTP API callbacks
  • Platform CLI installed (vercel, gcloud, or docker)
  • Clay webhook URL and/or API key stored securely
  • HTTPS endpoint accessible from the public internet

Instructions

Step 1: Vercel Deployment (Serverless)

Best for: Webhook receivers, small-scale enrichment handlers.

bash
# Set Clay secrets in Vercel
vercel env add CLAY_WEBHOOK_URL production
vercel env add CLAY_API_KEY production
vercel env add CLAY_WEBHOOK_SECRET production

# Deploy
vercel --prod
typescript
// api/clay/callback.ts — Vercel serverless function
import type { VercelRequest, VercelResponse } from '@vercel/node';
import crypto from 'crypto';

export default async function handler(req: VercelRequest, res: VercelResponse) {
  if (req.method !== 'POST') return res.status(405).end();

  // Validate webhook signature
  const signature = req.headers['x-clay-signature'] as string;
  const secret = process.env.CLAY_WEBHOOK_SECRET!;
  const expected = crypto.createHmac('sha256', secret)
    .update(JSON.stringify(req.body))
    .digest('hex');

  if (!crypto.timingSafeEqual(Buffer.from(signature || ''), Buffer.from(expected))) {
    return res.status(401).json({ error: 'Invalid signature' });
  }

  // Process enriched data from Clay HTTP API column
  const enrichedLead = req.body;
  console.log('Received enriched lead:', {
    email: enrichedLead.email,
    company: enrichedLead.company_name,
    score: enrichedLead.icp_score,
  });

  // Push to CRM, database, or outreach tool
  await processLead(enrichedLead);

  return res.status(200).json({ status: 'processed' });
}
Step 2: Cloud Run Deployment (Container)

Best for: High-volume enrichment pipelines, CRM sync services.

dockerfile
# Dockerfile
FROM node:20-slim
WORKDIR /app
COPY package*.json ./
RUN npm ci --only=production
COPY dist/ ./dist/
EXPOSE 8080
ENV PORT=8080
CMD ["node", "dist/index.js"]
bash
# Build and deploy to Cloud Run
gcloud builds submit --tag gcr.io/$PROJECT_ID/clay-handler

gcloud run deploy clay-handler \
  --image gcr.io/$PROJECT_ID/clay-handler \
  --platform managed \
  --region us-central1 \
  --allow-unauthenticated \
  --set-secrets "CLAY_API_KEY=clay-api-key:latest,CLAY_WEBHOOK_SECRET=clay-webhook-secret:latest" \
  --min-instances 1 \
  --max-instances 10
Step 3: Docker Compose (Self-Hosted)

Best for: On-premise deployments, development staging.

yaml
# docker-compose.yml
version: '3.8'
services:
  clay-handler:
    build: .
    ports:
      - "3000:3000"
    environment:
      - CLAY_WEBHOOK_URL=${CLAY_WEBHOOK_URL}
      - CLAY_API_KEY=${CLAY_API_KEY}
      - CLAY_WEBHOOK_SECRET=${CLAY_WEBHOOK_SECRET}
      - DATABASE_URL=${DATABASE_URL}
    restart: unless-stopped
    healthcheck:
      test: ["CMD", "curl", "-f", "http://localhost:3000/health"]
      interval: 30s
      timeout: 10s
      retries: 3
Step 4: Configure Clay to Call Your Deployed Endpoint

Once deployed, update your Clay table's HTTP API column:

  1. Get your deployment URL (e.g., https://clay-handler.vercel.app or Cloud Run URL)
  2. In Clay table, edit the HTTP API column
  3. Set URL to: https://your-deployment.com/api/clay/callback
  4. Test on a single row before enabling auto-run
Step 5: Health Check Endpoint
typescript
// src/health.ts — health check that verifies Clay connectivity
app.get('/health', async (req, res) => {
  const checks: Record<string, string> = {
    server: 'ok',
    clay_webhook: 'unknown',
    database: 'unknown',
  };

  // Check Clay webhook reachability
  try {
    const webhookTest = await fetch(process.env.CLAY_WEBHOOK_URL!, {
      method: 'POST',
      headers: { 'Content-Type': 'application/json' },
      body: JSON.stringify({ _health_check: true }),
    });
    checks.clay_webhook = webhookTest.ok ? 'ok' : `error: ${webhookTest.status}`;
  } catch {
    checks.clay_webhook = 'unreachable';
  }

  const allHealthy = Object.values(checks).every(v => v === 'ok');
  res.status(allHealthy ? 200 : 503).json({ status: allHealthy ? 'healthy' : 'degraded', checks });
});
Step 6: Production Environment Variables
bash
# Required for all deployments
CLAY_WEBHOOK_URL=https://app.clay.com/api/v1/webhooks/your-id
CLAY_WEBHOOK_SECRET=your-shared-secret

# Optional (Enterprise only)
CLAY_API_KEY=clay_ent_your_key

# Application-specific
DATABASE_URL=postgresql://...
CRM_API_KEY=your-crm-key
PORT=3000

Error Handling

IssueCauseSolution
Clay can't reach callbackEndpoint not public HTTPSVerify URL is accessible, check firewall
Cold start timeoutServerless function too slowSet min-instances=1 on Cloud Run
Missing secrets in deployEnv vars not configuredAdd via platform CLI before deploying
Health check failsClay webhook URL invalidRe-copy webhook URL from Clay table
Show full SKILL.md (116 more words)Show less

Output

Publish a deployment receipt containing environment, release/version, runtime identity, secret references, webhook verification, health checks, alert route, and rollback decision. Do not emit webhook URLs, shared secrets, individual lead payloads, or CRM credentials in application logs, CI output, or receipts.

Examples

Deploy a staging callback with a dedicated runtime role, submit a synthetic row, and verify a signed/authorized receipt, queued processing, and a redacted health result. Promote only after the production environment gate approves the same evidence; on reachability or secret failure, roll back the release rather than opening the endpoint or widening its permissions.

Resources

Next Steps

For webhook handling patterns, see clay-webhooks-events.

© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/.curated/clay-deploy-integration of jeremylongshore/tons-of-skills-marketplace.

Open the folder on GitHubat commit cfae287

Compare with similar skills

Clay Deploy Integration next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Clay Deploy Integration compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Clay Deploy Integration this skilljeremylongshore/tons-of-skills-marketplace2.8k—~1.8kAutomated safety check: PassMIT
CI/CD Pipeline Principlesirahardianto/awesome-agv156—~2.7kAutomated safety check: NotesMIT
Monstermq Broker Configvogler75/monster-mq143—~2.2kAutomated safety check: PassGPL-3.0
Frontmcp Deploymentagentfront/frontmcp146—~9.2kAutomated safety check: NotesApache-2.0
LangBot Deployment Guidelangbot-app/LangBot18k—~1.5kAutomated safety check: NotesApache-2.0
Deploymentmatrixorigin/memoria610—~1.6kAutomated safety check: NotesApache-2.0

Similar skills

  • CI/CD Pipeline Principles

    irahardianto/awesome-agv

    Rules for designing CI/CD pipelines in layers: universal lint, test and scan stages, container builds with SBOM attestation, and GitOps for orchestrated deployments.

    156 GitHub stars~2.7k tokensUpdated 6 days ago
    DevOps & CloudAuto-check: notes

  • Monstermq Broker Config

    vogler75/monster-mq

    Guide for configuring, deploying, and operating the MonsterMQ broker.

    143 GitHub stars~2.2k tokensUpdated today
    DevOps & CloudAuto-check passed

  • Frontmcp Deployment

    agentfront/frontmcp

    A skill your agent uses when deploying, building for production, packaging, or shipping a FrontMCP server.

    146 GitHub stars~9.2k tokensUpdated today
    DevOps & CloudAuto-check: notes

  • LangBot Deployment Guide

    langbot-app/LangBot

    Deploys and configures a LangBot instance with Docker Compose or Kubernetes, covering config.yaml, the Box sandbox runtime, the plugin runtime and the global API key.

    18k GitHub stars~1.5k tokensUpdated today
    DevOps & CloudAuto-check: notes

  • Deployment

    matrixorigin/memoria

    Deploy Memoria with Docker Compose or Kubernetes. An agent skill from matrixorigin/memoria.

    610 GitHub stars~1.6k tokensUpdated yesterday
    DevOps & CloudAuto-check: notes

  • Frontmcp Production Readiness

    agentfront/frontmcp

    Pre-production audit, hardening, and go-live checklists for FrontMCP servers.

    146 GitHub stars~6.5k tokensUpdated yesterday
    DevOps & CloudAuto-check passed

More from jeremylongshore/tons-of-skills-marketplace

All 3,342 skills in this repo

  • Performing Security Code Review

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.

    2.8k GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check: notes

  • Adapting Transfer Learning Models

    jeremylongshore/tons-of-skills-marketplace

    Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Agent Context Loader

    jeremylongshore/tons-of-skills-marketplace

    Execute proactive auto-loading: automatically detects and loads agents.md files.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Aggregating Performance Metrics

    jeremylongshore/tons-of-skills-marketplace

    Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.

    2.8k GitHub stars~1.2k tokensUpdated today
    Auto-check passed

  • Analyzing Capacity Planning

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.

    2.8k GitHub stars~947 tokensUpdated today
    Auto-check passed

  • Analyzing Database Indexes

    jeremylongshore/tons-of-skills-marketplace

    Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~2k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Clay Deploy Integration

What does Clay Deploy Integration do?

Deploy Clay-powered applications to Vercel, Cloud Run, or Docker with proper secrets management. Clay Deploy Integration is an agent skill from jeremylongshore/tons-of-skills-marketplace. Deploy Clay-powered applications to Vercel, Cloud Run, or Docker with proper secrets management.

When should I use Clay Deploy Integration?

Clay Deploy Integration fits situations like: deploying Clay webhook receivers; enrichment pipelines; CRM sync services to production infrastructure; with phrases like deploy clay.

How do I install Clay Deploy Integration in Claude Code?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill clay-deploy-integration -a claude-code`. Or copy the skill folder (skills/.curated/clay-deploy-integration in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/clay-deploy-integration in your project. Claude Code loads it when a task matches its description.

How do I install Clay Deploy Integration in Codex?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill clay-deploy-integration -a codex`. Or copy the skill folder (skills/.curated/clay-deploy-integration in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/clay-deploy-integration in your project. Codex loads it when a task matches its description.

Can I use Clay Deploy Integration in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill clay-deploy-integration -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/clay-deploy-integration, .gemini/skills/clay-deploy-integration, .github/skills/clay-deploy-integration and .opencode/skills/clay-deploy-integration in your project.

What does Clay Deploy Integration need to run?

Going by SKILL.md and its folder, Clay Deploy Integration needs the command-line tools its instructions call (vercel and gcloud) and credentials named CLAY_WEBHOOK_SECRET, CLAY_API_KEY and CRM_API_KEY. Our summary lists: Docker; A credential in CLAY_API_KEY; A credential in CLAY_WEBHOOK_SECRET. Its frontmatter pre-approves these tools: Read, Write, Edit, Bash(vercel:*), Bash(gcloud:*), Bash(docker:*). Compatibility (from SKILL.md): Designed for Claude Code.

Does Clay Deploy Integration access the network?

SKILL.md names 4 domains. In commands or code: clay-handler.vercel.app; the agent is likely to contact it when it follows the instructions. As links in the text: vercel.com, cloud.google.com and university.clay.com. This is read from the text; nothing was executed.

Is Clay Deploy Integration safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Clay Deploy Integration use?

Clay Deploy Integration is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Clay Deploy Integration use?

About 1.8k tokens (SKILL.md is roughly 7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Clay Deploy Integration?

Skills that share tags, products or a category with Clay Deploy Integration: CI/CD Pipeline Principles (irahardianto/awesome-agv, 156 stars), Monstermq Broker Config (vogler75/monster-mq, 143 stars), Frontmcp Deployment (agentfront/frontmcp, 146 stars) and LangBot Deployment Guide (langbot-app/LangBot, 18k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Clay Deploy Integration?

jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.

Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.