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.
55
45%
Does it follow best practices?
Impact
Pending
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 boilerplate template pattern that fails to convey the specific capabilities of an email verification API. The 'what' portion is entirely generic ('manage data, records, and automate workflows') and could apply to virtually any API integration skill. The 'when' clause is tautological and provides no real selection guidance.
Suggestions
Replace generic actions with specific email verification capabilities, e.g., 'Verifies email addresses for deliverability, detects disposable/temporary emails, checks MX records and SMTP validity.'
Add natural trigger terms users would actually say, such as 'verify email', 'validate email address', 'check if email is real', 'email deliverability', 'disposable email detection'.
Rewrite the 'Use when...' clause with meaningful triggers, e.g., 'Use when the user needs to validate email addresses, check email deliverability, or detect fake/disposable emails before sending.'
| 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 and the 'when' doesn't provide meaningful guidance beyond restating the skill name. | 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. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is a generic Membrane CLI integration template with minimal Abstract Email Verification API-specific content. While the CLI workflow is clearly documented with executable commands, the skill lacks concrete examples of actually verifying an email address, expected output schemas, and error handling specific to the API. The content would benefit significantly from API-specific examples and less boilerplate.
Suggestions
Add a concrete end-to-end example showing email verification: discovering the verify action, running it with a real email input, and interpreting the output fields (deliverability, is_valid_format, etc.).
Remove or condense the introductory paragraph explaining what email verification is — Claude already knows this.
Include expected output schema or example response from a verification action so Claude knows how to interpret and present results to users.
Clarify the API overview section ('Verification > Email > Result', 'Account > Balance') — either explain what these represent or remove them if they don't add actionable value.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content includes some unnecessary explanation (e.g., 'It's used by businesses and developers to reduce bounce rates and improve email marketing campaign performance') and generic Membrane CLI boilerplate that isn't specific to the Abstract Email Verification API. However, it's not excessively verbose overall. | 2 / 3 |
Actionability | Commands are concrete and copy-paste ready for the Membrane CLI workflow, but there are no API-specific examples showing actual email verification (e.g., running a verify action with a specific email input and expected output). The skill is mostly generic Membrane instructions with placeholder values like 'QUERY' and 'CONNECTION_ID'. | 2 / 3 |
Workflow Clarity | The steps are sequenced logically (install → authenticate → connect → discover actions → run actions), and the action creation flow includes polling and state checking. However, there's no validation or error-handling guidance for the email verification results themselves, and no feedback loop for common failure scenarios. | 2 / 3 |
Progressive Disclosure | The content is reasonably structured with clear sections, but it's a monolithic file with no references to external documentation for advanced topics. The API overview section listing 'Verification > Email > Result' and 'Account > Balance' is cryptic and unexplained, adding no real value. | 2 / 3 |
Total | 8 / 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
56d7336
- 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.