Name: wallarm
Rating: 52.8 (1 reviews)
Author: membranedev

wallarm

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

Quality

59%

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

Quality

Content

61%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 concrete, executable Membrane CLI commands and a sensible end-to-end workflow, but it is held back by marketing padding, a broken step reference, and missing validation for the proxy/destructive path.

Suggestions

Fix the broken navigation: replace "skip to Step 2" with the actual target heading and reconcile the lone "1b" subsection with a matching "1a".

Trim marketing language ("focus on the integration logic rather than auth plumbing", "fastest way to get a connection") to improve token efficiency.

Add a validation/check step before destructive proxy requests (POST/PUT/DELETE) and a verify step after running actions, to strengthen the feedback loop.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but includes marketing fluff ("so you can focus on the integration logic rather than auth plumbing", "This is the fastest way to get a connection", "This will burn less tokens") and an explanatory opening paragraph about what Wallarm is, matching the score-3 anchor of mostly efficient with some unnecessary explanation.	3 / 5
Actionability	It provides copy-paste-ready commands throughout (install, login, connection ensure, action list/run, request) plus a full proxy-options table, matching the score-4 anchor of mostly executable guidance with minor gaps; placeholders like <actionId> and CONNECTION_ID are standard but keep it just short of fully complete.	4 / 5
Workflow Clarity	The install→authenticate→connect→poll→search→run sequence is clear with an explicit polling feedback loop for connection readiness, but the "skip to Step 2" reference points to a non-existent step and the "1b" heading has no "1a", and the proxy/destructive-request path lacks validation, fitting the score-3 anchor of steps present with validation gaps.	3 / 5
Progressive Disclosure	The content is organized into well-labeled single-level sections (Overview, Working with Wallarm, Install, Authentication, Connecting, Searching, Popular actions, Proxy, Best practices) with no nested references and no bundle files needed, matching the score-4 anchor of good structure with minor organization gaps such as the thin Popular actions list.	4 / 5
	Total	14 / 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 successfully pairs a what and when and leverages the distinct "Wallarm" product name, but its capability language is generic rather than concrete and it offers only a single trigger keyword.

Suggestions

Replace the generic actions ("Manage data, records, and automate workflows") with concrete Wallarm capabilities such as events, block pages, IP lists, rules, and users.

Expand the trigger clause with natural variations, e.g. "Use when the user wants to query Wallarm events, manage IP lists or rules, or work with Wallarm security data."

Tighten the "when" to specific Wallarm use cases rather than the broad "interact with Wallarm data".

Dimension	Reasoning	Score
Specificity	It names the domain ("Wallarm integration") but the actions "Manage data, records, and automate workflows" are generic verbs rather than concrete Wallarm capabilities, matching the score-2 anchor where the domain is named but actions are minimal or generic.	2 / 5
Completeness	Both a "what" ("Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with Wallarm data") are present, matching the score-4 anchor; the "when" is explicit but could be more specific, and the "what" is somewhat generic so it does not reach 5.	4 / 5
Trigger Term Quality	The trigger relies on the single keyword "Wallarm" ("Use when the user wants to interact with Wallarm data"); it is the natural term a user would say, but there are no variations or synonyms, fitting the score-3 anchor of some relevant keywords missing common variations.	3 / 5
Distinctiveness Conflict Risk	Naming the specific product "Wallarm" gives it a clear, distinct niche with minimal conflict risk, but the generic data-management phrasing leaves minor overlap risk with other data-integration skills, matching the score-4 anchor rather than a clear 5.	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/wallarm/SKILL.md
Commit: f484c82

Reviewed: 3 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.