Name: soax
Rating: 60 (1 reviews)
Author: membranedev

soax

Soax integration. Manage Persons, Organizations, Deals, Leads, Projects, Activities and more. Use when the user wants to interact with Soax data.

Quality

70%

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

Quality

Content

75%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 Membrane CLI integration guide with concrete commands and a clear connection state machine. It is slightly verbose in places and self-referential in its 'Step 2' wording, and it would benefit from splitting the denser reference material into separate files.

Suggestions

Remove the redundant 'Popular actions' section or merge it into 'Searching for actions' to avoid repeating the action-list command.

Fix the dangling 'Step 2' references by either labeling the 'Searching for actions' section as Step 2 or rewording to 'proceed to Searching for actions'.

Move the connection-state reference (READY/BUILDING/CLIENT_ACTION_REQUIRED) and the proxy-request flag table into dedicated reference files to keep SKILL.md a concise overview.

Dimension	Reasoning	Score
Conciseness	The guide is mostly efficient with concrete commands, but includes some unnecessary explanation (the 'Popular actions' section repeats the action-list command already shown, and prose like 'Those will be used to adjust tooling to be used best with your harness' is padded) that could be trimmed.	3 / 5
Actionability	It provides fully executable, copy-paste-ready Membrane CLI commands for every key operation (login, connection ensure/get with --wait, action list/run, request) including a flag table for proxy requests covering the common cases.	5 / 5
Workflow Clarity	The connection flow is clearly sequenced with state-based checkpoints and a poll-after-user-action feedback loop, but references to 'Step 2' are dangling (no section is actually labeled Step 2), leaving a minor navigation gap.	4 / 5
Progressive Disclosure	Content is well-organized into clear sections with no nested references, but at ~115 lines it is somewhat monolithic; the connection-state reference and proxy-request table could live in separate files to keep SKILL.md a lean overview.	4 / 5
	Total	16 / 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 answers both what and when and is anchored by a distinctive proper noun, but its action verb is generic and its trigger phrasing lacks natural variations. It also lists CRM-style entities (Persons, Deals, Leads) that do not match the proxy-service content in the body, signaling a possible copy-paste mismatch.

Suggestions

Replace the generic verb 'Manage' with concrete Soax-specific actions (e.g., 'Configure residential/mobile proxies, list countries, retrieve proxy credentials, manage orders').

Tighten the 'when' clause with concrete trigger phrases users would say, e.g. 'Use when the user needs proxy rotation, IP masking, or country-targeted web scraping via Soax.'

Align the entity list with the skill's actual proxy-service scope to avoid misleading the model about supported capabilities.

Dimension	Reasoning	Score
Specificity	Names the domain ('Soax integration') and lists several concrete entities ('Persons, Organizations, Deals, Leads, Projects, Activities'), but the only action verb is the generic 'Manage' and 'and more' pads without adding specifics.	3 / 5
Completeness	Both 'what' (Manage Persons, Organizations, Deals, Leads, Projects, Activities) and 'when' ('Use when the user wants to interact with Soax data') are present and explicit, though the 'when' clause could be more specific about concrete trigger scenarios.	4 / 5
Trigger Term Quality	'Soax' and 'Soax data' are relevant trigger keywords, but the phrasing 'interact with Soax data' is generic and lacks natural synonyms or variations a user would actually say.	3 / 5
Distinctiveness Conflict Risk	The proper noun 'Soax' anchors a clear, distinct niche with minimal conflict risk against other skills, despite the generic CRM-style entity list.	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/soax/SKILL.md
Commit: f484c82

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