CtrlK
BlogDocsLog inGet started
Tessl Logo

ipbase

Ipbase integration. Manage data, records, and automate workflows. Use when the user wants to interact with Ipbase 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/ipbase/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 content is highly actionable with concrete, executable CLI commands and a clear connection workflow with state-based checkpoints. It is mostly concise and well-structured, with only minor verbosity and one small workflow-numbering inconsistency.

Suggestions

Fix the step numbering: the 'If READY skip to Step 2' reference has no labeled Step 2, and '1b' appears without a '1a' — relabel the Connecting section as explicit numbered steps.

Trim editorial padding like 'so you can focus on the integration logic rather than auth plumbing' to keep every token earning its place.

Consider moving the proxy flag table and clientAction field reference into a separate REFERENCE.md to keep the overview lean.

DimensionReasoningScore

Conciseness

The body is mostly lean and assumes Claude's competence; explanations target Membrane-specific behavior (clientAction states, --wait semantics) that Claude would not already know, with only minor padding such as 'so you can focus on the integration logic rather than auth plumbing'.

4 / 5

Actionability

Fully executable, copy-paste-ready commands throughout — install, login, connection ensure, action list/run, proxy requests — each with concrete flags and JSON input examples covering the common cases.

5 / 5

Workflow Clarity

Clear sequenced workflow (install → auth → connect → poll until READY → search actions → run) with state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a re-poll feedback loop, but step numbering is inconsistent ('1b' with no '1a'/'Step 2' label) creating minor gaps.

4 / 5

Progressive Disclosure

Well-organized single-file structure with clear section headers and no nested references; at ~140 lines some of the proxy-options table and clientAction detail could be split into a reference file, but no bundle files exist and navigation is easy.

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 answers both what the skill does and when to use it, anchored to a distinctive product name. Its main weakness is generic, non-concrete action language and a thin set of natural trigger terms.

Suggestions

Replace 'Manage data, records, and automate workflows' with concrete Ipbase actions, e.g. 'Geolocate IP addresses, look up ASN details, and run bulk IP/ASN lookups'.

Add natural trigger phrases users would say: 'Use when the user wants to geolocate an IP address, look up ISP/ASN info, or batch-lookup multiple IPs.'

Mention file extensions or API-specific terms (e.g. IPv4/IPv6, ASN) to broaden trigger coverage.

DimensionReasoningScore

Specificity

Names the Ipbase domain but the actions are minimal and generic — 'Manage data, records, and automate workflows' describes no concrete Ipbase-specific operation (e.g. geolocate an IP, look up an ASN, bulk lookup).

2 / 5

Completeness

Both 'what' ('Ipbase integration. Manage data, records, and automate workflows') and 'when' ('Use when the user wants to interact with Ipbase data') are present and explicit, though the 'when' clause is fairly generic.

4 / 5

Trigger Term Quality

Contains the relevant keyword 'Ipbase' and 'Ipbase data' but misses the natural phrases a user would actually say ('IP geolocation', 'IP location', 'lookup IP address', 'ASN'), so common variations are absent.

3 / 5

Distinctiveness Conflict Risk

The 'Ipbase' name gives it a clear niche with minimal conflict risk, but the generic 'manage data, records, and automate workflows' phrasing could overlap with other data-integration 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.