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".
77
73%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/apollo-pack/skills/apollo-data-handling/SKILL.mdQuality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid skill description that clearly identifies its niche (Apollo.io data management and compliance) and provides explicit trigger guidance. Its main weakness is that the capability descriptions are somewhat high-level rather than listing specific concrete actions. The explicit trigger phrases and 'Use when' clause make it highly functional for skill selection.
Suggestions
Add more specific concrete actions, e.g., 'Delete contact records, generate GDPR compliance reports, configure data retention policies, handle PII redaction requests, export contact lists.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Apollo.io data management) and mentions some actions like 'handling contact data', 'implementing GDPR compliance', 'managing data exports and retention', but these are fairly high-level and not deeply concrete (e.g., doesn't specify exact operations like 'delete contact records', 'generate compliance reports', 'configure retention policies'). | 2 / 3 |
Completeness | Clearly answers both 'what' (Apollo.io data management and compliance, handling contact data, GDPR compliance, data exports and retention) and 'when' (explicit 'Use when...' clause and 'Trigger with phrases like...' section providing clear activation guidance). | 3 / 3 |
Trigger Term Quality | Includes a good set of natural trigger terms: 'apollo data', 'apollo gdpr', 'apollo compliance', 'apollo data export', 'apollo data retention', 'apollo pii', plus contextual terms like 'contact data', 'GDPR compliance'. These are terms users would naturally use when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Very clearly scoped to Apollo.io specifically, with distinct triggers that include the 'apollo' prefix. Unlikely to conflict with generic data management or other CRM-related skills due to the platform-specific naming. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides highly actionable, executable TypeScript code covering GDPR compliance operations with real Apollo API endpoints, which is its primary strength. However, it suffers from being a monolithic wall of code that should be split into referenced bundle files, and it lacks validation checkpoints for destructive batch operations like retention enforcement. The overview section contains unnecessary context about Apollo's database size and what PII means.
Suggestions
Split the inline code into actual bundle files (e.g., src/data/gdpr.ts, src/data/retention.ts, src/data/encryption.ts, src/data/audit-log.ts) and reference them from a concise SKILL.md overview.
Add explicit validation checkpoints for destructive operations — especially in retention enforcement, add a dry-run mode or confirmation step before batch deletion, and verify deletion success after each delete call.
Remove the overview explanation of what Apollo's database contains and what PII stands for — Claude already knows these concepts. Keep only the actionable prerequisites and jump straight to instructions.
Add a verification step after erasure (re-search for the contact to confirm deletion) to create a proper feedback loop for this critical GDPR operation.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly long with extensive inline code that could be split into referenced files. The overview paragraph explaining what Apollo's database contains and what PII means is unnecessary context for Claude. However, the code itself is reasonably tight without excessive commentary. | 2 / 3 |
Actionability | The skill provides fully executable TypeScript code with real Apollo API endpoints, concrete request/response structures, and copy-paste ready implementations for each operation (SAR, erasure, retention, encryption, audit logging). | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced and the erasure workflow correctly orders operations (remove from sequences before deleting). However, there are no explicit validation checkpoints — for example, no verification that the contact was actually deleted, no confirmation step before batch retention deletion, and no feedback loop for the retention enforcement which is a destructive batch operation. | 2 / 3 |
Progressive Disclosure | All content is monolithically inlined in a single file — over 200 lines of code that should be split into referenced files (gdpr.ts, retention.ts, encryption.ts, audit-log.ts are even named in comments but not actually separate). No bundle files exist despite the content clearly warranting them. The SKILL.md should be an overview pointing to these implementation files. | 1 / 3 |
Total | 8 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 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 | 9 / 11 Passed | |
- Commit
3a2d27d
- Reviewed
Table of Contents
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.