Content
88%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 high-quality, actionable skill body: executable commands at every step, a well-sequenced workflow with real validation and a feedback loop, and genuinely non-obvious gotchas rather than padded explanations. The only gap is progressive disclosure, where the single-file linear workflow could be split for navigation.
Suggestions
Consider moving the launchd plist troubleshooting (the verify/fix/reload block) into a references/ file linked from step 6, reducing the inline footprint and giving the main workflow a cleaner one-level-deep reference structure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Efficient and focused; nearly every section adds non-obvious domain knowledge Claude would not already have (the plist crash-loop bug, the mandatory catch-all ingress rule, the credentials-file sync gotcha). A few explanatory prose passages could be trimmed, keeping it just below the lean-and-efficient anchor. | 4 / 5 |
Actionability | Fully executable, copy-paste-ready guidance throughout: 'cloudflared tunnel login', 'cloudflared tunnel create <username>', 'cloudflared tunnel route dns ...', a complete config.yml, a Rails hosts regex, an XML plist ProgramArguments block, launchctl commands, and a curl end-to-end check covering the common cases. | 5 / 5 |
Workflow Clarity | A clearly numbered six-step sequence (login, create, route, config, allow hosts, install) with explicit validation checkpoints — verify the plist actually runs the tunnel, watch logs for 'Registered tunnel connection', and a curl end-to-end check — plus a fix-and-reload feedback loop for the plist crash-loop failure mode. | 5 / 5 |
Progressive Disclosure | Well-organized into clear sections and numbered steps with no nested or buried references (no bundle files exist; the skill is a single cohesive file). It exceeds the simple-skill <50-line threshold and could optionally split the plist troubleshooting into a reference, so it sits at good-structure rather than the clear-overview-with-one-level-references anchor. | 4 / 5 |
Total | 18 / 20 Passed |