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

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/saas-packs/instantly-pack/skills/instantly-data-handling/SKILL.md

Quality

Content

65%Weight 40%Scale 1-5

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

The content is concrete and actionable with mostly efficient code, but its destructive and batch operations lack explicit validation checkpoints and it is a monolithic file with no progressive disclosure or shipped supporting bundle. Tightening compliance-flow verification and splitting reference material into files would most improve it.

Suggestions

Add explicit verification to destructive/batch workflows: for GDPR deletion, confirm the lead no longer appears via search-by-contact after deletion and surface failures; for bulk lead/block-list operations, require a confirm or dry-run step before applying.

Split the API endpoint table and error catalog into a reference file (e.g. references/api.md) referenced one level deep, so the SKILL.md body stays a lean overview.

Resolve the undefined client dependency: either ship the ./src/instantly/client bundle (with client.leads.list/delete) or standardize all examples on the client.request pattern so code is copy-paste self-contained.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient code with lean comments and assumes Claude's competence, but includes some narration (console.log compliance logging) and commented example cruft in seedBlockList that could be trimmed.	4 / 5
Actionability	Provides concrete, executable TypeScript functions with real endpoints and field names covering common cases, but references an undefined InstantlyClient/client.leads API and an absent ./src/instantly/client bundle, so it is not fully self-contained.	4 / 5
Workflow Clarity	A clear five-step sequence with some import-time validation exists, but destructive and batch operations (GDPR deletion across campaigns, bulk lead delete, bulk block-list create) lack explicit verification checkpoints and confirmation, capping workflow clarity at 3 per the destructive-ops rule.	3 / 5
Progressive Disclosure	Section structure is present and coherent, but everything (full API endpoint table, error catalog, all code) is inlined in a 336-line file with no separate reference files, and an inline ./src/instantly/client reference points to a non-existent bundle.	3 / 5
	Total	14 / 20 Passed

Description

87%Weight 40%Scale 1-5

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

The description clearly and explicitly covers both capability and trigger conditions with good specificity and a well-scoped niche. Its main limitation is slightly less comprehensive action and keyword coverage, which keeps specificity and trigger quality just below the top.

Dimension	Reasoning	Score
Specificity	Names the domain plus several concrete actions (lead imports, block lists, unsubscribe flows, compliance), but omits others (lead CRUD, interest status, lead-list management), so coverage has minor gaps rather than being comprehensive.	4 / 5
Completeness	Explicitly answers both what ('Implement Instantly.ai lead data management, GDPR/CAN-SPAM compliance, and list operations') and when ('Use when handling lead imports...') with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Six explicit trigger phrases ('instantly leads', 'instantly data', 'instantly GDPR', etc.) give good keyword coverage with natural terms, but all follow the same 'instantly X' pattern and lack broader synonyms/variations.	4 / 5
Distinctiveness Conflict Risk	A clear Instantly.ai lead/compliance niche with 'instantly'-prefixed triggers makes it highly distinct with minimal conflict risk against other skills.	5 / 5
	Total	18 / 20 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
Path: plugins/saas-packs/instantly-pack/skills/instantly-data-handling/SKILL.md
Commit: 0540a62

Reviewed: about 18 hours 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.