Agent skill

Windows Shell Reliability

by sickn33 in sickn33/agentic-awesome-skills

Reliable command execution on Windows: paths, encoding, and common binary pitfalls.

MITAuto-check passedDevOps & Cloud

Install Windows Shell Reliability

skills CLI
$ npx skills add sickn33/agentic-awesome-skills --skill windows-shell-reliability -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install sickn33/agentic-awesome-skills windows-shell-reliability --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/windows-shell-reliability .claude/skills/windows-shell-reliability && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
windows-shell-reliability
GitHub stars
47k
Used in
2 other repos
Token cost
~1k tokens
SKILL.md length
464 words
Files
1
Skills in repo
1,394
Repo updated
First seen
Licence
MIT

At a glance

Reliable command execution on Windows: paths, encoding, and common binary pitfalls.

  • Works in 7 steps: Encoding & Redirection → Handling Paths & Spaces → Common Binary & Cmdlet Pitfalls → …
  • DevOps & Cloud work in your project
  • SKILL.md covers When to Use, 1. Encoding & Redirection, 2. Handling Paths & Spaces and 3. Common Binary & Cmdlet…, plus 5 more sections
  • Calls dotnet and npm

What it does

Windows Shell Reliability is an agent skill from sickn33/agentic-awesome-skills. Reliable command execution on Windows: paths, encoding, and common binary pitfalls.

Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in DevOps & Cloud. It works with PowerShell and .NET. The repository describes itself as: AAS Core is the local, agent-first control plane for complete catalog discovery, agent-owned selection, stack validation, and planning, backed by 2,400+ agentic skills. Includes… The licence is MIT.

When your agent uses it

  • DevOps & Cloud work in your project

Example prompts

  • “/windows-shell-reliability”

Workflow steps

7 steps, taken from the step headings in SKILL.md.

  1. Encoding & Redirection
  2. Handling Paths & Spaces
  3. Common Binary & Cmdlet Pitfalls
  4. Dotnet CLI Reliability
  5. Environment Variables
  6. Long Paths
  7. Troubleshooting Shell Errors

What it can do on your machine

Read from SKILL.md and the folder at commit 1e53ce2. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • dotnet
    • npm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npm, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Windows Shell Reliability loads about 1k tokens when it runs. Until then it costs about 27 tokens; SKILL.md has 464 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~27
When it runs · the whole SKILL.md, loaded when a task matches
~1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from sickn33/agentic-awesome-skills at commit 1e53ce2, republished under its MIT licence (© sickn33). 464 words, ~1,008 tokens.

