Skip to main content
exa-debug-bundle Collect Exa debug evidence for support tickets and troubleshooting.
Use when encountering persistent issues, preparing support tickets,
or collecting diagnostic information for Exa problems.
Trigger with phrases like "exa debug", "exa support bundle",
"collect exa logs", "exa diagnostic".
Aller à l'installation Skills Marketplace Découvrez et explorez les compétences IA créées par la communauté.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Copier le promptAfficher les détails du prompt Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.
npx skills add https://github.com/jeremylongshore/claude-code-plugins-plus-skills --skill exa-debug-bundleLa commande reste sur une seule ligne. Faites défiler horizontalement pour la vérifier avant de la copier.
Vous préférez une copie locale ? Téléchargez les fichiers actuellement disponibles dans SkillsMP.
Télécharger Zip Téléchargement... Plus depuis ce dépôt Implement user sign-up and sign-in flows with Clerk.
Use when building authentication UI, customizing sign-in experience,
or implementing OAuth social login.
Trigger with phrases like "clerk sign-in", "clerk sign-up",
"clerk login flow", "clerk OAuth", "clerk social login".
Implement session management and middleware with Clerk.
Use when managing user sessions, configuring route protection,
or implementing token refresh and custom JWT templates.
Trigger with phrases like "clerk session", "clerk middleware",
"clerk route protection", "clerk token", "clerk JWT".
Configure enterprise SSO, role-based access control, and organization management.
Use when implementing SSO integration, configuring role-based permissions,
or setting up organization-level controls.
Trigger with phrases like "clerk SSO", "clerk RBAC",
"clerk enterprise", "clerk roles", "clerk permissions", "clerk organizations".
Métiers associés SOC
Basé sur la classification professionnelle SOC
name exa-debug-bundle description Collect Exa debug evidence for support tickets and troubleshooting.
Use when encountering persistent issues, preparing support tickets,
or collecting diagnostic information for Exa problems.
Trigger with phrases like "exa debug", "exa support bundle",
"collect exa logs", "exa diagnostic".
allowed-tools Read, Bash(grep:*), Bash(curl:*), Bash(tar:*), Bash(node:*), Grep version 1.11.0 license MIT author Jeremy Longshore <jeremy@intentsolutions.io> tags ["saas","exa","debugging"] compatibility Designed for Claude Code, also compatible with Codex and OpenClaw
Exa Debug Bundle
Current State
!node --version 2>/dev/null || echo 'N/A'
!npm list exa-js 2>/dev/null | grep exa-js || echo 'exa-js not installed'
!echo "EXA_API_KEY: ${EXA_API_KEY:+SET (${#EXA_API_KEY} chars)}"
Overview
Collect all necessary diagnostic information for Exa support tickets. Exa error responses include a requestId field — always include it when contacting support at hello@exa.ai .
Instructions
Step 1: Quick Connectivity Test
set -euo pipefail
echo "=== Exa Connectivity Test ==="
echo "API Key: ${EXA_API_KEY:+SET (${#EXA_API_KEY} chars)} "
echo ""
HTTP_CODE=$(curl -s -o /tmp/exa-debug.json -w "%{http_code}" \
-X POST https://api.exa.ai/search \
-H "x-api-key: $EXA_API_KEY " \
-H "Content-Type: application/json" \
-d '{"query":"debug connectivity test","numResults":1}' )
echo "HTTP Status: $HTTP_CODE "
if [ "$HTTP_CODE " = "200" ]; then
echo "Status: HEALTHY"
python3 -c "import json; d=json.load(open('/tmp/exa-debug.json')); print(f'Results: {len(d.get(\"results\",[]))}')" 2>/dev/null
else
echo "Status: UNHEALTHY"
echo "Response:"
cat /tmp/exa-debug.json | python3 -m json.tool 2>/dev/null || cat /tmp/exa-debug.json
fi
Step 2: Capture Request/Response Details
import Exa from "exa-js" ;
const exa = new Exa (process.env .EXA_API_KEY );
async function debugSearch (query : string ) {
const startTime = performance.now ();
try {
const result = await exa.searchAndContents (query, {
numResults : 3 ,
text : { maxCharacters : 500 },
});
const duration = performance.now () - startTime;
console .log ("=== Debug Info ===" );
console .log (`Query: "${query} "` );
console .log (`Duration: ${duration.toFixed(0 )} ms` );
console .log (`Results: ${result.results.length} ` );
console .log (`Has autoprompt: ${!!result.autopromptString} ` );
for (const r of result. ) {
. ( );
. ( );
}
} ( : ) {
duration = performance. () - startTime;
. ( );
. ( );
. ( );
. ( );
. ( );
. ( );
. ( );
}
}
Step 3: Create Debug Bundle Script
#!/bin/bash
set -euo pipefail
BUNDLE_DIR="exa-debug-$(date +%Y%m%d-%H%M%S) "
mkdir -p "$BUNDLE_DIR "
echo "=== Exa Debug Bundle ===" > "$BUNDLE_DIR /summary.txt"
echo "Generated: $(date -u +%Y-%m-%dT%H:%M:%SZ) " >> "$BUNDLE_DIR /summary.txt"
echo "" >> "$BUNDLE_DIR /summary.txt"
echo "--- Environment ---" >> "$BUNDLE_DIR /summary.txt"
echo "Node: $(node --version 2>/dev/null || echo 'N/A') " >> "$BUNDLE_DIR /summary.txt"
echo "npm: $(npm --version 2>/dev/null || echo 'N/A') " >> "$BUNDLE_DIR /summary.txt"
echo "OS: $(uname -a) " >> "$BUNDLE_DIR /summary.txt"
echo "EXA_API_KEY: ${EXA_API_KEY:+SET} " >> "$BUNDLE_DIR /summary.txt"
echo "" >> "$BUNDLE_DIR /summary.txt"
echo >>
npm list exa-js 2>/dev/null >> || >>
>>
>>
HTTP_CODE=$(curl -s -o -w \
-X POST https://api.exa.ai/search \
-H \
-H \
-d 2>/dev/null)
>>
tar -czf
Output
exa-debug-YYYYMMDD-HHMMSS.tar.gz archive containing:
summary.txt — environment, SDK version, API connectivity
api-response.json — raw API response from test query
Sensitive Data Handling
Always redact before sharing:
API keys and tokens
Query content containing PII
Internal URLs or domain names
Safe to include:
HTTP status codes and error tags
requestId from error responses
SDK and runtime versions
Latency measurements
Error Handling
Issue Cause Solution curl: command not foundcurl not installed Install curl or use node script Empty API response Network firewall Check outbound HTTPS to api.exa.ai 401 in connectivity test Bad API key Regenerate at dashboard.exa.ai Bundle script fails Missing permissions Run with bash not sh
Resources
Next Steps
For rate limit issues, see exa-rate-limits. For common error solutions, see exa-common-errors.
results
console
log
` [${r.score.toFixed(3 )} ] ${r.title} (${r.url} )`
console
log
` Text: ${r.text ? `${r.text.length} chars` : "none" } `
catch
err
any
const
now
console
error
"=== Error Debug ==="
console
error
`Query: "${query} "`
console
error
`Duration: ${duration.toFixed(0 )} ms`
console
error
`Status: ${err.status || "unknown" } `
console
error
`Message: ${err.message} `
console
error
`RequestId: ${err.requestId || err.request_id || "none" } `
console
error
`Error tag: ${err.error_tag || err.tag || "none" } `
"--- SDK ---"
"$BUNDLE_DIR /summary.txt"
"$BUNDLE_DIR /summary.txt"
echo
"exa-js not found"
"$BUNDLE_DIR /summary.txt"
echo
""
"$BUNDLE_DIR /summary.txt"
echo
"--- API Test ---"
"$BUNDLE_DIR /summary.txt"
"$BUNDLE_DIR /api-response.json"
"%{http_code}"
"x-api-key: ${EXA_API_KEY:-missing} "
"Content-Type: application/json"
'{"query":"debug test","numResults":1}'
echo
"HTTP Status: $HTTP_CODE "
"$BUNDLE_DIR /summary.txt"
"$BUNDLE_DIR .tar.gz"
"$BUNDLE_DIR "
echo
"Bundle created: $BUNDLE_DIR .tar.gz"
echo
""
echo
"IMPORTANT: Review $BUNDLE_DIR /summary.txt before sharing."
echo
"Include the requestId from any error responses when contacting hello@exa.ai"