Name: proliant
Rating: 55.2 (1 reviews)
Author: membranedev

proliant

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

Quality

63%

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

Quality

Content

68%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 highly actionable with executable CLI commands and a solid connection-state workflow, but it carries some unnecessary explanatory prose and lacks validation guidance for destructive proxy operations.

Suggestions

Trim Membrane-internal explanations (e.g., how connectors are auto-built, the auth-plumbing commentary) to keep only what Claude needs to operate the CLI.

Add a validation/verification checkpoint before destructive proxy calls (e.g., confirm the method and target, dry-run GET before DELETE/PUT) so the workflow clears the destructive-operation bar.

Correct the opening line claiming Proliant is a server-hardware platform, which contradicts the legal/records entities listed in the overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient command examples, but includes unnecessary prose such as "so you can focus on the integration logic rather than auth plumbing" and explanations of Membrane's internal connector-building that Claude does not need.	3 / 5
Actionability	It provides copy-paste-ready commands for every stage (install, login, connection ensure/get, action list/run, request) plus a concrete proxy flag table, fully covering the common cases.	5 / 5
Workflow Clarity	The connection flow has a clear sequence with state-checking and polling feedback loops, but the proxy section enables destructive methods (DELETE/PUT) with no validation or verification checkpoint, capping this dimension at 3.	3 / 5
Progressive Disclosure	No bundle files exist and the SKILL.md is organized into clear sections (Overview, Auth, Connecting, Actions, Proxy, Best practices); structure is good though the proxy-flag detail could arguably live in a reference file.	4 / 5
	Total	15 / 20 Passed

Description

57%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 correctly pairs a what with an explicit "Use when" trigger and is anchored to a distinct product name, but its capability phrasing is generic rather than concrete and it offers only one narrow trigger keyword.

Suggestions

Replace generic verbs with concrete Proliant capabilities (e.g., "manage cases, contacts, matters, time and expense entries, and invoices") so the what is specific.

Broaden the trigger beyond "interact with Proliant data" to the natural phrases users say, such as "Proliant records," "Proliant payroll/HR data," or "Proliant reports."

Tighten the when clause to the actual use cases (e.g., querying employees, pulling payroll reports, syncing time entries) to reduce overlap with generic data skills.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Proliant domain but the actions are generic (manage data/records, automate workflows) rather than concrete capabilities, matching the anchor for minimal/generic actions.	2 / 5
Completeness	It states both a what ("Manage data, records, and automate workflows") and an explicit when ("Use when the user wants to interact with Proliant data"), though the what is generic and the when could be more specific.	4 / 5
Trigger Term Quality	The trigger relies on the single proper-noun keyword "Proliant" in "interact with Proliant data"; it has the relevant term but lacks natural variations or synonyms users might say.	3 / 5
Distinctiveness Conflict Risk	Tying triggers to the named product "Proliant" gives it a clear niche with minimal conflict risk, though the generic data/records phrasing leaves minor overlap with other data-management skills.	4 / 5
	Total	13 / 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/proliant/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.