CtrlK
BlogDocsLog inGet started
Tessl Logo

native-wsl-workspaces

Reliably inspect, create, edit, validate, and transfer files in a Windows-hosted WSL workspace. Use when a task names a WSL path, a `\\wsl.localhost` path, a Windows/WSL project location, or when remote file writes, UNC paths, mounted workspaces, and WSL shell execution may disagree.

75

Quality

92%

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

SKILL.md
Quality
Evals
Security

Quality

Content

92%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.

A well-structured, lean instruction skill with a rigorously sequenced mandatory workflow, explicit validation checkpoints, and clean one-level-deep references to real executable scripts. The only minor gap is that the command-pattern block stays conceptual rather than offering a fully copy-paste ready example.

DimensionReasoningScore

Conciseness

The body is a lean ~40 lines of directive prose that assumes Claude knows WSL/UNC basics and never pads with introductory explanation; every line earns its place.

5 / 5

Actionability

Provides concrete invocations ("wsl.exe -d <distro> -- bash verify_wsl_workspace.sh <native-path> --probe-write") backed by real executable scripts, but the command-pattern block is a conceptual sequence rather than a complete copy-paste example with concrete values.

4 / 5

Workflow Clarity

The seven-step mandatory workflow is explicitly sequenced with an embedded validation gate ("Stop if it reports /mnt, drvfs…") and a recovery feedback loop, satisfying the checkpoint and error-recovery anchors.

5 / 5

Progressive Disclosure

A clear overview points one level deep to real bundled files (references/remote-execution.md, two scripts) via a Bundled resources table, with well-signaled navigation.

5 / 5

Total

19

/

20

Passed

Description

92%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.

A strong, third-person description that concretely enumerates capabilities and pairs them with explicit, domain-specific trigger conditions. It is slightly technical in phrasing but highly specific and well-scoped.

DimensionReasoningScore

Specificity

"inspect, create, edit, validate, and transfer files" lists five concrete, distinct actions covering the skill's full scope, matching the comprehensive-coverage anchor.

5 / 5

Completeness

Explicitly answers "what" (inspect/create/edit/validate/transfer files) and "when" with a concrete "Use when a task names a WSL path…" trigger clause.

5 / 5

Trigger Term Quality

Includes natural domain terms ("WSL path", "\\wsl.localhost path", "UNC paths", "mounted workspaces") plus the literal path syntax users would cite; slightly jargon-tilted rather than purely conversational, so just below the comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

A clear WSL-workspace niche with distinctive triggers (\wsl.localhost, UNC paths, WSL shell execution) makes conflict with unrelated skills unlikely.

5 / 5

Total

19

/

20

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
pvnkmnk/AgenticSelfHostSkills
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.