apollo-data-handling

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".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with complete, executable TypeScript against real Apollo endpoints and clear step sequencing. Its main weaknesses are missing validation checkpoints for destructive/batch operations and poor progressive disclosure — an orphaned implementation-guide.md reference that the body never points to while inlining the very detail it should hold.

Suggestions

Add validation/verification checkpoints to destructive flows: confirm sequence removal succeeded before deleting a contact, and run retention as a dry-run (report candidates) before performing bulk deletes.

Slim the inline code in SKILL.md to concise overview snippets and move full implementations into references/implementation-guide.md with clearly signaled one-level-deep links (e.g., "Full code: see [implementation-guide.md](references/implementation-guide.md)").

Tighten the body by removing the complete inline AES-256-GCM encrypt/decrypt module — show the call site and link to the reference for the crypto details.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean executable code without explaining concepts Claude already knows, but it inlines five full implementations (e.g., the complete AES-256-GCM crypto module) that could be tightened or moved to the bundled reference, so it does not fully meet the every-token-earns-its-place anchor.	2 / 3
Actionability	Each step ships complete, copy-paste-ready TypeScript hitting real Apollo endpoints (/contacts/search, /people/match, /contacts/{id} delete) with typed interfaces, matching the fully-executable anchor.	3 / 3
Workflow Clarity	Steps are clearly sequenced (Step 1–5), but destructive and batch operations lack validation checkpoints — erasure deletes the contact without verifying sequence removal succeeded, and retention bulk-deletes with no dry-run/confirmation — which caps clarity at 2 per the destructive-operations guideline.	2 / 3
Progressive Disclosure	Sections are well-organized and a bundle file (references/implementation-guide.md) exists, but the body never signals it and instead inlines full implementations that overlap with the guide; content that should be a one-level-deep reference is kept inline, fitting the 2-anchor rather than the well-split 3-anchor.	2 / 3
	Total	9 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A well-formed description that clearly states the skill's purpose, provides an explicit Use-when trigger clause, and lists natural apollo-prefixed trigger phrases. It is concise, uses third-person imperative voice, and is clearly distinguishable from other skills.

Dimension	Reasoning	Score
Specificity	Names the Apollo.io domain and enumerates multiple concrete actions — "handling contact data, implementing GDPR compliance, or managing data exports and retention" — matching the multi-action anchor rather than the single-domain anchor at 2.	3 / 3
Completeness	Explicitly answers both what ("Apollo.io data management and compliance") and when ("Use when handling contact data...") with an explicit trigger clause, satisfying the top anchor.	3 / 3
Trigger Term Quality	Lists natural phrases a user would actually say — "apollo data", "apollo gdpr", "apollo compliance", "apollo data export", "apollo data retention", "apollo pii" — giving good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	The "apollo" prefix on every trigger term carves out a clear niche unlikely to fire for unrelated skills; not generic enough to conflict as the 1- and 2-anchors describe.	3 / 3
	Total	12 / 12 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 02d6341

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.