CtrlK
BlogDocsLog inGet started
Tessl Logo

nginx-config-generator

Generate Nginx reverse proxy configurations with SSL/TLS (Let's Encrypt), static file serving, upstream definitions, rate limiting, gzip compression, security headers, and location blocks.

62

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./infrastructure/nginx-config-generator/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%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.

Highly actionable with complete, copy-paste-ready Nginx configs and minimal padding, but it lacks an explicit scaffold-to-reload workflow with validation checkpoints and keeps all reference-grade content inline rather than splitting it into bundle files.

Suggestions

Add a short numbered workflow that wires validation into the sequence: 1) run Scaffold Command, 2) author configs from Essential Patterns, 3) `nginx -t` to validate, 4) `nginx -s reload` only on success, 5) re-validate if errors.

Move the full snippet files (ssl-params.conf, security-headers.conf, proxy-params.conf) and the docker-compose/certbot block into references/ files and link to them from SKILL.md to improve progressive disclosure.

State the destructive-op safety check explicitly (always run `nginx -t` before `nginx -s reload`) as a labeled validation step.

DimensionReasoningScore

Conciseness

Lean, code-heavy content that assumes Claude's competence and avoids explaining what Nginx is; minor trimming possible (full cipher/mime lists, complete snippet files) but no padded prose.

4 / 5

Actionability

Fully executable, copy-paste-ready configs and commands covering the common cases — full nginx.conf, app.conf with SSL/WebSocket/static/SPA, snippets, load balancing, and certbot/docker-compose setup.

5 / 5

Workflow Clarity

Sections are present (Scaffold, Structure, Patterns, Common Commands) and `nginx -t` validation exists, but there is no explicit sequenced workflow with checkpoints (e.g. scaffold -> write config -> `nginx -t` -> `nginx -s reload`), so the validate-before-reload feedback loop is only implicit.

3 / 5

Progressive Disclosure

Well-organized into clear sections, but everything is inlined in a ~330-line SKILL.md with no bundle files; reference-grade material (full snippet configs, docker-compose block) that belongs in one-level-deep reference files is kept inline.

3 / 5

Total

15

/

20

Passed

Description

75%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.

A specific, third-person description with strong capability coverage and distinct triggers, but it omits any explicit 'when to use' guidance, which limits completeness. Adding a Use-when clause would lift the description to the top band.

Suggestions

Append an explicit trigger clause, e.g. 'Use when generating or reviewing Nginx reverse proxy configs, setting up SSL/TLS with Let's Encrypt, or configuring rate limiting, gzip, and security headers.'

Add natural synonyms users might say ('load balancer', 'TLS certificates', 'HTTPS') to broaden trigger coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities — 'reverse proxy configurations with SSL/TLS (Let's Encrypt), static file serving, upstream definitions, rate limiting, gzip compression, security headers, and location blocks' — giving comprehensive coverage rather than vague abstraction.

5 / 5

Completeness

Has a clear 'what' (generate nginx reverse proxy configs with listed features) but no 'Use when...' / 'when should Claude use it' clause, which caps completeness at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

Strong natural terms a devops user would say ('Nginx', 'reverse proxy', 'SSL/TLS', 'Let's Encrypt', 'rate limiting', 'gzip'), but a few natural synonyms (e.g. 'load balancer', 'TLS certs') are absent and there is no file-extension or phrasing variety.

4 / 5

Distinctiveness Conflict Risk

Clearly scoped to Nginx config generation with a distinct niche; the trigger terms (nginx, reverse proxy, Let's Encrypt, rate limiting) are unlikely to fire for unrelated skills.

5 / 5

Total

17

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
achreftlili/deep-dev-skills
Reviewed

Table of Contents

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.