Download SKILL.mdSave it as .claude/skills/windows-shell-reliability/SKILL.md (or your agent's skills folder).
name
windows-shell-reliability
description
Reliable command execution on Windows: paths, encoding, and common binary pitfalls.
risk
safe
source
community
date_added
2026-03-19

Windows Shell Reliability Patterns

Best practices for running commands on Windows via PowerShell and CMD.

When to Use

Use this skill when developing or debugging scripts and automation that run on Windows systems, especially when involving file paths, character encoding, or standard CLI tools.


1. Encoding & Redirection

CRITICAL: Redirection Differences Across PowerShell Versions

Older Windows PowerShell releases can rewrite native-command output in ways that break later processing. PowerShell 7.4+ preserves the byte stream when redirecting stdout, so only apply the UTF-8 conversion workaround when you are dealing with older shell behavior or a log file that is already unreadable.

ProblemSymptomSolution
dotnet > log.txtview_file fails in older Windows PowerShell`Get-Content log.txt
npm run > log.txtNeed a UTF-8 text log with errors included`npm run ... 2>&1

Rule: Prefer native redirection as-is on PowerShell 7.4+, and use explicit UTF-8 conversion only when older Windows PowerShell redirection produces an unreadable log.


2. Handling Paths & Spaces

CRITICAL: Quoting

Windows paths often contain spaces.

❌ Wrong✅ Correct
dotnet build src/my project/file.fsprojdotnet build "src/my project/file.fsproj"
& C:\Path With Spaces\bin.exe& "C:\Path With Spaces\bin.exe"

Rule: Always quote absolute and relative paths that may contain spaces.

The Call Operator (&)

In PowerShell, if an executable path starts with a quote, you MUST use the & operator.

Pattern:

powershell
& "C:\Program Files\dotnet\dotnet.exe" build ...

3. Common Binary & Cmdlet Pitfalls

Action❌ CMD Style✅ PowerShell Choice
Deletedel /f /q fileRemove-Item -Force file
Copycopy a bCopy-Item a b
Movemove a bMove-Item a b
Make Dirmkdir folderNew-Item -ItemType Directory -Path folder

Tip: Using CLI aliases like ls, cat, and cp in PowerShell is usually fine, but using full cmdlets in scripts is more robust.


Show full SKILL.md (186 more words)Show less

4. Dotnet CLI Reliability

Build Speed & Consistency
ContextCommandWhy
Fast Iterationdotnet build --no-restoreSkips redundant nuget restore.
Clean Builddotnet build --no-incrementalEnsures no stale artifacts.
BackgroundStart-Process dotnet -ArgumentList 'run' -RedirectStandardOutput output.txt -RedirectStandardError error.txtLaunches the app without blocking the shell and keeps logs.

5. Environment Variables

ShellSyntax
PowerShell$env:VARIABLE_NAME
CMD%VARIABLE_NAME%

6. Long Paths

Windows has a 260-character path limit by default.

Fix: If you hit long path errors, use the extended path prefix: \\?\C:\Very\Long\Path\...


7. Troubleshooting Shell Errors

ErrorLikely CauseFix
The term 'xxx' is not recognizedPath not in $env:PATHUse absolute path or fix PATH.
Access to the path is deniedFile in use or permissionsStop process or run as Admin.
Encoding mismatchOlder shell redirection rewrote the outputRe-export the file as UTF-8 or capture with `2>&1

Limitations

  • Use this skill only when the task clearly matches the scope described above.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

© sickn33, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/windows-shell-reliability of sickn33/agentic-awesome-skills.

Open the folder on GitHubat commit 1e53ce2

Used in 2 other repositories

We found 11 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 2 other GitHub owners. This page covers the copy in sickn33/agentic-awesome-skills, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Windows Shell Reliability next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Windows Shell Reliability compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Windows Shell Reliability this skillsickn33/agentic-awesome-skills47k2 repos~1kAutomated safety check: PassMIT
Azure FunctionsDataDog/dd-trace-dotnet573—~4.7kAutomated safety check: PassApache-2.0
Nuget Trusted Publishingdotnet/skills5.6k2 repos~2.3kAutomated safety check: PassMIT
MAUI UI Test Shard Rebalancerdotnet/maui23k—~995Automated safety check: PassMIT
Copilot Session Failure Analysisdotnet/maui23k—~3.4kAutomated safety check: PassMIT
Evaluate PR Testsdotnet/maui23k—~2.9kAutomated safety check: PassMIT

Similar skills

  • Azure Functions

    DataDog/dd-trace-dotnet

    Official

    Dev/test workflow for tracer engineers working on the Datadog .NET tracer — build a local Datadog.AzureFunctions NuGet package, deploy it to a test Azure Function App, trigger it, and analyze…

    573 GitHub stars~4.7k tokensUpdated today
    DevOps & CloudAuto-check passed
  • Official

    Set up NuGet trusted publishing (OIDC) on a GitHub Actions repo — replaces long-lived API keys with short-lived tokens.

    5.6k GitHub starsUsed in 2 repos~2.3k tokens
    DevOps & CloudAuto-check passed
  • Official

    Splits a slow .NET MAUI UI-test category into method-level CI shards sized from historical Azure DevOps timings so each job fits a target duration.

    23k GitHub stars~995 tokensUpdated today
    Testing & QAAuto-check passed
  • Mines local Copilot CLI session logs for dotnet/maui to rank costly or failing runs, tag recurring failure modes, propose repo edits and emit guard evals.

    23k GitHub stars~3.4k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Official

    Reviews the tests added in a pull request for fix coverage, quality, edge cases and test type, and recommends lighter test types where they would do.

    23k GitHub stars~2.9k tokensUpdated today
    Testing & QAAuto-check passed
  • Official

    Modify Cottle templates that generate Dockerfiles and READMEs in dotnet/dotnet-docker.

    4.9k GitHub stars~563 tokensUpdated today
    DevOps & CloudAuto-check passed

More from sickn33/agentic-awesome-skills

All 1,394 skills in this repo
  • Liuguang Banlan UI

    sickn33/agentic-awesome-skills

    Implements an interface in one of two named color modes, iridescent white or colorful black, from a parameterized starter that reports measured color intensity.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed
  • User Thoughts Memory

    sickn33/agentic-awesome-skills

    Saves a user's project decisions, rules and preferences into a project-local mdbase so later sessions and other agents can recover the intent.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed
  • Using LWC Memory and Graphs

    sickn33/agentic-awesome-skills

    Keeps project decisions, research and verified results available across coding-agent sessions through LWC memory, a document Wiki graph and a CodeGraph code index.

    47k GitHub starsUsed in 1 repo~2k tokens
    Auto-check passed
  • Find Complementary Founders

    sickn33/agentic-awesome-skills

    Guides an agent through assessing its own owner for cofounder fit, publishing an approved profile, and ranking complementary profiles other agents published for their owners.

    47k GitHub starsUsed in 1 repo~4.8k tokens
    Auto-check passed
  • Whatsapp Cloud API

    sickn33/agentic-awesome-skills

    Integracao com WhatsApp Business Cloud API (Meta). An agent skill from sickn33/agentic-awesome-skills.

    47k GitHub starsUsed in 2 repos~4.5k tokens
    Auto-check passed
  • Cline Pilot

    sickn33/agentic-awesome-skills

    Acts as a proxy for the Cline CLI, dispatching coding tasks one at a time, monitoring runs by hard evidence, relaying decisions to you and learning per-project preferences.

    47k GitHub starsUsed in 1 repo~4.6k tokens
    Auto-check passed

Works with

Categories

Questions about Windows Shell Reliability

What does Windows Shell Reliability do?

Reliable command execution on Windows: paths, encoding, and common binary pitfalls. Windows Shell Reliability is an agent skill from sickn33/agentic-awesome-skills. Reliable command execution on Windows: paths, encoding, and common binary pitfalls.

When should I use Windows Shell Reliability?

Windows Shell Reliability fits situations like: devOps & Cloud work in your project.

How do I install Windows Shell Reliability in Claude Code?

Run `npx skills add sickn33/agentic-awesome-skills --skill windows-shell-reliability -a claude-code`. Or copy the skill folder (skills/windows-shell-reliability in sickn33/agentic-awesome-skills) into .claude/skills/windows-shell-reliability in your project. Claude Code loads it when a task matches its description.

How do I install Windows Shell Reliability in Codex?

Run `npx skills add sickn33/agentic-awesome-skills --skill windows-shell-reliability -a codex`. Or copy the skill folder (skills/windows-shell-reliability in sickn33/agentic-awesome-skills) into .agents/skills/windows-shell-reliability in your project. Codex loads it when a task matches its description.

Can I use Windows Shell Reliability in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sickn33/agentic-awesome-skills --skill windows-shell-reliability -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/windows-shell-reliability, .gemini/skills/windows-shell-reliability, .github/skills/windows-shell-reliability and .opencode/skills/windows-shell-reliability in your project.

What does Windows Shell Reliability need to run?

Going by SKILL.md and its folder, Windows Shell Reliability needs the command-line tools its instructions call (dotnet and npm).

Does Windows Shell Reliability access the network?

SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Windows Shell Reliability safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Windows Shell Reliability use?

Windows Shell Reliability is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Windows Shell Reliability use?

About 1k tokens (SKILL.md is roughly 4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Windows Shell Reliability?

Skills that share tags, products or a category with Windows Shell Reliability: Azure Functions (DataDog/dd-trace-dotnet, 573 stars), Nuget Trusted Publishing (dotnet/skills, 5.6k stars), MAUI UI Test Shard Rebalancer (dotnet/maui, 23k stars) and Copilot Session Failure Analysis (dotnet/maui, 23k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Windows Shell Reliability?

sickn33 (a GitHub user) maintains it in sickn33/agentic-awesome-skills, which has 47,304 GitHub stars. The repository holds 1,394 skills in this directory. The repository was last updated on October 6, 2026.

Source: sickn33/agentic-awesome-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.