Name: ipdataco
Rating: 56.8 (1 reviews)
Author: membranedev

ipdataco

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

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/ipdataco/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 body is a well-structured, actionable guide with concrete Membrane CLI commands and a clear connection-to-execution workflow. Its main weaknesses are minor verbosity in the framing prose and a lack of explicit validation checkpoints, which keep conciseness and workflow clarity just below the top anchors.

Suggestions

Trim marketing/framing prose such as the 'Developers and businesses use it...' sentence and the 'so you can focus on the integration logic rather than auth plumbing' aside.

Add an explicit validation step after running actions, e.g. check the `output`/`error` fields and surface non-2xx results before continuing.

Clarify how to resolve the CONNECTION_ID and actionId placeholders (e.g. capture the id from `connection ensure --json`) so the commands are end-to-end runnable.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but includes some unnecessary filler such as 'Developers and businesses use it to personalize content...' and 'Membrane handles authentication and credentials refresh automatically — so you can focus on the integration logic rather than auth plumbing' that Claude does not need; it could be tightened, matching 'Mostly efficient but includes some unnecessary explanation'.	3 / 5
Actionability	It provides concrete, copy-pasteable commands (membrane connection ensure, action list/run, request flags table) covering the common cases with minor gaps such as placeholder CONNECTION_ID and unspecified actionIds, placing it at 'Mostly executable guidance' rather than fully comprehensive.	4 / 5
Workflow Clarity	There is a clear sequence (install, login, ensure connection, wait for READY, search actions, run) with state-based decision branches and a poll-until-ready feedback loop; it lacks explicit validation for the destructive/batch threshold but the checkpoints present justify 4, just below the explicit-checklist anchor of 5.	4 / 5
Progressive Disclosure	Content is well organized into clear sections (Overview, Working with Ipdata.co, Popular actions, Best practices) with no bundle files needed and no nested references; it is a single self-contained file with good structure, sitting at 'Good structure' rather than the one-level-deep multi-reference anchor of 5.	4 / 5
	Total	15 / 20 Passed

Description

62%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 correctly pairs a 'what' with an explicit 'Use when' trigger and is tied to a specific product, which keeps conflict risk low. It is weakest in specificity and trigger-term coverage, relying on generic verbs ('Manage data, records') rather than concrete Ipdata.co actions and natural IP-lookup phrases.

Suggestions

Replace generic verbs with concrete Ipdata.co actions, e.g. 'Look up IP geolocation, ASN/carrier, and threat data, and run Ipdata.co actions.'

Add natural trigger phrases users say, such as 'IP lookup', 'IP location', 'IP geolocation', or 'IP address info'.

Sharpen the 'Use when' clause to name scenarios like 'Use when the user wants to look up, enrich, or check the location/security of an IP address via Ipdata.co.'

Dimension	Reasoning	Score
Specificity	The description names the domain (Ipdata.co) and a couple of generic actions ('Manage data, records, and automate workflows') but offers no concrete capabilities like 'look up IP location', 'fetch ASN/carrier data', or 'query threat information'; per the anchor, domain plus 1-2 minimal actions sits at 3, not 4 because actions are generic rather than specific.	3 / 5
Completeness	It states what the skill does ('Ipdata.co integration. Manage data, records, and automate workflows') and gives an explicit 'Use when the user wants to interact with Ipdata.co data' clause, so both what and when are present, though the 'when' could be more specific about trigger scenarios.	4 / 5
Trigger Term Quality	It includes some relevant terms ('IP', 'Ipdata.co', 'interact with ... data') but misses the natural phrases users would say such as 'IP geolocation', 'IP lookup', 'IP location', or 'IP address' as triggers; coverage is partial, matching 'Some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	Tying the trigger explicitly to 'Ipdata.co data' makes it fairly niche and distinct from other skills, with only minor overlap risk against a generic data-management skill; it is not a fully comprehensive niche trigger set, so it stays at 4 rather than 5.	4 / 5
	Total	14 / 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/ipdataco/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.