Agent skill

Apollo Data Handling

by jeremylongshore in jeremylongshore/tons-of-skills-marketplace

Apollo.io data management and compliance. An agent skill from jeremylongshore/tons-of-skills-marketplace.

MITAuto-check passedLegal & Compliance

Install Apollo Data Handling

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill apollo-data-handling -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace apollo-data-handling --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ 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/apollo-data-handling .claude/skills/apollo-data-handling && rm -rf skills-src

Use ~/.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/

Facts

Skill name
apollo-data-handling
GitHub stars
2.8k
Token cost
~2.3k tokens
SKILL.md length
312 words
Files
2 (incl. references)
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Apollo.io data management and compliance. An agent skill from jeremylongshore/tons-of-skills-marketplace.

  • Works in 5 steps: GDPR Subject Access Request (SAR) → Right to Erasure (Delete) → Data Retention Policy → …
  • Handling contact data
  • SKILL.md covers Overview, Prerequisites, Instructions and Output, plus 4 more sections
  • Reaches api.apollo.io; needs APOLLO_API_KEY and APOLLO_ENCRYPTION_KEY

What it does

Apollo Data Handling is an agent skill from jeremylongshore/tons-of-skills-marketplace. Apollo.io data management and compliance. Use when handling contact data, implementing GDPR compliance, or managing data exports and retention. Trigger with phrases like "apollo data", "apollo gdpr", "apollo compliance", "apollo data export", "apollo data retention", "apollo pii".

Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/implementation-guide.md`). Compatibility notes: Designed for Claude Code

It sits in Legal & Compliance, covering GraphQL and Privacy and GDPR. 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.

When your agent uses it

  • Handling contact data
  • Implementing GDPR compliance
  • Managing data exports and retention
  • With phrases like apollo data

Example prompts

  • “apollo data”
  • “apollo gdpr”
  • “apollo compliance”
  • “/apollo-data-handling”

Requirements

  • Node.js
  • A credential in APOLLO_API_KEY
  • A credential in APOLLO_ENCRYPTION_KEY
  • Compatibility (from SKILL.md): Designed for Claude Code
  • Pre-approved tools (allowed-tools): Read, Write, Edit, Bash(kubectl:*), Bash(curl:*)

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. GDPR Subject Access Request (SAR)
  2. Right to Erasure (Delete)
  3. Data Retention Policy
  4. Field-Level Encryption for Local Storage
  5. Audit Logging

What it can do on your machine

Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Write
    • Edit
    • Bash(kubectl:*)
    • Bash(curl:*)

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are typescript).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • api.apollo.io

    Also links to:

    • docs.apollo.io
    • apollo.io
    • gdpr.eu

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • APOLLO_API_KEY
    • APOLLO_ENCRYPTION_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Designed for Claude Code

    From compatibility in the SKILL.md frontmatter.

Context cost

Apollo Data Handling loads about 2.3k tokens when it runs, and up to ~5.4k if it reads all its reference files. Until then it costs about 76 tokens; SKILL.md has 312 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~76
When it runs · the whole SKILL.md, loaded when a task matches
~2.3k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~5.4k

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.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

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.

SKILL.md

The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 312 words, ~2,317 tokens.

Download SKILL.mdSave it as .claude/skills/apollo-data-handling/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
apollo-data-handling
description
Apollo.io data management and compliance. Use when handling contact data, implementing GDPR compliance, or managing data exports and retention. Trigger with phrases like "apollo data", "apollo gdpr", "apollo compliance", "apollo data export", "apollo data retention", "apollo pii".
allowed-tools
Read, Write, Edit, Bash(kubectl:*), Bash(curl:*)
compatibility
Designed for Claude Code
version
1.13.0
license
MIT
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
saas, apollo, compliance

Apollo Data Handling

Overview

Data management, compliance, and governance for Apollo.io contact data. Apollo's database contains 275M+ contacts with PII (emails, phones, LinkedIn profiles). This covers GDPR subject access/erasure, data retention, field-level encryption, and audit logging — using the real Apollo Contacts API endpoints.

Prerequisites

  • Apollo master API key (contacts/delete requires master key)
  • Node.js 18+

Instructions

Step 1: GDPR Subject Access Request (SAR)

Find all data Apollo has on a person and export it.

typescript
// src/data/gdpr.ts
import axios from 'axios';

const client = axios.create({
  baseURL: 'https://api.apollo.io/api/v1',
  headers: { 'Content-Type': 'application/json', 'x-api-key': process.env.APOLLO_API_KEY! },
});

interface SubjectAccessReport {
  email: string;
  dataFound: boolean;
  crmContact?: Record<string, any>;
  apolloDatabaseMatch?: Record<string, any>;
  activeSequences: string[];
  exportedAt: string;
}

export async function handleSAR(email: string): Promise<SubjectAccessReport> {
  const report: SubjectAccessReport = {
    email, dataFound: false, activeSequences: [],
    exportedAt: new Date().toISOString(),
  };

  // 1. Search your CRM contacts (contacts you've saved)
  const { data: crmData } = await client.post('/contacts/search', {
    q_keywords: email,
    per_page: 1,
  });

  if (crmData.contacts?.length > 0) {
    const c = crmData.contacts[0];
    report.dataFound = true;
    report.crmContact = {
      id: c.id, name: c.name, email: c.email, title: c.title,
      phone: c.phone_numbers, organization: c.organization_name,
      city: c.city, state: c.state, country: c.country,
      createdAt: c.created_at, updatedAt: c.updated_at,
      contactStage: c.contact_stage_id,
      labels: c.label_ids,
    };
    report.activeSequences = c.emailer_campaign_ids ?? [];
  }

  // 2. Check Apollo's database (enrichment data)
  try {
    const { data: enrichData } = await client.post('/people/match', { email });
    if (enrichData.person) {
      report.dataFound = true;
      report.apolloDatabaseMatch = {
        name: enrichData.person.name,
        title: enrichData.person.title,
        seniority: enrichData.person.seniority,
        city: enrichData.person.city,
        linkedinUrl: enrichData.person.linkedin_url,
        organization: enrichData.person.organization?.name,
      };
    }
  } catch { /* person not found in Apollo DB */ }

  return report;
}
Step 2: Right to Erasure (Delete)
typescript
export async function handleErasure(email: string): Promise<{
  email: string; erased: boolean; sequencesRemoved: number;
}> {
  // 1. Find the CRM contact
  const { data } = await client.post('/contacts/search', {
    q_keywords: email, per_page: 1,
  });

  const contact = data.contacts?.[0];
  if (!contact) return { email, erased: false, sequencesRemoved: 0 };

  // 2. Remove from all sequences first
  let sequencesRemoved = 0;
  const sequenceRemovalFailures: string[] = [];
  for (const seqId of contact.emailer_campaign_ids ?? []) {
    try {
      await client.post('/emailer_campaigns/remove_or_stop_contact_ids', {
        emailer_campaign_id: seqId,
        contact_ids: [contact.id],
      });
      sequencesRemoved++;
    } catch (err: any) {
      // Do not delete while the contact may still receive outreach.
      sequenceRemovalFailures.push(seqId);
    }
  }

  if (sequenceRemovalFailures.length > 0) {
    throw new Error(`Erasure paused: removal failed for ${sequenceRemovalFailures.length} sequence(s)`);
  }

  // 3. Delete the contact from your CRM (requires master key)
  await client.delete(`/contacts/${contact.id}`);

  return { email, erased: true, sequencesRemoved };
}
Step 3: Data Retention Policy
typescript
// src/data/retention.ts
interface RetentionPolicy {
  maxAgeDays: number;
  inactiveThresholdDays: number;
  protectedLabels: string[];  // label IDs to never auto-delete
}

export async function enforceRetention(policy: RetentionPolicy) {
  const cutoff = new Date();
  cutoff.setDate(cutoff.getDate() - policy.maxAgeDays);

  // Search for old contacts
  const { data } = await client.post('/contacts/search', {
    sort_by_field: 'contact_created_at',
    sort_ascending: true,
    per_page: 100,
  });

  const candidates = data.contacts.filter((c: any) => {
    if (new Date(c.created_at) > cutoff) return false;
    // Skip contacts with protected labels
    const labels = c.label_ids ?? [];
    return !policy.protectedLabels.some((l) => labels.includes(l));
  });

  console.log(`Found ${candidates.length} contacts past ${policy.maxAgeDays}-day retention`);

  let deleted = 0;
  for (const contact of candidates) {
    try {
      await client.delete(`/contacts/${contact.id}`);
      deleted++;
    } catch (err: any) {
      console.error(`Failed to delete ${contact.name}: ${err.message}`);
    }
  }

  return { evaluated: data.contacts.length, deleted };
}
Step 4: Field-Level Encryption for Local Storage
typescript
// src/data/encryption.ts
import crypto from 'crypto';

const KEY = Buffer.from(process.env.APOLLO_ENCRYPTION_KEY!, 'hex');  // 32 bytes
const ALGO = 'aes-256-gcm';

export function encrypt(plaintext: string): string {
  const iv = crypto.randomBytes(16);
  const cipher = crypto.createCipheriv(ALGO, KEY, iv);
  let enc = cipher.update(plaintext, 'utf8', 'hex');
  enc += cipher.final('hex');
  return `${iv.toString('hex')}:${cipher.getAuthTag().toString('hex')}:${enc}`;
}

export function decrypt(ciphertext: string): string {
  const [ivHex, tagHex, enc] = ciphertext.split(':');
  const decipher = crypto.createDecipheriv(ALGO, KEY, Buffer.from(ivHex, 'hex'));
  decipher.setAuthTag(Buffer.from(tagHex, 'hex'));
  let dec = decipher.update(enc, 'hex', 'utf8');
  dec += decipher.final('utf8');
  return dec;
}

// Encrypt PII before storing Apollo data locally
export function encryptContactPII(contact: any) {
  return {
    ...contact,
    email: contact.email ? encrypt(contact.email) : null,
    phone: contact.phone ? encrypt(contact.phone) : null,
    linkedin_url: contact.linkedin_url ? encrypt(contact.linkedin_url) : null,
    name: contact.name,  // keep searchable
  };
}
Step 5: Audit Logging
typescript
// src/data/audit-log.ts
interface AuditEntry {
  timestamp: string;
  action: 'search' | 'enrich' | 'export' | 'delete' | 'sar' | 'erasure';
  userId: string;
  contactId?: string;
  email?: string;
  detail: string;
}

export function logAudit(entry: Omit<AuditEntry, 'timestamp'>) {
  const full: AuditEntry = { ...entry, timestamp: new Date().toISOString() };
  // In production: write to database or cloud logging
  console.log(`[AUDIT] ${full.action} by ${full.userId}: ${full.detail}`);
}

// Usage:
// logAudit({ action: 'erasure', userId: 'privacy@co.com', email: 'user@ex.com',
//   detail: 'GDPR erasure: contact deleted, removed from 2 sequences' });

Output

  • GDPR Subject Access Request handler searching CRM contacts + Apollo database
  • Right to Erasure handler: remove from sequences then delete contact
  • Retention policy enforcer with age-based cleanup and label protection
  • AES-256-GCM field-level encryption for locally stored PII
  • Audit log capturing every data operation with user attribution

Examples

For a verified subject-access and erasure request, authenticate the requester through the organization’s privacy process, create a case ID, and run the SAR against only the authorized contact record. Store the export in the approved restricted location and log its retention deadline without copying raw PII to CI or chat. For erasure, first remove the record from every active sequence; if any removal fails, leave the CRM record intact, record the failed sequence IDs in the case system, and escalate for manual completion. Delete only after all sequence removals succeed, then retain the minimal audit receipt required by the organization’s policy.

Error Handling

IssueResolution
403 on deleteContact deletion requires master API key
Contact in active sequenceRemove from sequence before deleting
Encryption key lostUse a KMS (GCP KMS, AWS KMS) with key versioning
Audit log gapsWrite to durable store before processing, not after

Resources

Next Steps

Proceed to apollo-enterprise-rbac for access control.

© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in skills/.curated/apollo-data-handling of jeremylongshore/tons-of-skills-marketplace.

  • SKILL.md
  • references/implementation-guide.md

Open the folder on GitHubat commit cfae287

Compare with similar skills

Apollo Data Handling 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.

Apollo Data Handling compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Apollo Data Handling this skilljeremylongshore/tons-of-skills-marketplace2.8k—~2.3kAutomated safety check: PassMIT
Eu Data Act Oliver Schmidt Prietzlawve-ai/awesome-legal-skills847—~3.9kAutomated safety check: PassAGPL-3.0
Healthcare Phi Complianceaffaan-m/ECC277k1 repos~1.4kAutomated safety check: PassMIT
Auto Data Discoverymukul975/Privacy-Data-Protection-Skills301—~3.3kAutomated safety check: PassApache-2.0
Cloud Retention Configmukul975/Privacy-Data-Protection-Skills301—~3.7kAutomated safety check: PassApache-2.0
Purpose Based Accessmukul975/Privacy-Data-Protection-Skills301—~3.9kAutomated safety check: PassApache-2.0

Similar skills

  • Eu Data Act Oliver Schmidt Prietz

    lawve-ai/awesome-legal-skills

    Practitioner skill for advising on EU Regulation 2023/2854 (Data Act).

    847 GitHub stars~3.9k tokensUpdated 8 days ago
    Legal & ComplianceAuto-check passed
  • Protected Health Information (PHI) and PII compliance patterns for healthcare applications: data classification, row-level access control, tamper-proof audit trails, schema tagging, and common leak…

    277k GitHub starsUsed in 1 repo~1.4k tokens
    Legal & ComplianceAuto-check passed
  • Auto Data Discovery

    mukul975/Privacy-Data-Protection-Skills

    Implements automated PII discovery and classification using tools like Microsoft Purview, BigID, OneTrust DataDiscovery, and AWS Macie.

    301 GitHub stars~3.3k tokensUpdated 6 mo ago
    Legal & ComplianceAuto-check passed
  • Cloud Retention Config

    mukul975/Privacy-Data-Protection-Skills

    Configures cloud storage retention policies across AWS S3, Azure Blob Storage, and Google Cloud Storage.

    301 GitHub stars~3.7k tokensUpdated 6 mo ago
    Legal & ComplianceAuto-check passed
  • Purpose Based Access

    mukul975/Privacy-Data-Protection-Skills

    Design and implement Purpose-Based Access Control (PBAC) architecture including purpose ontology definition, policy engine configuration, audit logging of purpose verification at query time, and…

    301 GitHub stars~3.9k tokensUpdated 6 mo ago
    Legal & ComplianceAuto-check passed
  • Neighbor Dispute Resolver

    mohitagw15856/pm-claude-skills

    Handle a neighbor conflict — noise, boundaries, parking, shared costs, pets — with a measured approach that de-escalates first and keeps a paper trail if it has to go formal.

    1.4k GitHub stars~1.3k tokensUpdated yesterday
    Legal & ComplianceAuto-check passed

More from jeremylongshore/tons-of-skills-marketplace

All 3,342 skills in this repo
  • Performing Security Code Review

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.

    2.8k GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check: notes
  • Adapting Transfer Learning Models

    jeremylongshore/tons-of-skills-marketplace

    Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Agent Context Loader

    jeremylongshore/tons-of-skills-marketplace

    Execute proactive auto-loading: automatically detects and loads agents.md files.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Aggregating Performance Metrics

    jeremylongshore/tons-of-skills-marketplace

    Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.

    2.8k GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • Analyzing Capacity Planning

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.

    2.8k GitHub stars~947 tokensUpdated today
    Auto-check passed
  • Analyzing Database Indexes

    jeremylongshore/tons-of-skills-marketplace

    Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~2k tokensUpdated today
    Auto-check passed

Questions about Apollo Data Handling

What does Apollo Data Handling do?

Apollo.io data management and compliance. An agent skill from jeremylongshore/tons-of-skills-marketplace. Apollo Data Handling is an agent skill from jeremylongshore/tons-of-skills-marketplace.io data management and compliance.

When should I use Apollo Data Handling?

Apollo Data Handling fits situations like: handling contact data; implementing GDPR compliance; managing data exports and retention; with phrases like apollo data.

How do I install Apollo Data Handling in Claude Code?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill apollo-data-handling -a claude-code`. Or copy the skill folder (skills/.curated/apollo-data-handling in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/apollo-data-handling in your project. Claude Code loads it when a task matches its description.

How do I install Apollo Data Handling in Codex?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill apollo-data-handling -a codex`. Or copy the skill folder (skills/.curated/apollo-data-handling in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/apollo-data-handling in your project. Codex loads it when a task matches its description.

Can I use Apollo Data Handling in Cursor, Gemini CLI or GitHub Copilot?

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 apollo-data-handling -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/apollo-data-handling, .gemini/skills/apollo-data-handling, .github/skills/apollo-data-handling and .opencode/skills/apollo-data-handling in your project.

What does Apollo Data Handling need to run?

Going by SKILL.md and its folder, Apollo Data Handling needs credentials named APOLLO_API_KEY and APOLLO_ENCRYPTION_KEY. Our summary lists: Node.js; A credential in APOLLO_API_KEY; A credential in APOLLO_ENCRYPTION_KEY. Its frontmatter pre-approves these tools: Read, Write, Edit, Bash(kubectl:*), Bash(curl:*). Compatibility (from SKILL.md): Designed for Claude Code.

Does Apollo Data Handling access the network?

SKILL.md names 4 domains. In commands or code: api.apollo.io; the agent is likely to contact it when it follows the instructions. As links in the text: docs.apollo.io, apollo.io and gdpr.eu. This is read from the text; nothing was executed.

Is Apollo Data Handling safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Apollo Data Handling use?

Apollo Data Handling is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Apollo Data Handling use?

About 2.3k tokens (SKILL.md is roughly 9.3k 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 3.1k tokens, read only when the agent opens those files.

What are the alternatives to Apollo Data Handling?

Skills that share tags, products or a category with Apollo Data Handling: Eu Data Act Oliver Schmidt Prietz (lawve-ai/awesome-legal-skills, 847 stars), Healthcare Phi Compliance (affaan-m/ECC, 277k stars), Auto Data Discovery (mukul975/Privacy-Data-Protection-Skills, 301 stars) and Cloud Retention Config (mukul975/Privacy-Data-Protection-Skills, 301 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Apollo Data Handling?

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.