CtrlK
BlogDocsLog inGet started
Tessl Logo

ttyd-remote-terminal-wsl2

Setup secure web-based terminal access to WSL2 from mobile/tablet via ttyd + ngrok/Cloudflare/Tailscale. One-command install, start, stop, status. Use when you need remote terminal access, web terminal, browser-based shell, or mobile access to WSL2 environment.

66

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/ttyd-remote-terminal-wsl2/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

60%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable and well-sequenced with real validation checkpoints and a clean one-level reference structure, but it is significantly over-long: padded sections and duplicated Quick-Start/Workflow content push conciseness down. Tightening the body and offloading peripheral sections to references would lift the weakest dimension.

Suggestions

Trim or move peripheral sections (Tips & Tricks, Performance Expectations, ttyd vs code-server comparison, Success Checklist) into a reference file or remove them — they explain concepts Claude already knows and roughly double the body length.

Collapse the duplicated Quick Start and full Workflow into a single sequenced procedure so steps are not stated twice; keep concrete commands but drop the repeated full connection-info output blocks.

Promote validation to explicit validate→fix→retry loops (e.g. after install and after start) to push workflow clarity from 4 toward 5.

DimensionReasoningScore

Conciseness

The body runs ~1010 lines with several padded sections (Tips & Tricks, Performance Expectations, ttyd-vs-code-server comparison, emoji success checklist, repeated full connection-info blocks) that explain things Claude already knows or restate the Quick Start in the longer Workflow. It is noticeably verbose rather than lean, fitting the 'several unnecessary explanations or padded sections' anchor and not the level-3 'mostly efficient' one.

2 / 5

Actionability

Concrete executable commands appear throughout — `./install.sh`, `./configure-auth.sh`, `--writable`, `--ping-interval 3`, `TTYD_PORT=7682 ./ttyd-start.sh` — and the referenced scripts all exist, giving mostly copy-paste-ready guidance with only minor gaps (script internals are described rather than shown).

4 / 5

Workflow Clarity

A clearly sequenced six-step workflow (Setup → Auth → Start → Connect → Stop → Status) with explicit validation checkpoints (1.4 Verify Installation, 5.2 Verify Stopped, health-check.sh) and recovery loops for the risky public-exposure operation. It sits just below the level-5 anchor because a few checkpoints are implicit rather than framed as validate→fix→retry.

4 / 5

Progressive Disclosure

SKILL.md is an overview pointing to five real one-level-deep reference guides (installation, security, tunneling, networking, troubleshooting), all clearly signaled in a Reference Guides section. It is not level 5 because some inline content (Tips & Tricks, Performance Expectations, the comparison) arguably belongs in separate files, leaving minor organization gaps.

4 / 5

Total

14

/

20

Passed

Description

100%Weight 40%Scale 1-5

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 is strong across all dimensions: concrete actions, natural trigger synonyms, explicit what-and-when, and a distinct niche with minimal overlap risk. It matches the top anchor on every rubric dimension.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Setup secure web-based terminal access', 'One-command install, start, stop, status' — via named tools (ttyd + ngrok/Cloudflare/Tailscale), giving comprehensive coverage.

5 / 5

Completeness

Explicitly answers both what ('Setup secure web-based terminal access to WSL2 ... via ttyd + ngrok/Cloudflare/Tailscale. One-command install, start, stop, status') and when ('Use when you need remote terminal access ...').

5 / 5

Trigger Term Quality

Includes natural user-facing phrases with synonyms — 'remote terminal access, web terminal, browser-based shell, mobile access to WSL2' — covering the ways a user would naturally request this.

5 / 5

Distinctiveness Conflict Risk

A clear WSL2-specific remote-terminal niche with distinct triggers; the body even disambiguates against a sibling skill (code-server-remote-ide-wsl2), so conflict risk is minimal.

5 / 5

Total

20

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (1010 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository
fernandezbaptiste/Skrillz
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.