Name: smartproxy
Rating: 64 (1 reviews)
Author: membranedev

smartproxy

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

Quality

76%

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

Quality

Content

76%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 highly actionable with executable commands and a reasonable section structure, and is largely token-efficient. Its weakness is workflow clarity: the connection and action workflows lack explicit validation/feedback checkpoints for error recovery on potentially risky operations.

Suggestions

Add explicit validation/feedback checkpoints after risky steps — e.g. after `action run` or proxy `request`, show how to inspect the `output`/`error` field, detect failure, and retry, to lift workflow clarity above the validation cap.

Trim inferable padding such as the opening paragraph on what Smartproxy is used for and phrases like "This is the fastest way to get a connection", keeping only what Claude would not already know.

Either move the request-flag reference table and polling-state detail into a one-level-deep reference file (e.g. REFERENCES.md) or explicitly justify keeping them inline, to tighten the overview-to-detail split.

Dimension	Reasoning	Score
Conciseness	The body is largely efficient with copy-paste commands and tight tables, but a few phrases over-explain what Claude can infer (e.g. "This is the fastest way to get a connection", "It's used by businesses and individuals for..."), fitting the "efficient; minor instances of over-explanation" anchor.	4 / 5
Actionability	Commands are complete and copy-paste ready (e.g. `membrane connection ensure`, `membrane action run <actionId> --input '{...}' --json`) with specific flag tables covering common cases, matching the fully executable anchor.	5 / 5
Workflow Clarity	There is a clear connection-readiness sequence (ensure -> poll -> READY/CLIENT_ACTION_REQUIRED/ERROR), but no explicit validate-then-act feedback loop for risky operations; per the destructive/batch guidance, a workflow lacking validation checkpoints is capped at 3.	3 / 5
Progressive Disclosure	Section headers (Overview, Authentication, Connecting, Popular actions, Proxy requests, Best practices) give good single-file structure with no nested references; without bundle files it cannot reach the 5 anchor's well-signaled one-level-deep reference pattern, but the organization is otherwise good.	4 / 5
	Total	16 / 20 Passed

Description

76%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 the skill does and when to use it with an explicit trigger clause, and is anchored to a specific named service. Its main weakness is trigger term breadth — it relies almost entirely on the "Smartproxy" name without natural synonyms or variations a user might say.

Suggestions

Add natural-language synonyms and user phrasings to the trigger (e.g. "rotating residential proxies", "datacenter IPs", "web scraping proxies") so the skill surfaces for varied user requests.

Replace the generic "Manage data, records, and automate workflows" with Smartproxy-specific actions (e.g. "manage proxy users, subusers, traffic, and subscriptions") to sharpen specificity and distinctiveness.

Keep the explicit "Use when..." clause but broaden it to mention concrete proxy use cases (scraping, ad verification, geo-bypass) to widen trigger coverage without inflating length.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names several concrete capability areas with only minor gaps, fitting the "several specific actions" anchor rather than the minimal (2) or fully comprehensive (5) anchors.	4 / 5
Completeness	It clearly states what it does ("Manage data, records, and automate workflows") and explicitly when to use it ("Use when the user wants to interact with Smartproxy data"), matching the top anchor that answers both what and when.	5 / 5
Trigger Term Quality	The term "Smartproxy" is present and relevant, but there are no natural synonyms, variations, or file extensions that a user would actually say; it sits at the "some relevant keywords but missing common variations" anchor.	3 / 5
Distinctiveness Conflict Risk	Tying the skill to the named Smartproxy niche gives it a distinct trigger with only minor overlap risk against other data-management skills, fitting the "mostly distinct" anchor rather than the clear-niche (5) anchor because "data, records" phrasing is still somewhat broad.	4 / 5
	Total	16 / 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/smartproxy/SKILL.md
Commit: f484c82

Reviewed: ~22 hours 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.