Skip to content
TrustedSkillsbeta
Back to all skills

Windows Git Bash Paths

Checked
josiahsiegel·vlatest·backend·MIT

Translates user requests into Windows Git Bash paths for file access and command execution.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add josiahsiegel/claude-plugin-marketplace --skill windows-git-bash-paths -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

josiahsiegel

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned josiahsiegel/claude-plugin-marketplace at 5a1b1123b9.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
5a1b1123b9
Manifest
plugins/ssdt-master/skills/windows-git-bash-paths/SKILL.md
Scanned
1 file, 487 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill helps AI agents correctly translate file paths when interacting with Windows systems using Git Bash (MINGW/MSYS2). It addresses the issue where Git Bash automatically converts POSIX-style paths to Windows paths, which can cause problems when executing commands or accessing files via tools like SqlPackage and MSBuild. The skill provides guidance on how to avoid these path conversion errors and ensure proper file access within a Windows development environment.

When to use it

  • When an AI agent needs to execute command-line tools (like sqlpackage or MSBuild) on a Windows machine using Git Bash.
  • When the AI agent is instructed to work with files located in paths that would be interpreted differently by Git Bash and Windows native tools.
  • When interacting with SQL Server development environments (SSDT) where path conversions are common.

Key capabilities

  • Provides guidance on converting POSIX-style file paths to Windows-style paths using backslashes (\).
  • Explains how Git Bash automatically converts paths and the resulting issues.
  • Offers best practices for SSDT workflows within a Git Bash environment.
  • Emphasizes the importance of using backslashes in file paths when interacting with tools like Edit or Write.

Example prompts

  • "Execute SqlPackage to publish MyDB.dacpac."
  • "Run MSBuild on the project located at /repos/project."
  • "Access and edit the file located at /D/repos/project/file.tsx."

Tips & gotchas

  • Crucially, always use backslashes (\) in file paths when using tools like Edit or Write. Forward slashes (/) will cause errors.
  • Be aware that Git Bash automatically converts POSIX-style paths to Windows paths, which can lead to unexpected behavior if not handled correctly.
  • This skill focuses on path conversion issues within the context of SQL Server development (SSDT) and using Git Bash on Windows.