Name: proxyclick
Rating: 58.4 (1 reviews)
Author: membranedev

proxyclick

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

Quality

68%

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/proxyclick/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 highly actionable, with executable CLI commands and a well-sequenced connection workflow that includes state checkpoints and retry loops. Its main weaknesses are mild verbosity (an introductory concept sentence and an unexplained entity list) and minor section redundancy rather than structural problems.

Suggestions

Trim or remove the opening "Proxyclick is a cloud-based visitor management system..." sentence and the bare entity bullet list, or move them to a reference file, since Claude does not need this background.

Merge the redundant "Searching for actions" and "Popular actions" sections into a single action-discovery section to remove the repeated `membrane action list` command.

Consider extracting the entity catalog and proxy-request flag reference into a separate reference file so SKILL.md stays a lean overview.

Dimension	Reasoning	Score
Conciseness	The CLI command blocks are lean and earn their tokens, but the opening sentence explaining what Proxyclick is and the bulleted entity vocabulary dump (Visit, Visitor, Integration, Dashboard, etc.) add content Claude largely does not need, fitting the mostly-efficient-with-some-unnecessary-explanation anchor.	3 / 5
Actionability	The body provides fully executable, copy-paste-ready commands for every common case — install, login, connection ensure/get, action list/run, and request — plus a concrete flags table for proxy requests, matching the fully-executable anchor.	5 / 5
Workflow Clarity	The connection flow is clearly sequenced with state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll-retry feedback loop, but the "Popular actions" section redundantly repeats the action-list command already shown in "Searching for actions", leaving a minor organization gap.	4 / 5
Progressive Disclosure	Content is organized into clear, well-labeled sections with no nested references, but the skill is a single monolithic file over 50 lines with no external reference files for the entity catalog or proxy details, so it stops short of the clean overview-plus-references ideal.	4 / 5
	Total	16 / 20 Passed

Description

61%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 distinct and includes an explicit use-trigger, but its capability statement is generic ("manage data, records, automate workflows") and lacks concrete Proxyclick-specific actions or natural keyword variations. Strengthening the action list with specific operations would raise specificity and trigger quality.

Suggestions

Replace generic verbs with concrete Proxyclick operations, e.g. "Check in visitors, manage watchlists, view visit logs, and retrieve location/device data".

Add natural user-facing trigger phrases beyond the product name, such as "visitor check-in", "visit management", or "Proxyclick visitor logs".

Tighten the "what" so it lists 2-4 specific capabilities instead of "manage data, records, and automate workflows".

Dimension	Reasoning	Score
Specificity	The description names the Proxyclick domain but its actions — "Manage data, records, and automate workflows" — are generic rather than concrete, Proxyclick-specific operations, matching the anchor for minimal/generic actions rather than the 1-2 concrete actions of a 3.	2 / 5
Completeness	Both a "what" ("Manage data, records, and automate workflows") and an explicit "Use when the user wants to interact with Proxyclick data" trigger are present, but the "what" is generic and could be more specific, fitting the 4 anchor rather than the fully concrete 5.	4 / 5
Trigger Term Quality	The only natural keyword is "Proxyclick" (repeated in "interact with Proxyclick data"); there are no synonyms, use-case phrases, or variations a user might naturally say, so coverage is partial rather than comprehensive.	3 / 5
Distinctiveness Conflict Risk	"Proxyclick integration" names a specific product with a clear niche, so it is highly distinguishable from other skills and unlikely to trigger for the wrong one.	5 / 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/proxyclick/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.