CL

clay-debug-bundle

Collects diagnostic logs and evidence bundles for Clay support tickets and troubleshooting.

Install

mkdir -p .claude/skills/clay-debug-bundle && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/7591" && unzip -o skill.zip -d .claude/skills/clay-debug-bundle && rm skill.zip

Installs to .claude/skills/clay-debug-bundle

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Collect Clay debug evidence for support tickets and troubleshooting.
68 charsno explicit “when” trigger
Beginner

Key capabilities

  • →Test webhook endpoint reachability
  • →Capture environment details like Node and Python versions
  • →Test Enterprise API connectivity using a provided API key
  • →Collect recent Clay-related log entries from specified directories
  • →Package collected diagnostic information into a compressed archive

How it works

The skill creates a directory, collects system information, tests Clay webhook and API connectivity, captures application logs, and then archives these files into a single bundle.

Inputs & outputs

You give it
User request for Clay debug information, CLAY_WEBHOOK_URL, CLAY_API_KEY
You get back
A .tar.gz archive containing diagnostic files like summary.txt, webhook-response.txt, api-response.txt, config-redacted.txt, and logs.txt

When to use clay-debug-bundle

  • →Creating support diagnostic bundles
  • →Testing webhook connectivity
  • →Debugging Clay enrichment errors
  • →Collecting integration logs

About clay-debug-bundle

Standardizes the collection of diagnostic information for Clay integrations, including webhook connectivity tests and API logs, to speed up support issue resolution.

Collect Clay debug evidence for support tickets and troubleshooting. Use when encountering persistent issues, preparing support tickets, or collecting diagnostic information for Clay problems. Trigger with phrases like "clay debug", "clay support bundle", "collect clay logs", "clay diagnostic".

When not to use it

  • →When debugging issues unrelated to Clay integrations
  • →When the problem is with pods or clusters, not web platform aspects

Prerequisites

Clay account with access to affected tablecurl for testing webhook/API connectivityBrowser developer tools for capturing network requests

Limitations

  • →Requires manual steps for collecting Clay UI table diagnostics
  • →Requires manual review for sensitive data before submission

How it compares

This skill automates the collection of specific Clay-related diagnostic data, unlike manual gathering of disparate system and application logs.

Compared to similar skills

clay-debug-bundle side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
clay-debug-bundle (this skill)14moCautionBeginner
godot1,0448moReviewIntermediate
python-testing-patterns776moReviewIntermediate
error-handling-patterns356moNo flagsIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

More by jeremylongshore

View all by jeremylongshore →

analyzing-logs

jeremylongshore

Analyze application logs to detect performance issues, identify error patterns, and improve stability by extracting key insights.

14123

ollama-setup

jeremylongshore

Configure auto-configure Ollama when user needs local LLM deployment, free AI alternatives, or wants to eliminate hosted API costs. Trigger phrases: "install ollama", "local AI", "free LLM", "self-hosted AI", "replace OpenAI", "no API costs". Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.

1167

backtesting-trading-strategies

jeremylongshore

Backtest crypto and traditional trading strategies against historical data. Calculates performance metrics (Sharpe, Sortino, max drawdown), generates equity curves, and optimizes strategy parameters. Use when user wants to test a trading strategy, validate signals, or compare approaches. Trigger with phrases like "backtest strategy", "test trading strategy", "historical performance", "simulate trades", "optimize parameters", or "validate signals".

1071

generating-database-seed-data

jeremylongshore

Process this skill enables AI assistant to generate realistic test data and database seed scripts for development and testing environments. it uses faker libraries to create realistic data, maintains relational integrity, and allows configurable data volumes. u... Use when working with databases or data models. Trigger with phrases like 'database', 'query', or 'schema'.

1033

cursor-codebase-indexing

jeremylongshore

Execute set up and optimize Cursor codebase indexing. Triggers on "cursor index setup", "codebase indexing", "index codebase", "cursor semantic search". Use when working with cursor codebase indexing functionality. Trigger with phrases like "cursor codebase indexing", "cursor indexing", "cursor".

885

testing-mobile-apps

jeremylongshore

Execute mobile app testing on iOS and Android devices/simulators. Use when performing specialized testing. Trigger with phrases like "test mobile app", "run iOS tests", or "validate Android functionality".

810

You might also like

godot

bfollington

This skill should be used when working on Godot Engine projects. It provides specialized knowledge of Godot's file formats (.gd, .tscn, .tres), architecture patterns (component-based, signal-driven, resource-based), common pitfalls, validation tools, code templates, and CLI workflows. The `godot` command is available for running the game, validating scripts, importing resources, and exporting builds. Use this skill for tasks involving Godot game development, debugging scene/resource files, implementing game systems, or creating new Godot components.

1,0441,947

python-testing-patterns

wshobson

Implement comprehensive testing strategies with pytest, fixtures, mocking, and test-driven development. Use when writing Python tests, setting up test suites, or implementing testing best practices.

77204

error-handling-patterns

wshobson

Master error handling patterns across languages including exceptions, Result types, error propagation, and graceful degradation to build resilient applications. Use when implementing error handling, designing APIs, or improving application reliability.

35170

chrome-devtools

mrgoonie

Browser automation, debugging, and performance analysis using Puppeteer CLI scripts. Use for automating browsers, taking screenshots, analyzing performance, monitoring network traffic, web scraping, form automation, and JavaScript debugging.

41157

unreal-engine-cpp-pro

sickn33

Expert guide for Unreal Engine 5.x C++ development, covering UObject hygiene, performance patterns, and best practices.

43117

python-performance-optimization

wshobson

Profile and optimize Python code using cProfile, memory profilers, and performance best practices. Use when debugging slow Python code, optimizing bottlenecks, or improving application performance.

27131

Search skills

Search the agent skills registry