CtrlK
BlogDocsLog inGet started
Tessl Logo

ipinfoio

IPinfo.io integration. Manage Domains, ASNs, Companies. Use when the user wants to interact with IPinfo.io data.

60

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/ipinfoio/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 highly actionable, well-sequenced integration guide with executable commands and an explicit connection-readiness feedback loop, suffering only minor verbosity and an unlabeled 'Step 2' reference.

DimensionReasoningScore

Conciseness

The body is dominated by concrete, copy-pasteable commands with only minor over-explanation such as 'Developers and businesses use it to enrich IP addresses...' and 'so you can focus on the integration logic rather than auth plumbing', fitting 'Efficient; minor instances of over-explanation that could be trimmed' rather than the more padded 3 or the fully lean 5.

4 / 5

Actionability

It provides fully executable commands throughout (npm install, membrane login, connection ensure/get with --wait, action list/run, request) with real flags and JSON-output examples, matching 'Fully executable; copy-paste ready code or commands; specific examples cover the common cases.'

5 / 5

Workflow Clarity

The install→auth→connect→poll→search→run sequence is clear and includes an explicit readiness state machine with a feedback loop (CLIENT_ACTION_REQUIRED → user acts → poll again), but 'skip to Step 2' references a Step 2 that is never labeled, leaving a minor navigation gap, matching 'Clear sequence with most checkpoints present; minor validation gaps.'

4 / 5

Progressive Disclosure

As a single-file skill with no bundle files, it is well-organized into clearly headed sections (Overview, Working with IPinfo.io, Popular actions, Proxy requests, Best practices); the inlined popular-actions and proxy-flag tables are reasonable reference content kept inline, matching 'Good structure; most content is appropriately placed; minor organization gaps.'

4 / 5

Total

17

/

20

Passed

Description

57%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 names a distinct vendor niche, but its action verb is generic and its trigger vocabulary is narrow.

Suggestions

Replace the generic verb 'Manage' with concrete actions, e.g. 'Look up IP geolocation, ASN, company, carrier, and privacy data for IP addresses and domains.'

Add natural trigger terms users would actually say, such as 'IP address lookup', 'geolocation', 'IP enrichment', and 'whois/ASN details'.

Make the 'Use when' clause more specific by listing concrete scenarios, e.g. 'Use when the user wants to enrich an IP address with location, ASN, company, carrier, or privacy data via IPinfo.io.'

DimensionReasoningScore

Specificity

The phrase 'Manage Domains, ASNs, Companies' names the domain (IPinfo.io) and several data objects, but 'Manage' is a single generic action verb rather than concrete operations like 'look up', 'enrich', or 'detect'. This fits the anchor 'Names the domain but actions are minimal or generic' better than 3, which requires 1-2 concrete named actions.

2 / 5

Completeness

Both 'what' ('IPinfo.io integration. Manage Domains, ASNs, Companies.') and 'when' ('Use when the user wants to interact with IPinfo.io data.') are present and explicit, but the 'when' clause is generic and could be more specific, matching the anchor 'Has both what and when; when could be more explicit or specific.'

4 / 5

Trigger Term Quality

It includes the product name 'IPinfo.io' and data-type terms 'Domains, ASNs, Companies', but misses common natural variations users would say such as 'IP address', 'IP lookup', 'geolocation', or 'IP enrichment', matching 'Some relevant keywords but missing common variations or synonyms.'

3 / 5

Distinctiveness Conflict Risk

Tying the skill to the specific vendor product 'IPinfo.io' with named data categories gives it a clear niche with minimal conflict risk, though 'interact with IPinfo.io data' is broad enough to allow minor overlap with other IP-data skills, matching 'Mostly distinct; minor overlap risk with closely related skills.'

4 / 5

Total

13

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
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.