CtrlK
BlogDocsLog inGet started
Tessl Logo

proxy-spider

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

52

Quality

58%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/proxy-spider/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 actionable and well-structured with executable Membrane CLI commands and a sensible connection-readiness workflow including validation feedback loops. Main weaknesses are light marketing padding and a dangling "Step 2" reference that breaks the step numbering.

Suggestions

Remove marketing-style padding (e.g., "so you can focus on the integration logic rather than auth plumbing", "This will burn less tokens") to tighten token efficiency.

Fix the step numbering: the body references "Step 2" and "1b" but no Step 1a/Step 2 labels exist — either label the sections or drop the cross-references.

Add at least one concrete `membrane action run` example with a real actionId and --input payload so the actionability reaches copy-paste completeness.

DimensionReasoningScore

Conciseness

The body is mostly commands and brief prose, but padded lines like "so you can focus on the integration logic rather than auth plumbing" and "This will burn less tokens and make communication more secure" add marketing fluff that could be trimmed.

3 / 5

Actionability

Concrete copy-paste commands ("npm install -g @membranehq/cli@latest", "membrane connection ensure", "membrane action run ... --input") cover the common cases, with only minor gaps since no example action run uses real parameter values.

4 / 5

Workflow Clarity

There is a clear install→authenticate→connect→search→run sequence with polling and feedback loops for connection states (BUILDING, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR), but references to a "Step 2" that is never labeled are a minor sequencing gap.

4 / 5

Progressive Disclosure

The single SKILL.md is well-organized into Overview, Working with Proxy Spider, and Best practices sections with no bundle files to reference; content is appropriately inline, with only minor organization gaps in the longer clientAction detail block.

4 / 5

Total

15

/

20

Passed

Description

48%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 is third-person and includes an explicit Use-when trigger plus a named product, but its capability statement is minimal and somewhat misleading relative to the body. Trigger-term coverage is narrow, relying on the product name alone.

Suggestions

Replace the generic "Manage Organizations" with the concrete capabilities the skill supports (e.g., manage and rotate proxy servers, run scrapes, inspect proxy requests).

Expand the trigger phrase to include natural terms users would say, such as "proxies", "proxy servers", "web scraping", or "data collection".

Tighten the Use-when clause to reference the specific Proxy Spider resources (Proxies, Requests, Scrapes) listed in the body.

DimensionReasoningScore

Specificity

Quotes "Proxy Spider integration. Manage Organizations." name the domain but the single action is generic and minimal, and it does not reflect the proxy-rotation/scraping capabilities the body describes.

2 / 5

Completeness

It supplies both a "what" ("Proxy Spider integration. Manage Organizations.") and an explicit "when" trigger, but the "what" is vague/generic rather than clearly describing the skill's actual capabilities, placing it below the anchor 4 example.

3 / 5

Trigger Term Quality

Quotes "Use when the user wants to interact with Proxy Spider data" include the product name as a keyword but miss natural variations users would say such as "proxies", "proxy servers", "web scraping", or "data collection".

3 / 5

Distinctiveness Conflict Risk

Quotes "Proxy Spider integration" name a specific product giving a clear niche with minimal conflict risk, though the generic "Manage Organizations" leaves minor overlap with other management skills.

4 / 5

Total

12

/

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.