Name: haproxy
Rating: 50.4 (1 reviews)
Author: membranedev

haproxy

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

Quality

55%

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

Quality

Content

57%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 delivers largely executable membrane CLI commands and a reasonable connection workflow, but it opens with concept explanations Claude already knows, has inconsistent step numbering ('1b', a referenced 'Step 2' with no Step 1/2 labels), and lacks validation checkpoints for direct proxy requests. With no bundle files, progressive disclosure relies entirely on inline sectioning that could be tighter.

Suggestions

Remove the opening 'HAProxy is a popular open-source load balancer...' paragraph and the generic Overview bullet list; assume Claude knows what HAProxy is.

Fix the step numbering — replace the orphan '1b' and the undefined 'Step 2' references with a coherent numbered sequence (1, 2, 3...).

Add an explicit validation/verification step before running actions or proxy requests (e.g. check connection state is READY, verify action inputSchema before run), and consider moving the proxy options table and action discovery detail into a separate reference file.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands, but includes unnecessary explanation Claude already knows (e.g. 'HAProxy is a popular open-source load balancer... It's used by developers and system administrators to improve the performance and reliability of web applications') and an 'Overview' list of generic terms.	3 / 5
Actionability	Provides concrete, executable membrane CLI commands throughout (connection ensure, action list/run, request) with a clear options table, with only minor gaps such as the abrupt 'Step 2' reference that lacks a labeled preceding step.	4 / 5
Workflow Clarity	The connection workflow has a clear poll-until-ready loop with state handling, but numbering is inconsistent (no 'Step 2' heading, jumps to '1b'), and there are no explicit validation checkpoints for the destructive proxy/request operations, capping the score at 3.	3 / 5
Progressive Disclosure	Content is organized into sections with a quick-start flow, but no bundle/reference files exist so all detail lives inline in SKILL.md, and the proxy options table and action discovery content could be separated for clearer navigation.	3 / 5
	Total	13 / 20 Passed

Description

53%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 names a clear niche (HAProxy) and includes an explicit 'Use when' clause, but the action list is generic ('Manage data, records, automate workflows') rather than HAProxy-specific, weakening specificity and trigger terms. It is distinct enough to avoid most conflicts but lacks the concrete, load-balancer-focused phrasing the good examples demonstrate.

Suggestions

Replace generic verbs with HAProxy-specific actions, e.g. 'Manage HAProxy backends, frontends, and servers; inspect and update load-balancer configuration.'

Expand the 'Use when' trigger to reference natural user phrasing such as load balancing, traffic distribution, backend/frontend/server management, or HAProxy config inspection.

Drop the vague 'Manage data, records' phrasing, which adds no HAProxy-specific information and inflates the description.

Dimension	Reasoning	Score
Specificity	Names the domain and one concrete action ('automate workflows') but otherwise relies on generic verbs ('Manage data, records') that are not comprehensive or HAProxy-specific.	3 / 5
Completeness	Has a clear 'what' (HAProxy integration) but the 'when' clause ('Use when the user wants to interact with HAProxy data') is generic and only weakly specifies the trigger, capping completeness at 3 per the missing-explicit-trigger guideline.	3 / 5
Trigger Term Quality	Includes the natural term 'HAProxy' but lacks common variations, synonyms, or the specific concepts (load balancing, backends, frontends) users actually say when they need this skill.	3 / 5
Distinctiveness Conflict Risk	The HAProxy niche is fairly distinct and unlikely to trigger for unrelated skills, though the generic 'Manage data, records, and automate workflows' phrasing creates minor overlap risk with other integration 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/haproxy/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.