Name: oxylabs
Rating: 56.00000000000001 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

oxylabs

Oxylabs integration. Manage Organizations. Use when the user wants to interact with Oxylabs data.

Quality

64%

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/oxylabs/SKILL.md

Quality

Content

66%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, actionable guide with executable CLI commands and a clearly sequenced connection workflow including state-based checkpoints. It is slightly over-explanatory in places and lacks a validation checkpoint before executing actions against live external services.

Suggestions

Trim over-explanation of concepts Claude already knows (e.g., what Membrane auth does) and de-duplicate the action-list command, which is shown twice.

Add an explicit validation/verification checkpoint before running actions against live Oxylabs data, such as confirming the connection is READY before executing action run.

Consider splitting the detailed clientAction state machine and proxy flags table into a separate reference file to keep SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with command tables and code blocks, but it explains basics Claude knows ('Membrane handles authentication and credentials refresh automatically') and restates the same action-list command twice, so it could be tightened.	3 / 5
Actionability	Concrete, executable commands appear throughout (install, login, connection ensure, action list/run, request flags table) with copy-paste-ready examples, with only minor gaps such as placeholder substitution guidance.	4 / 5
Workflow Clarity	The connection setup is clearly sequenced with state checks (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and explicit polling loops, though there is no validation step before running actions against live external data.	4 / 5
Progressive Disclosure	The skill has no bundle files and uses well-organized sections (Overview, Working with Oxylabs, Popular actions, Best practices) as an overview; there are no nested references, which is appropriate for a single-file skill, with only minor structural looseness.	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 clearly names the domain and includes an explicit 'Use when...' trigger, but its capability list is thin ('Manage Organizations' alone) and trigger phrasing is generic. It is functional and distinct but not comprehensive.

Suggestions

Add more concrete capabilities to the description (e.g., scraping websites, running scrape jobs, viewing usage statistics) so users know the full scope.

Enrich the trigger clause with natural keywords users would say, such as 'scraping', 'proxy requests', or 'web data collection', not just 'interact with Oxylabs data'.

Make the 'when' clause more specific by tying it to concrete scenarios rather than a generic data-interaction phrase.

Dimension	Reasoning	Score
Specificity	Names the Oxylabs domain and the concrete action 'Manage Organizations' but lists only a single capability and is otherwise minimal, matching the 'names domain and 1-2 concrete actions but not comprehensive' anchor.	3 / 5
Completeness	A clear 'what' ('Oxylabs integration. Manage Organizations.') and an explicit 'when' ('Use when the user wants to interact with Oxylabs data.') are both present, though the 'when' is generic rather than tied to concrete trigger phrases.	4 / 5
Trigger Term Quality	The phrase 'interact with Oxylabs data' provides a relevant natural term but lacks synonyms or variations like 'scraping', 'proxy', or specific endpoints, fitting the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The Oxylabs brand name gives it a clear niche and distinct triggers with minor overlap risk against other data-collection skills.	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/oxylabs/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.