Content
65%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A well-structured, token-efficient overview of four access patterns with a genuine safety section, but the guidance stops short of executable commands for the Cloudflare and Nginx paths and lacks inline validation checkpoints. Adding concrete commands and validation steps per pattern would raise actionability and workflow clarity to match its organization.
Suggestions
Add executable commands to the Cloudflare Tunnel pattern (e.g., 'cloudflared tunnel login', 'cloudflared tunnel create <name>', 'cloudflared tunnel route dns <name> sub.domain.com') and a minimal config.yml example.
Include an example Nginx server block (proxy_pass, listen, Certbot certonly flags) instead of the bare instruction to 'Add a server block'.
Embed validation steps into each pattern (e.g., 'curl -I https://sub.domain.com' or 'cloudflared tunnel info' to confirm the route is live, with what to check on failure) rather than listing validation only in the Safety section.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and assumes competence ('No inbound firewall ports required', 'Caddy handles TLS automatically') with no padding explaining known concepts. It is not 5 because the 'Invocation' section (OpenCode/Codex/Freebuff lines) adds tokens with no value for the skill's actual task. It is not 3 because there is no unnecessary explanation beyond that section. | 4 / 5 |
Actionability | The Caddy pattern gives a concrete snippet ('subdomain.domain.com { reverse_proxy localhost:PORT }'), but the other patterns are high-level hints with no executable commands ('Install cloudflared', 'Create a tunnel and route a subdomain', 'Add a server block in /etc/nginx/sites-available/'). This matches the anchor of some concrete guidance with key details missing; it is not 4 because the most common cases (Cloudflare Tunnel, Nginx) lack copy-paste commands. | 3 / 5 |
Workflow Clarity | Each access pattern has a recognizable step sequence, and one checkpoint exists ('Validate DNS propagation before considering a tunnel live'), but validation is not woven into the steps and there is no error-recovery guidance (e.g., what to check if the tunnel doesn't come up). It is not 2 because sequences are present and reasonably defined; not 4 because checkpoints are mostly implicit rather than inline validation steps. | 3 / 5 |
Progressive Disclosure | The skill is under 50 lines, self-contained with no bundle files needed (references/ and scripts/ are empty), and organized into clear sections (Access Patterns with four sub-patterns, Safety, Companion Skills, References) with one-level-deep external links clearly signaled. This matches the simple-skill exception: well-organized sections alone justify a 5. | 5 / 5 |
Total | 15 / 20 Passed |