caddy-reverse-proxy
Caddy reverse proxy configuration, Caddyfile syntax, automatic HTTPS, Docker integration, and common patterns
77
71%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./caddy-reverse-proxy/SKILL.mdQuality
Discovery
54%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 effectively identifies the Caddy ecosystem with good trigger terms but reads as a topic list rather than an actionable skill description. It lacks concrete actions (verbs describing what the skill does) and completely omits guidance on when Claude should use this skill, which is critical for skill selection.
Suggestions
Add a 'Use when...' clause specifying triggers like 'when the user asks about Caddy configuration, Caddyfile syntax, or setting up reverse proxies with Caddy'
Convert topic areas into concrete actions: 'Generates Caddyfile configurations, sets up automatic HTTPS, configures Docker-based Caddy deployments, and troubleshoots reverse proxy issues'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Caddy reverse proxy) and lists several areas (Caddyfile syntax, automatic HTTPS, Docker integration, common patterns), but these are topic areas rather than concrete actions like 'configure', 'generate', or 'troubleshoot'. | 2 / 3 |
Completeness | Only describes 'what' at a topic level, completely missing the 'when' clause. No 'Use when...' guidance or explicit triggers for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'Caddy', 'reverse proxy', 'Caddyfile', 'HTTPS', 'Docker'. These are terms users would naturally use when seeking help with Caddy configuration. | 3 / 3 |
Distinctiveness Conflict Risk | Caddy is a specific tool with distinct terminology (Caddyfile, automatic HTTPS). Unlikely to conflict with other reverse proxy skills (nginx, Apache) due to explicit Caddy naming. | 3 / 3 |
Total | 9 / 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, actionable Caddy configuration patterns with excellent token efficiency. The examples are executable and well-organized across logical sections. The main weakness is the lack of explicit validation checkpoints in workflows—the management commands section mentions validation but doesn't integrate it into a clear change workflow.
Suggestions
Add an explicit workflow section showing the recommended sequence: edit Caddyfile -> validate -> reload, with error recovery steps if validation fails
Consider adding a brief 'Making changes safely' section that emphasizes validating before reloading to prevent downtime
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, providing direct code examples without explaining what Caddy is beyond a single sentence. Every section delivers actionable configuration snippets without unnecessary preamble or concepts Claude already knows. | 3 / 3 |
Actionability | All examples are copy-paste ready Caddyfile configurations and shell commands. The docker-compose.yml, management commands, and troubleshooting table provide fully executable, concrete guidance. | 3 / 3 |
Workflow Clarity | While individual patterns are clear, the skill lacks explicit validation workflows. The troubleshooting table helps, but there's no clear 'validate -> fix -> reload' sequence emphasized for config changes, which is important for avoiding downtime. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear section headers progressing from basics to advanced patterns. For a reference-style skill of this scope, the structure is appropriate with logical groupings and a helpful comparison table at the end. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- ddnetters/homelab-agent-skills
- Commit
87d2278
- 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.