Agent skill · software engineering · jeremylongshore
apollo-reference-architecture
Implement Apollo.io reference architecture.
Why this skill is useful
Adds a complete production-ready reference architecture with executable TypeScript code and integration patterns for Apollo.io that are not widely documented.
What it needs
Requires node, postgresql, redis installed locally. Requires apollo account access. About 4k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Apollo Reference Architecture Overview Production-ready reference architecture for Apollo.io integrations. Layered design with API client, service layer, background jobs, database models, CRM sync, and deals pipeline — all built around Apollo's REST API with correct endpoints and x-api-key authentication. Prerequisites Apollo master API key Node.js 18+ with TypeScript PostgreSQL for data layer Redis for job queues Instructions Step 1: Architecture Diagram Step 2: Service Layer Step 3: Deals/Opportunities Service Apollo has a full Deals API for tracking revenue pipeline. Step 4: Background Job Processing Step 5: Database Model Step 6: API Routes Output Layered architecture: API, Service, Client, Jobs, Data LeadService with cached search and retried enrichment DealService with create, list, update, and stage management BullMQ background jobs for async enrichment Database model (Prisma + TypeORM) Express API routes for search, enrichment, and deals Examples For an initial architecture rollout, begin with free search behind an authenticated service boundary, retain only the organization and lead fields the approved use case needs, and encrypt contact data before it enters the database. Store a keyed hash only for deduplication; never persist raw Apollo responses or expose enrichment routes directly without authorization, budget, and audit controls. Run a small staging queue with an explicit dead-letter review path and validate that retrying a job cannot create duplicate contacts or deals. If encryption, authorization, budget enforcement, or idempotency is not demonstrably active, stop the rollout and keep the workflow in the non-production environment. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/apollo-reference-architecture