agentleFS
niksavisniksavis/handily/.agents/skills/wsl/SKILL.md

wsl

Skill2 starsChanged 34 days agoMITView on GitHub

Operates WSL: wsl.exe, interop, PATH, slow /mnt/c. Use when crossing Windows and Linux, or when a tool works in a terminal but not from a script.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use the Linux toolchain for repository work: Call <tool>.exe only when you want the Windows program, for example explorer.exe ..

    line 19

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md
<!-- Generated by `basicly skills-build` from skill.yaml. Do not edit; edit the source. -->

WSL

Work in WSL (Windows Subsystem for Linux) across the Windows and Linux boundary. The wsl.exe management and interop commands are in references/commands.md.

Rules

  • Keep project files on the Linux filesystem (~/...), not under /mnt/c/.... Access through /mnt is much slower, and its case and permission rules differ.
  • Run command -v <tool> when a tool behaves strangely. Interop puts Windows executables on the Linux PATH, so git, node or python can resolve to a .exe.
  • Use the Linux toolchain for repository work. Call <tool>.exe only when you want the Windows program, for example explorer.exe ..
  • Set PATH in the script, or run it through bash -lc '...'. A non-interactive shell does not read your profile.
  • Keep LF line endings. A Windows editor that writes CRLF breaks shell scripts and git hooks.

Non-interactive and login shells

A login or interactive shell reads ~/.bashrc or ~/.zshrc. That profile loads version managers and sets PATH. A script, a background job or a hook that an agent starts is non-interactive and does not read the profile. So the PATH, the aliases and the version managers of your terminal are not there. A command that works when you type it can then fail from a script.

The node and nvm form of this problem is in the node skill.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.