Novu Design Workflow
novuhq/novu
Design notification workflows the Novu way — choose channels, set severity, decide when a workflow is critical, configure digests, and route based on subscriber state.
Configure Clay integrations across development, staging, and production environments.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill clay-multi-env-setup -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace clay-multi-env-setup --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-multi-env-setup .claude/skills/clay-multi-env-setup && rm -rf skills-srcUse ~/.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/
Install the "clay-multi-env-setup" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/clay-multi-env-setup into .claude/skills/clay-multi-env-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clay-multi-env-setup", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/clay-multi-env-setupType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill clay-multi-env-setup -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace clay-multi-env-setup --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/.curated/clay-multi-env-setup .agents/skills/clay-multi-env-setup && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "clay-multi-env-setup" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/clay-multi-env-setup into .agents/skills/clay-multi-env-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clay-multi-env-setup", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill clay-multi-env-setup -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace clay-multi-env-setup --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/.curated/clay-multi-env-setup .cursor/skills/clay-multi-env-setup && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "clay-multi-env-setup" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/clay-multi-env-setup into .cursor/skills/clay-multi-env-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clay-multi-env-setup", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/jeremylongshore/tons-of-skills-marketplace.git --path skills/.curated/clay-multi-env-setup--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill clay-multi-env-setup -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace clay-multi-env-setup --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/.curated/clay-multi-env-setup .gemini/skills/clay-multi-env-setup && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "clay-multi-env-setup" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/clay-multi-env-setup into .gemini/skills/clay-multi-env-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clay-multi-env-setup", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install jeremylongshore/tons-of-skills-marketplace clay-multi-env-setupInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill clay-multi-env-setup -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/.curated/clay-multi-env-setup .github/skills/clay-multi-env-setup && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "clay-multi-env-setup" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/clay-multi-env-setup into .github/skills/clay-multi-env-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clay-multi-env-setup", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill clay-multi-env-setup -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace clay-multi-env-setup --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/.curated/clay-multi-env-setup .opencode/skills/clay-multi-env-setup && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "clay-multi-env-setup" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/clay-multi-env-setup into .opencode/skills/clay-multi-env-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clay-multi-env-setup", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
clay-multi-env-setupConfigure Clay integrations across development, staging, and production environments.
Clay Multi Env Setup is an agent skill from jeremylongshore/tons-of-skills-marketplace. Configure Clay integrations across development, staging, and production environments. Use when setting up per-environment Clay tables, managing webhook URLs per environment, or implementing environment-specific enrichment configurations. Trigger with phrases like "clay environments", "clay staging", "clay dev prod", "clay environment setup", "clay config by env".
Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/implementation-guide.md` and `references/implementation.md`). Compatibility notes: Designed for Claude Code
It sits in Backend & APIs, covering Webhooks. 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.
5 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.
Pre-approves these tools, so the agent can use them without asking each time:
ReadWriteEditBash(curl:*)GrepFrom allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
ghFrom the folder's file list and the shell code blocks in SKILL.md.
Links to these hosts (documentation or services it may open):
university.clay.comzod.devFrom URLs in SKILL.md, links to its own repository left out.
Names these keys or tokens, usually read from environment variables:
CLAY_API_KEYFrom names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Designed for Claude Code
From compatibility in the SKILL.md frontmatter.
Clay Multi Env Setup loads about 1.8k tokens when it runs, and up to ~3.7k if it reads all its reference files. Until then it costs about 97 tokens; SKILL.md has 325 words of instructions outside code blocks.
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.
The automated check noted patterns worth knowing about, such as sudo or a known installer.
# .env.development# .env.staging# .env.production (never in git — use secrets manager)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.
The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 325 words, ~1,752 tokens.
.claude/skills/clay-multi-env-setup/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.Configure Clay integrations across dev/staging/prod with isolated tables, separate webhook URLs, and environment-specific enrichment settings. Clay is a single workspace per account, so multi-environment isolation requires separate tables, careful naming, and environment-aware application code.
In Clay, create separate tables for each environment:
| Table Name | Environment | Webhook URL | Auto-Enrich | Credit Cap |
|---|---|---|---|---|
[DEV] Outbound Leads | Development | Dev webhook | ON (small batches) | 100 rows |
[STG] Outbound Leads | Staging | Staging webhook | ON | 500 rows |
Outbound Leads | Production | Prod webhook | ON | 10,000 rows |
Each table gets its own webhook URL. Copy each URL to the appropriate environment's secrets.
// src/config/clay.ts — environment-aware Clay configuration
interface ClayEnvConfig {
webhookUrl: string;
apiKey?: string; // Enterprise API (if applicable)
maxRowsPerBatch: number;
delayBetweenRowsMs: number;
enableCRMSync: boolean;
tablePrefix: string;
}
function getClayConfig(): ClayEnvConfig {
const env = process.env.NODE_ENV || 'development';
const configs: Record<string, ClayEnvConfig> = {
development: {
webhookUrl: process.env.CLAY_WEBHOOK_URL_DEV!,
maxRowsPerBatch: 10, // Small batches to conserve credits
delayBetweenRowsMs: 500, // Slow, safe
enableCRMSync: false, // Never push dev data to real CRM
tablePrefix: '[DEV]',
},
staging: {
webhookUrl: process.env.CLAY_WEBHOOK_URL_STG!,
maxRowsPerBatch: 100,
delayBetweenRowsMs: 250,
enableCRMSync: false, // Use sandbox CRM if needed
tablePrefix: '[STG]',
},
production: {
webhookUrl: process.env.CLAY_WEBHOOK_URL!,
apiKey: process.env.CLAY_API_KEY,
maxRowsPerBatch: 1000,
delayBetweenRowsMs: 100,
enableCRMSync: true,
tablePrefix: '',
},
};
const config = configs[env];
if (!config) throw new Error(`Unknown environment: ${env}`);
if (!config.webhookUrl) throw new Error(`CLAY_WEBHOOK_URL not set for ${env}`);
return config;
}# .env.development
CLAY_WEBHOOK_URL_DEV=https://app.clay.com/api/v1/webhooks/dev-webhook-id
NODE_ENV=development
# .env.staging
CLAY_WEBHOOK_URL_STG=https://app.clay.com/api/v1/webhooks/stg-webhook-id
NODE_ENV=staging
# .env.production (never in git — use secrets manager)
CLAY_WEBHOOK_URL=https://app.clay.com/api/v1/webhooks/prod-webhook-id
CLAY_API_KEY=clay_ent_production_key
NODE_ENV=production# GitHub Actions — per-environment secrets
gh secret set CLAY_WEBHOOK_URL_DEV --body "https://app.clay.com/api/v1/webhooks/dev-id"
gh secret set CLAY_WEBHOOK_URL_STG --body "https://app.clay.com/api/v1/webhooks/stg-id"
gh secret set CLAY_WEBHOOK_URL --body "https://app.clay.com/api/v1/webhooks/prod-id"
gh secret set CLAY_API_KEY --body "clay_ent_production_key"// src/config/validate.ts — fail fast if config is wrong
import { z } from 'zod';
const ClayConfigSchema = z.object({
webhookUrl: z.string().url().startsWith('https://'),
apiKey: z.string().startsWith('clay_ent_').optional(),
maxRowsPerBatch: z.number().positive().max(10_000),
delayBetweenRowsMs: z.number().min(0),
enableCRMSync: z.boolean(),
tablePrefix: z.string(),
});
export function validateClayConfig(config: unknown) {
const result = ClayConfigSchema.safeParse(config);
if (!result.success) {
console.error('Clay configuration invalid:', result.error.format());
process.exit(1);
}
console.log(`Clay config validated for ${process.env.NODE_ENV}`);
return result.data;
}// src/clay/guards.ts — prevent production data in dev and vice versa
function safetyCheck(env: string, rowCount: number): void {
if (env === 'development' && rowCount > 50) {
throw new Error(`Dev environment: refusing to process ${rowCount} rows (max 50). Use staging or production.`);
}
if (env === 'staging' && rowCount > 1000) {
throw new Error(`Staging environment: refusing to process ${rowCount} rows (max 1000). Use production.`);
}
}
function preventCrossEnvData(env: string, crmPushEnabled: boolean): void {
if (env !== 'production' && crmPushEnabled) {
throw new Error(`CRM sync is disabled in ${env}. Only production can push to CRM.`);
}
}| Issue | Cause | Solution |
|---|---|---|
| Wrong table receives data | Dev webhook URL in production | Validate webhook URL matches environment |
| Dev data in production CRM | CRM sync enabled in dev | Guard CRM sync to production only |
| Credit waste in dev/staging | Full enrichment on test data | Set low row caps on dev/staging tables |
| Missing webhook URL at startup | Environment variable not set | Add startup validation with Zod |
Create an environment-bound configuration record listing the workspace/table prefix, secret references, row and credit limits, CRM permission, validation result, deployment owner, and tested promotion/rollback path. Never share actual webhook URLs, API keys, provider credentials, or production lead data in environment files, examples, or diagnostics.
Deploy a staging configuration with a distinct table prefix and CRM push disabled, then submit a synthetic row and verify the safety guards reject an oversized batch. Promote the reviewed configuration only after production secrets and limits are independently validated; if any cross-environment value is detected, halt deployment and rotate the exposed boundary as appropriate.
For monitoring and observability, see clay-observability.
© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 2 other files (references) in skills/.curated/clay-multi-env-setup of jeremylongshore/tons-of-skills-marketplace.
Open the folder on GitHubat commit cfae287
Clay Multi Env Setup 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Clay Multi Env Setup this skilljeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~1.8k | Automated safety check: Notes | MIT | |
| Novu Design Workflownovuhq/novu | 40k | — | ~2.6k | Automated safety check: Pass | Custom licence | |
| Golivemikehasa/golive-skill | 1.3k | — | ~13k | Automated safety check: Notes | MIT | |
| Stripe Appsfossasia/eventyay | 1.7k | 1 repos | ~3.6k | Automated safety check: Pass | Apache-2.0 | |
| Dingtalk Messageagentscope-ai/ReMe | 3.6k | — | ~1.6k | Automated safety check: Pass | Apache-2.0 | |
| PR Review Provideryansongda/pay | 5.4k | — | ~2.4k | Automated safety check: Pass | MIT |
novuhq/novu
Design notification workflows the Novu way — choose channels, set severity, decide when a workflow is critical, configure digests, and route based on subscriber state.
mikehasa/golive-skill
Take an agent-written app from repo to live production on the user's OWN accounts, with providers they choose (hosting, database, auth, payments, email, domain/DNS).
fossasia/eventyay
A skill your agent uses when building, modifying, or reviewing a Stripe App — or when the user describes something that implies one (e.g.
agentscope-ai/ReMe
钉钉消息发送技能。支持企业内部机器人(批量单聊/群聊)和 Webhook 自定义机器人两种接入方式,支持多机器人管理,支持文本、Markdown、链接、ActionCard、FeedCard等多种消息类型。
yansongda/pay
A skill your agent uses when reviewing PRs that add or modify a payment Provider in yansongda/pay - covers plugin pipeline, multi-tenant safety, signature verification, docs, and naming conventions.
kanchengw/cnllm
Guides Stripe integration decisions — API selection (Checkout Sessions vs PaymentIntents), Connect platform setup (Accounts v2, controller properties), billing/subscriptions, Treasury financial…
jeremylongshore/tons-of-skills-marketplace
Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.
jeremylongshore/tons-of-skills-marketplace
Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.
jeremylongshore/tons-of-skills-marketplace
Execute proactive auto-loading: automatically detects and loads agents.md files.
jeremylongshore/tons-of-skills-marketplace
Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.
jeremylongshore/tons-of-skills-marketplace
Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.
jeremylongshore/tons-of-skills-marketplace
Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.
Categories
Configure Clay integrations across development, staging, and production environments. Clay Multi Env Setup is an agent skill from jeremylongshore/tons-of-skills-marketplace. Configure Clay integrations across development, staging, and production environments.
Clay Multi Env Setup fits situations like: setting up per-environment Clay tables; managing webhook URLs per environment; implementing environment-specific enrichment configurations; with phrases like clay environments.
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill clay-multi-env-setup -a claude-code`. Or copy the skill folder (skills/.curated/clay-multi-env-setup in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/clay-multi-env-setup in your project. Claude Code loads it when a task matches its description.
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill clay-multi-env-setup -a codex`. Or copy the skill folder (skills/.curated/clay-multi-env-setup in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/clay-multi-env-setup in your project. Codex loads it when a task matches its description.
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-multi-env-setup -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-multi-env-setup, .gemini/skills/clay-multi-env-setup, .github/skills/clay-multi-env-setup and .opencode/skills/clay-multi-env-setup in your project.
Going by SKILL.md and its folder, Clay Multi Env Setup needs the command-line tools its instructions call (gh) and credentials named CLAY_API_KEY. Our summary lists: A credential in CLAY_API_KEY. Its frontmatter pre-approves these tools: Read, Write, Edit, Bash(curl:*), Grep. Compatibility (from SKILL.md): Designed for Claude Code.
SKILL.md names 2 domains. As links in the text: university.clay.com and zod.dev. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
Clay Multi Env Setup is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
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. Its references folder adds about 1.9k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Clay Multi Env Setup: Novu Design Workflow (novuhq/novu, 40k stars), Golive (mikehasa/golive-skill, 1.3k stars), Stripe Apps (fossasia/eventyay, 1.7k stars) and Dingtalk Message (agentscope-ai/ReMe, 3.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
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.