instantly-data-handling
Implement Instantly.ai lead data management, GDPR/CAN-SPAM compliance, and list operations. Use when handling lead imports, managing block lists, implementing unsubscribe flows, or ensuring compliance with email regulations. Trigger with phrases like "instantly leads", "instantly data", "instantly GDPR", "instantly block list", "instantly lead management", "instantly unsubscribe".
84
82%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
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.
This is a strong skill description that clearly identifies the platform (Instantly.ai), lists specific capabilities (lead management, GDPR/CAN-SPAM compliance, block lists, unsubscribe flows), provides explicit 'Use when' guidance, and includes natural trigger phrases. The description is well-structured, uses third person voice correctly, and is concise without being vague.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: lead data management, GDPR/CAN-SPAM compliance, list operations, lead imports, block lists, unsubscribe flows, and email regulation compliance. | 3 / 3 |
Completeness | Clearly answers both 'what' (lead data management, GDPR/CAN-SPAM compliance, list operations) and 'when' (explicit 'Use when' clause covering lead imports, block lists, unsubscribe flows, compliance) with additional explicit trigger phrases. | 3 / 3 |
Trigger Term Quality | Includes good coverage of natural trigger terms like 'instantly leads', 'instantly GDPR', 'instantly block list', 'instantly unsubscribe', plus domain terms like 'lead imports', 'CAN-SPAM', and 'email regulations' that users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive by scoping to Instantly.ai specifically, with domain-specific triggers like 'instantly leads', 'instantly block list', and 'instantly GDPR' that are unlikely to conflict with generic email or CRM skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill with executable TypeScript examples covering the full spectrum of Instantly lead management and compliance operations. Its main weaknesses are the lack of explicit validation checkpoints for destructive operations (GDPR deletion, bulk deletes) and the overall length that could benefit from splitting detailed implementations into separate reference files. The code quality is high but some comments and placeholder data add unnecessary tokens.
Suggestions
Add explicit validation/verification steps after destructive operations like GDPR deletion (e.g., confirm the lead no longer appears in search, verify block list entry was created) to create proper feedback loops.
Extract the detailed function implementations (Steps 2-5) into separate referenced files (e.g., `instantly-lead-import.md`, `instantly-compliance.md`) and keep SKILL.md as a concise overview with key patterns and navigation.
Remove obvious comments like '// Single entry', '// Or bulk add', and trim placeholder data in seedBlockList to reduce token usage.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly comprehensive but includes some unnecessary verbosity — comments explaining obvious things (e.g., '// Single entry', '// Or bulk add'), the seedBlockList function with placeholder domains that aren't universally applicable, and some explanatory comments Claude wouldn't need. The overview paragraph explaining what cold email compliance is adds marginal value. | 2 / 3 |
Actionability | The code examples are fully executable TypeScript with proper types, concrete API paths, request bodies, and error handling. Functions are copy-paste ready with clear interfaces, and the API endpoint reference table provides a complete quick-reference. | 3 / 3 |
Workflow Clarity | Steps are numbered and sequenced logically (list management → import → operations → block list → compliance), but there are no explicit validation checkpoints between steps. The GDPR deletion and bulk delete operations are destructive but lack verification steps (e.g., confirming deletion succeeded, validating the block list was updated before proceeding). The import function has good internal validation but the overall workflow lacks feedback loops. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and includes references to external resources and a next-steps pointer. However, at ~250 lines of code, some sections (like the full block list seeding example or the complete lead operations) could be split into referenced files. The API endpoint table and error handling table are good inline summaries, but the skill is borderline monolithic. | 2 / 3 |
Total | 9 / 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
70e9fa4
- 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.