Agent skill · software engineering · jeremylongshore
exa-deploy-integration
Deploy an Exa integration with server-side credentials, bounded concurrency, canary controls, and explicit rollback of scheduled work. Use when operating or reviewing this Exa boundary. Trigger with "Exa deploy integration", "review Exa deploy integration", or "fix Exa deploy integration".
Why this skill is useful
Adds executable deployment scripts for Vercel, Docker, and Google Cloud Run that automate the deployment process for Exa-powered applications.
What it needs
Requires docker, gcloud, vercel installed locally. Requires exa account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Exa Reversible Deployment Workflow Overview Deploy an Exa integration with server-side credentials, bounded concurrency, canary controls, and explicit rollback of scheduled work. Treat credentials, queries, retrieved content, generated output, spend, and destructive state as separately governed boundaries. Prerequisites The target repository, environment, Exa team, product surface, and accountable owner. The workload's data classification, latency and freshness promise, cost ceiling, and retention policy. Current first-party documentation plus credentials only for a narrowly approved live check. Current Contract Production workers should call Exa from trusted server runtimes. Search and Contents can be synchronous, while Agent, Monitors, Websets, and Batch require durable IDs and terminal-state reconciliation. Deployments must account for queues and scheduled resources that outlive a process release. Authentication For normal REST work, inject EXAAPIKEY from an approved server-side secret manager and send it only as Authorization: Bearer to the configured first-party Exa API host. Team Management service keys, hosted MCP OAuth or enterprise managed authorization, and payment-protocol calls are separate trust models. Never print, commit, place in a URL, or expose a credential to an untrusted client. Instructions 1. Identify every runtime, queue, webhook, schedule, key, and Exa product in the release. 2. Inject environment-specific secrets and deny them to browser or preview builds. 3. Configure timeouts, endpoint budgets, queue bounds, and content-size limits. 4. Deploy dark, validate configuration, then enable a small synthetic canary. 5. Observe request IDs, error classes, latency, cost, and asynchronous backlog. 6. Rollback code and separately pause or reconcile monitors, batches, and runs. Tool Discipline Use Read, Glob, and Grep to inspect repository code, configuration, fixtures, and evidence. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/exa-deploy-integration