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.
83
77%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./infrastructure/nginx-config-generator/SKILL.mdQuality
Discovery
67%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description excels at listing specific, concrete capabilities for Nginx configuration generation, making it highly distinctive. However, it lacks an explicit 'Use when...' clause that would help Claude know exactly when to select this skill, and could benefit from additional natural trigger terms users might say.
Suggestions
Add a 'Use when...' clause with trigger phrases like 'Use when the user asks about Nginx configuration, reverse proxy setup, web server config, or mentions nginx.conf files'
Include common variations of trigger terms such as 'HTTPS setup', 'web server', 'proxy config', 'nginx.conf', or 'load balancer configuration'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'SSL/TLS (Let's Encrypt)', 'static file serving', 'upstream definitions', 'rate limiting', 'gzip compression', 'security headers', and 'location blocks'. These are all concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers 'what does this do' with comprehensive capability listing, but lacks an explicit 'Use when...' clause or equivalent trigger guidance. The 'when' is only implied by the capabilities themselves. | 2 / 3 |
Trigger Term Quality | Includes good technical terms like 'Nginx', 'reverse proxy', 'SSL/TLS', 'Let's Encrypt' that users would naturally mention. However, missing common variations like 'web server config', 'proxy setup', 'HTTPS', or file extensions like 'nginx.conf'. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific niche focused on Nginx configurations. The combination of 'Nginx', 'reverse proxy', and specific features like 'Let's Encrypt' and 'upstream definitions' makes it clearly distinguishable from other web server or configuration skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill that provides comprehensive, production-ready Nginx configurations. The content is concise, assumes Claude's competence, and delivers immediately usable code. The main weakness is the lack of an explicit validation workflow - the skill should emphasize testing configs with 'nginx -t' before applying changes, especially given that invalid configs can break the server.
Suggestions
Add a 'Making Changes Safely' workflow section that explicitly sequences: edit config → run 'nginx -t' → if errors, fix and re-test → only when valid, run 'nginx -s reload'
Consider adding a brief troubleshooting section for common config errors (e.g., missing semicolons, invalid upstream references) to help with error recovery
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, providing concrete configurations without explaining what Nginx is or how reverse proxies work. Every section delivers actionable config snippets that Claude can directly use. | 3 / 3 |
Actionability | Fully executable Nginx configurations throughout - complete nginx.conf, virtual host configs, SSL snippets, and Docker Compose examples. All code is copy-paste ready with realistic values and proper syntax. | 3 / 3 |
Workflow Clarity | While the project structure and patterns are clear, there's no explicit validation workflow. The Common Commands section lists 'nginx -t' but doesn't integrate it into a step-by-step process for making config changes safely. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections progressing from prerequisites to scaffold to patterns to commands. The snippets approach naturally separates concerns, and Integration Notes appropriately reference other skills without deep nesting. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
181fcbc
Table of Contents
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.