Name: ip2whois
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

ip2whois

IP2WHOIS integration. Manage data, records, and automate workflows. Use when the user wants to interact with IP2WHOIS data.

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/ip2whois/SKILL.md

Quality

Content

67%Weight 40%Scale 1-5

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

The content is a well-structured, largely executable guide to driving IP2WHOIS through the Membrane CLI with genuine validation checkpoints. It would improve by trimming explanatory filler, fixing the broken step numbering, and showing one complete real WHOIS query.

Suggestions

Remove the empty 'IP2WHOIS Overview' section and the explanatory prose about who uses IP2WHOIS; assume Claude knows this context.

Fix the workflow numbering: replace the dangling '#### 1b' header and 'skip to Step 2' references with a consistent numbered sequence.

Add one concrete end-to-end example showing a real WHOIS action discovery and run with actual parameters, not just placeholders.

Dimension	Reasoning	Score
Conciseness	The body is mostly concrete commands, but padded prose (e.g. explaining who uses IP2WHOIS, 'focus on the integration logic rather than auth plumbing') and a near-empty 'IP2WHOIS Overview' section ('IP Address / WHOIS Record', 'Use action names and parameters as needed') add unnecessary tokens.	3 / 5
Actionability	Provides many concrete, executable commands with flags (login, connection ensure --wait, action list/run, request with full flag table), but examples rely on placeholders like CONNECTION_ID and lack a concrete end-to-end WHOIS query with real parameters.	4 / 5
Workflow Clarity	Clear install → authenticate → connect → poll-for-ready → search → run/proxy sequence with validation via the --wait poll loop and state handling (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), though the orphaned '1b' header and references to a non-existent 'Step 2' introduce minor incoherence.	4 / 5
Progressive Disclosure	Single self-contained SKILL.md with well-organized sections (Install, Authentication, Connecting, Searching, Popular actions, Proxy, Best practices) and no bundle files; structure is clear though some inline reference material could be split out.	4 / 5
	Total	15 / 20 Passed

Description

66%Weight 40%Scale 1-5

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 structurally sound — it states both what the skill does and when to use it, anchored to a distinct named product. Its main weakness is generic action language and missing natural WHOIS/IP trigger synonyms.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete IP2WHOIS operations such as 'look up WHOIS records for IP addresses and domains'.

Add natural trigger terms users would say, e.g. 'WHOIS lookup', 'domain WHOIS', or 'IP ownership information'.

Dimension	Reasoning	Score
Specificity	Names the domain (IP2WHOIS) and lists several actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete WHOIS/IP operations, so it sits above the minimal-anchor but below comprehensive.	3 / 5
Completeness	Both a 'what' (IP2WHOIS integration managing data/records/workflows) and an explicit 'when' ('Use when the user wants to interact with IP2WHOIS data') are present, though the 'what' is generic and the trigger is narrow.	4 / 5
Trigger Term Quality	Includes the product name 'IP2WHOIS' and terms like 'data' and 'records', but misses the natural phrases a user would actually say such as 'WHOIS lookup', 'domain WHOIS', or 'IP information'.	3 / 5
Distinctiveness Conflict Risk	The named-product trigger 'IP2WHOIS' carves out a clear niche with a distinct 'when' clause, giving minimal overlap risk with other skills.	5 / 5
	Total	15 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/ip2whois/SKILL.md
Commit: f484c82

Reviewed: 5 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.