abuselpdb-automation

Automate Abuselpdb tasks via Rube MCP (Composio). Always search tools first for current schemas.

7.00x

Quality

42%

Does it follow best practices?

Impact

77%

7.00x

Average score across 3 eval scenarios

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./composio-skills/abuselpdb-automation/SKILL.md

Quality

Content

77%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a well-structured skill that efficiently teaches the Abuselpdb automation workflow via Rube MCP. Its strengths are concise writing and clear workflow sequencing with validation steps. The main weakness is that tool call examples are pseudo-code patterns rather than fully executable examples, and some tools mentioned in the quick reference lack explanation in the body.

Suggestions

Provide at least one complete, executable example showing a real Abuselpdb operation end-to-end with actual tool slugs and arguments

Either explain RUBE_REMOTE_WORKBENCH and RUBE_GET_TOOL_SCHEMAS in the body or remove them from the quick reference to avoid confusion

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient, avoiding unnecessary explanations. It assumes Claude understands MCP, APIs, and workflow patterns without over-explaining basic concepts.	3 / 3
Actionability	Provides concrete tool call patterns with parameter examples, but uses pseudo-code style rather than fully executable code. The tool calls show structure but aren't copy-paste ready for any specific programming language or environment.	2 / 3
Workflow Clarity	Clear 3-step workflow with explicit sequence (discover → check connection → execute). Includes validation checkpoint for connection status ('Confirm connection status shows ACTIVE before running any workflows') and known pitfalls section addresses error prevention.	3 / 3
Progressive Disclosure	Good structure with sections and quick reference table, but links to external toolkit docs without clear signaling of what's there. The content is appropriately sized for a single file, though the quick reference table introduces tools (RUBE_REMOTE_WORKBENCH, RUBE_GET_TOOL_SCHEMAS) not explained in the main content.	2 / 3
	Total	10 / 12 Passed

Description

7%Scale 1-3

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 is severely underdeveloped. It fails to specify what AbuseIPDB tasks can be performed, uses technical jargon without natural trigger terms, and lacks any 'Use when...' guidance. The typo in 'Abuselpdb' further reduces clarity and searchability.

Suggestions

List specific AbuseIPDB actions like 'check IP reputation, report malicious IPs, query blacklist status, retrieve abuse confidence scores'

Add a 'Use when...' clause with natural trigger terms: 'Use when checking if an IP is malicious, reporting abuse, looking up IP reputation, or querying AbuseIPDB'

Fix the typo 'Abuselpdb' to 'AbuseIPDB' and include variations users might say like 'IP blacklist', 'abuse database', 'malicious IP check'

Dimension	Reasoning	Score
Specificity	The description says 'Automate Abuselpdb tasks' which is extremely vague - it doesn't specify what tasks can be automated (checking IPs, reporting abuse, querying blacklists, etc.). No concrete actions are listed.	1 / 3
Completeness	The 'what' is vague ('automate tasks') and there is no 'when' clause or explicit trigger guidance. The instruction to 'search tools first' is operational guidance, not a usage trigger.	1 / 3
Trigger Term Quality	'Abuselpdb' appears to be a typo for 'AbuseIPDB', and 'Rube MCP (Composio)' is technical jargon. No natural user terms like 'IP reputation', 'abuse check', 'blacklist', or 'malicious IP' are included.	1 / 3
Distinctiveness Conflict Risk	The mention of 'Abuselpdb' and 'Rube MCP (Composio)' does create some distinctiveness for this specific integration, but the vague 'tasks' language could overlap with other automation or security-related skills.	2 / 3
	Total	5 / 12 Passed

Validation

90%

Warnings & errors only

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: ComposioHQ/awesome-claude-skills
Path: composio-skills/abuselpdb-automation/SKILL.md
Commit: 2790447

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.