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.
Install with Tessl CLI
npx tessl i github:membranedev/application-skills --skill abstract-ip-geolocation-api61
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 suffers from generic boilerplate language that fails to explain what email verification actually does or when users would need it. The 'Use when' clause is circular and unhelpful. The description would benefit greatly from specific email verification actions and natural trigger terms users would actually say.
Suggestions
Replace generic actions with specific email verification capabilities like 'Validate email addresses, check deliverability, detect disposable/temporary emails, verify email format and domain'
Rewrite the 'Use when' clause with natural triggers: 'Use when the user wants to validate email addresses, check if emails are real, detect fake/disposable emails, or verify email deliverability'
Add common user phrases as trigger terms: 'email validation', 'check email', 'verify email address', 'email deliverability', 'fake email detection'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'Manage data, records, and automate workflows' without specifying concrete actions. It doesn't explain what email verification actually does (e.g., validate email addresses, check deliverability, detect disposable emails). | 1 / 3 |
Completeness | Has a 'Use when...' clause but it's circular ('when the user wants to interact with Abstract - Email Verification API data'). The 'what' is generic and the 'when' doesn't provide meaningful trigger guidance beyond restating the skill name. | 2 / 3 |
Trigger Term Quality | Includes 'Email Verification API' and 'Abstract' as keywords, but misses natural user terms like 'validate email', 'check email address', 'email deliverability', 'verify email', or 'disposable email detection'. | 2 / 3 |
Distinctiveness Conflict Risk | The 'Abstract - Email Verification API' name provides some distinctiveness, but 'Manage data, records, and automate workflows' is extremely generic and could apply to dozens of API integration skills. | 2 / 3 |
Total | 7 / 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 skill provides solid, actionable CLI commands for integrating with the Abstract Email Verification API via Membrane. The main weaknesses are some unnecessary introductory content, a mismatch in the connector search command (references 'abstract-ip-geolocation-api' instead of email verification), and missing validation/error handling steps in the workflows.
Suggestions
Fix the connector search command to use the correct connector name for Abstract Email Verification API instead of 'abstract-ip-geolocation-api'
Remove the introductory paragraph explaining what the API does - Claude already knows this context
Add explicit validation steps after connection creation (e.g., 'Verify connection succeeded by running membrane connection list')
Add error handling guidance for common failure scenarios (e.g., what to do if authentication fails or connection times out)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some unnecessary explanation (e.g., explaining what the API does when Claude would know this). The overview section listing 'Verification > Email > Result' and 'Account > Balance' adds little value. | 2 / 3 |
Actionability | Provides fully executable CLI commands throughout with clear syntax examples. Commands are copy-paste ready with proper flags and JSON parameter passing demonstrated. | 3 / 3 |
Workflow Clarity | Steps are listed for setup and connection but lack explicit validation checkpoints. The workflow for checking existing connections vs creating new ones could be clearer with decision points and error handling guidance. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but everything is inline in one file. The proxy request options table and best practices could potentially be separated, though for this skill length it's acceptable. | 2 / 3 |
Total | 9 / 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 | |
- 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.