abuselpdb
AbuselPDB integration. Manage data, records, and automate workflows. Use when the user wants to interact with AbuselPDB data.
Install with Tessl CLI
npx tessl i github:membranedev/application-skills --skill abuselpdb61
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 fails to communicate what AbuseIPDB actually does (IP abuse/threat intelligence database) and uses generic boilerplate language that could apply to any integration. The misspelling of 'AbuseIPDB' as 'AbuselPDB' is also problematic. While it includes a 'Use when' clause, the triggers are too vague to help Claude distinguish this skill from others.
Suggestions
Replace generic actions with AbuseIPDB-specific capabilities: 'Check IP reputation scores, report malicious IPs, query the blacklist database, retrieve abuse confidence scores'
Add domain-specific trigger terms: 'Use when checking IP addresses for abuse, querying threat intelligence, reporting malicious activity, or looking up IP reputation/blacklist status'
Fix the typo: 'AbuselPDB' should be 'AbuseIPDB'
| 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 specific operations can be performed with AbuseIPDB (e.g., check IP reputation, report malicious IPs, query blacklists). | 1 / 3 |
Completeness | Has a 'Use when...' clause which addresses the 'when' question, but the 'what' is extremely vague ('Manage data, records, and automate workflows' could apply to almost any integration). The trigger guidance is also too generic. | 2 / 3 |
Trigger Term Quality | Includes 'AbuseIPDB' (though misspelled as 'AbuselPDB') which is a relevant keyword, but misses natural terms users might say like 'IP reputation', 'malicious IP', 'blacklist check', 'report abuse', or 'IP threat intelligence'. | 2 / 3 |
Distinctiveness Conflict Risk | The AbuseIPDB name provides some distinctiveness, but 'Manage data, records, and automate workflows' is generic enough to overlap with many other integration skills. Without specific IP/security-related triggers, it could conflict with other data management tools. | 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 AbuseIPDB integration via Membrane with good structure and practical examples. However, it includes unnecessary introductory explanation, lacks validation checkpoints in workflows, and could benefit from splitting reference content (action tables, proxy options) into separate files.
Suggestions
Remove the introductory paragraph explaining what AbuseIPDB is - Claude already knows this
Add validation steps after key operations (e.g., 'Verify connection succeeded by checking the output contains connectionId')
Move the popular actions table and proxy request options to separate reference files (e.g., ACTIONS.md, PROXY.md) with links from the main skill
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanation (e.g., 'AbuseIPDB is a database of IP addresses...') that Claude already knows, but the core content is reasonably efficient with good use of tables and code blocks. | 2 / 3 |
Actionability | Provides fully executable CLI commands with clear syntax, including parameter passing examples. Commands are copy-paste ready with placeholders clearly marked (CONNECTION_ID, ACTION_ID). | 3 / 3 |
Workflow Clarity | Steps for setup and connection are sequenced but lack validation checkpoints. No explicit verification steps after connection creation or action execution to confirm success before proceeding. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with sections, but everything is inline in one file. The popular actions table and proxy options could be split into separate reference files for better navigation. | 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.