abuselpdb
AbuselPDB integration. Manage data, records, and automate workflows. Use when the user wants to interact with AbuselPDB data.
52
58%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/abuselpdb/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.
The description is weak overall, relying on generic phrases like 'manage data, records, and automate workflows' that could apply to virtually any integration skill. It fails to describe the specific capabilities of AbuseIPDB (IP reputation checking, abuse reporting, blacklist queries) and contains what appears to be a typo ('AbuselPDB' instead of 'AbuseIPDB'). The 'Use when' clause is present but too vague to be useful for skill selection.
Suggestions
Replace generic phrases with specific AbuseIPDB actions such as 'Check IP address reputation scores, report abusive IPs, query the AbuseIPDB blacklist, and retrieve abuse confidence data'.
Expand the 'Use when' clause with natural trigger terms: 'Use when the user asks about IP reputation, wants to check if an IP is malicious, needs to report abuse, or mentions AbuseIPDB, IP blacklists, or abuse confidence scores'.
Fix the apparent typo 'AbuselPDB' to 'AbuseIPDB' to ensure proper keyword matching.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'manage data, records, and automate workflows' without listing any concrete actions specific to AbuseIPDB (e.g., check IP reputation, report abusive IPs, query blacklists, retrieve abuse confidence scores). | 1 / 3 |
Completeness | It has a weak 'what' (manage data, records, automate workflows) and a 'when' clause ('Use when the user wants to interact with AbuselPDB data'), but the 'when' is essentially just restating the 'what' without providing explicit trigger scenarios. | 2 / 3 |
Trigger Term Quality | It includes 'AbuselPDB' (appears to be a typo for AbuseIPDB) as a keyword, but misses natural trigger terms users would say like 'IP reputation', 'abuse report', 'blacklist check', 'malicious IP', or 'IP address lookup'. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'AbuselPDB' provides some distinctiveness as a specific service, but 'manage data, records, and automate workflows' is extremely generic and could overlap with many integration or data management skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
77%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 integration skill with excellent actionability and workflow clarity — every step has executable commands and the connection state machine is well-documented with proper feedback loops. The main weaknesses are some unnecessary explanatory text (explaining what AbuseIPDB is, motivational phrases about Membrane) and empty description fields in the popular actions table that reduce usefulness.
Suggestions
Remove the opening paragraph explaining what AbuseIPDB is — Claude already knows this. Start directly with the overview or working instructions.
Fill in the empty description fields in the popular actions table, or remove the table if descriptions aren't available.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explains what AbuseIPDB is, which Claude already knows. The Membrane CLI setup and authentication sections are reasonably efficient but include some unnecessary explanation (e.g., 'Membrane handles authentication and credentials refresh automatically — so you can focus on the integration logic rather than auth plumbing'). The proxy section and best practices add useful but somewhat verbose content. | 2 / 3 |
Actionability | The skill provides fully executable, copy-paste-ready CLI commands for every step: installation, authentication, connection setup, action discovery, action execution, and proxy requests. Flag tables and JSON parameter examples are concrete and specific. | 3 / 3 |
Workflow Clarity | The multi-step connection workflow is clearly sequenced with explicit state-based branching (READY, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR, SETUP_FAILED). It includes polling/retry loops for BUILDING state and clear instructions for each possible outcome, forming a proper feedback loop. | 3 / 3 |
Progressive Disclosure | The content is reasonably structured with clear sections and headers, but it's a monolithic document with no references to supporting files. The popular actions table has empty description fields, and the proxy request details and best practices could potentially be split out. However, the overall length is manageable. | 2 / 3 |
Total | 10 / 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.