abstract-ip-geolocation-api
Abstract - Email Verification API integration. Manage data, records, and automate workflows. Use when the user wants to interact with Abstract - Email Verification API data.
39
37%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/abstract-ip-geolocation-api/SKILL.mdQuality
Discovery
40%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 description follows a generic template pattern ('Manage data, records, and automate workflows') that fails to convey what email verification actually involves. While it names the specific API product, the lack of concrete email verification actions and meaningful trigger terms makes it nearly indistinguishable from other API integration skills. The 'Use when' clause is tautological rather than providing genuine selection guidance.
Suggestions
Replace generic boilerplate with specific email verification actions, e.g., 'Verifies email addresses, checks deliverability, detects disposable/temporary emails, and validates email format using the Abstract Email Verification API.'
Improve the 'Use when...' clause with natural trigger terms: 'Use when the user wants to verify email addresses, check if an email is valid or deliverable, detect fake/disposable emails, or clean an email list.'
Add file format or data context triggers like 'email list validation', 'bulk email verification', or 'email hygiene' to help distinguish from other API skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'Manage data, records, and automate workflows' without listing any concrete actions specific to email verification. It doesn't mention verifying emails, checking validity, detecting disposable addresses, or any other specific capabilities. | 1 / 3 |
Completeness | It has a 'Use when...' clause, but the trigger is essentially a tautology ('use when the user wants to interact with Abstract - Email Verification API data'). The 'what' is generic boilerplate ('manage data, records, and automate workflows') rather than describing actual email verification capabilities. | 2 / 3 |
Trigger Term Quality | It includes 'Email Verification API' and 'Abstract' which are relevant keywords, but misses natural user terms like 'verify email', 'check email address', 'validate email', 'disposable email', or 'email deliverability'. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'Abstract - Email Verification API' provides some distinctiveness, but the generic phrases 'manage data, records, and automate workflows' could overlap with dozens of other API integration skills. Only the product name differentiates it. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially a generic Membrane CLI integration template with 'Abstract Email Verification API' substituted into the title and a few placeholders. It contains almost no domain-specific guidance about email verification — no example of verifying an email, no sample API responses, no explanation of deliverability fields or how to interpret results. The bulk of the content is reusable Membrane boilerplate that wastes tokens.
Suggestions
Add a concrete, end-to-end example of verifying an email address, including sample input and expected output with key fields (deliverability, is_valid_format, is_disposable, etc.).
Remove or drastically condense the generic Membrane CLI documentation (authentication flow, proxy requests, connection states) — this is not specific to email verification and could be referenced from a shared skill.
Populate the 'Popular actions' section with actual action names and descriptions specific to the Email Verification API instead of just telling the user to discover them.
Remove the introductory paragraph explaining what the API does — Claude can infer this from context and the API name.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is highly verbose and generic. It explains what the Abstract Email Verification API is (Claude knows this), includes extensive Membrane CLI documentation that is not specific to this API, and the vast majority of content is boilerplate that would be identical across any Membrane-connected service. Very little content is specific to email verification. | 1 / 3 |
Actionability | The commands are concrete and copy-paste ready (e.g., membrane connection ensure, membrane action run), but there are no email-verification-specific examples. There's no example of actually verifying an email address, no sample input/output, and the 'Popular actions' section just tells you to discover actions rather than listing them. | 2 / 3 |
Workflow Clarity | The connection setup workflow is reasonably well-sequenced with state handling (READY, CLIENT_ACTION_REQUIRED, etc.), but there are no validation checkpoints for the actual email verification workflow. The skill never walks through a complete end-to-end email verification process with verification of results. | 2 / 3 |
Progressive Disclosure | The content has some structure with headers and sections, but it's a monolithic document with no references to supporting files. The lengthy Membrane CLI boilerplate (authentication, proxy requests, connection states) could be extracted to a shared reference, keeping only email-verification-specific content inline. | 2 / 3 |
Total | 7 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- membranedev/application-skills
- Commit
f484c82
- 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.