Name: nginx
Rating: 49.6 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

nginx

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

Quality

54%

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

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 body is a strongly actionable Membrane CLI integration guide with executable commands and a clear connection-readiness feedback loop. Its main weaknesses are boilerplate concept explanation Claude already knows, inconsistent CLI invocation, and small structural/numbering gaps.

Suggestions

Remove the 'NGINX is a popular open-source web server...' paragraph and the vague Server/Configuration/File/Log tree — Claude already knows what NGINX is.

Standardize CLI invocation (pick either 'membrane' or 'npx @membranehq/cli@latest') and fix the step numbering (add a '1a' / remove the dangling 'Step 2' reference).

Replace the 'Popular actions' section's restated search command with an actual list of common NGINX actions, or remove the section if the search guidance already covers it.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient CLI guidance, but it pads concepts Claude already knows (the 'NGINX is a popular open-source web server, reverse proxy, load balancer...' intro) and includes a vague Overview tree ('Server / Configuration / File / Log'), fitting 'mostly efficient but includes some unnecessary explanation'.	3 / 5
Actionability	It provides concrete, copy-paste-ready commands for install, login, connection ensure, action list/run, and proxy requests plus a flag table, but minor gaps remain — inconsistent invocation ('membrane' vs 'npx @membranehq/cli@latest') and a 'Popular actions' section that merely repeats the search command instead of listing actions.	4 / 5
Workflow Clarity	The connect → poll-until-ready → handle client action → search → run sequence is clear with a genuine feedback loop (poll state, act on CLIENT_ACTION_REQUIRED, re-poll), but numbering gaps ('1b' with no '1a', a dangling 'skip to Step 2' with no Step 2) keep it just below the 5-anchor.	4 / 5
Progressive Disclosure	As a single-file skill with no bundle files, it is organized into well-signaled sections (Install, Authentication, Connecting, Searching, Running, Proxy, Best practices) appropriate for one-level structure; minor redundancy in 'Popular actions' and the odd Overview tree prevent a 5.	4 / 5
	Total	15 / 20 Passed

Description

41%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 has an explicit use-when trigger and a clear domain, but its capability statement is generic boilerplate ('manage data, records, and automate workflows') with sparse natural trigger terms. It is distinct as an NGINX skill yet underspecified on what it concretely does.

Suggestions

Replace 'Manage data, records, and automate workflows' with concrete NGINX actions such as 'inspect server config, query access/error logs, and run NGINX API actions'.

Expand trigger terms to include natural user phrasing like 'web server, reverse proxy, load balancer, nginx config, or access logs'.

Tighten the 'Use when' clause to reference specific NGINX tasks (e.g. 'Use when the user wants to query NGINX logs or manage server configuration') rather than the generic 'interact with NGINX data'.

Dimension	Reasoning	Score
Specificity	The description names the domain ('NGINX integration') but its actions are minimal and generic — 'Manage data, records, and automate workflows' describes no concrete NGINX capability, matching the 'names the domain but actions are minimal or generic' anchor rather than the 3-anchor which requires 1-2 concrete actions.	2 / 5
Completeness	An explicit 'Use when the user wants to interact with NGINX data' clause is present (so it is not capped by the missing-trigger rule), but the 'what' is vague boilerplate ('Manage data, records, and automate workflows'), pulling it below the 4-anchor which expects a concrete capability statement alongside the trigger.	3 / 5
Trigger Term Quality	It surfaces only the literal token 'NGINX' / 'NGINX data' and omits the natural phrases users actually say (web server, reverse proxy, load balancer, nginx config), fitting the 'one or two generic keywords; missing the natural phrases' anchor.	2 / 5
Distinctiveness Conflict Risk	The NGINX-named trigger carves a clear niche with minimal conflict risk against unrelated skills, though the generic 'manage data, records, workflows' wording leaves minor overlap with other integration skills, fitting 'mostly distinct; minor overlap risk'.	4 / 5
	Total	11 / 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/nginx/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.