Content
56%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.
The skill is highly actionable with verified, copy-paste-ready commands and a well-sequenced workflow with validation checkpoints, but it is severely over-inflated: duplicated narratives, padded explanatory sections, and dangling file references undermine token efficiency and structure. Cutting the body to a lean overview that defers to the existing reference guides would address most weaknesses.
Suggestions
Cut the body to a lean Quick Start plus script reference (~150-200 lines): remove the duplicated Quick Start/Workflow overlap, the simulated credential output blocks, 'What You Can Do', 'Example Commands to Try', the iOS/Android bookmark instructions, and the pre-checked Success Checklist.
Move the Security Essentials threat model, Performance Expectations, and the ttyd vs code-server comparison into the existing reference guides (security-guide.md, tunneling-options.md) and link to them instead of inlining.
Fix dangling references: either add the templates/ directory with ttyd.service and .env.template, or remove the 'File: templates/...' and 'cp templates/...' instructions; do the same for the non-existent ~/.ttyd/PERSISTENT-SESSION-GUIDE.md and CONNECTION-KEEPALIVE-GUIDE.md pointers, and relocate the orphaned 'Connection Timeout' and 'Persistent Session' sections (which document critical readonly-mode and tmux behavior) into the main workflow or troubleshooting section.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The ~950-line body is noticeably to heavily padded: the Quick Start duplicates the entire Workflow section, simulated credential output blocks appear three times, and sections like 'What You Can Do' ('Run any command you normally run in terminal', 'Navigate directories'), 'Example Commands to Try' (uname -a, ls -la, htop), iOS/Android bookmark instructions, and a pre-checked Success Checklist explain things Claude already knows. Not 1 because genuine instructional content (exact script invocations, tunnel setup, verified fixes) is interwoven throughout. | 2 / 5 |
Actionability | Commands are copy-paste ready and verified against the bundle (TTYD_PORT, --writable, --ngrok/--cloudflare/--tailscale, --custom-password, tmux new -As ttyd-mobile, --ping-interval 3 all exist in the scripts). Not 5 because referenced files that commands depend on do not exist: 'cp templates/ttyd.service ~/.config/systemd/user/' would fail (no templates/ directory), and the ~/.ttyd/PERSISTENT-SESSION-GUIDE.md and CONNECTION-KEEPALIVE-GUIDE.md 'complete guides' are not created by any script. | 4 / 5 |
Workflow Clarity | Steps 1-6 are clearly sequenced with verification checkpoints (1.4 verify installation, 5.2 verify stopped, ttyd-status.sh checks) and per-error troubleshooting fixes. Not 5 because two critical behaviors (the readonly-mode keyboard fix and the persistent tmux session default) are appended as orphaned headings after the document's closing sign-off line, disconnected from the main flow, and the Quick Start/Workflow duplication creates two parallel narratives for the same process. | 4 / 5 |
Progressive Disclosure | The five reference guides exist and are well-signaled one level deep, but the body inlines large amounts of content that belongs in those references (threat model, performance statistics, tunnel comparison duplicating tunneling-options.md), forming a ~950-line monolithic overview. Referenced paths that do not exist in the bundle (templates/ttyd.service, templates/.env.template, ~/.ttyd/*-GUIDE.md) further break the navigation structure. | 3 / 5 |
Total | 13 / 20 Passed |