path-normalizer

Normalize tilde-based file paths to absolute paths for file tools.

3|Updated Feb 28, 2026
One-click install
npx skills add https://github.com/Dalomeve/bot-output --skill path-normalizer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: path-normalizer
Source: https://github.com/Dalomeve/bot-output/tree/main/skills/path-normalizer
Command: npx skills add https://github.com/Dalomeve/bot-output --skill path-normalizer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Normalize tilde-based file paths to ensure reliable file tool operations when paths begin with ~, preventing path failures and misreads.

Core Features & Use Cases

  • Resolves home directory tilde prefixes for POSIX and Windows styles.
  • Applies to read, edit, and write file tools, ensuring absolute paths are used.
  • Use case: a script calls read with path ~/docs/config.txt and receives a normalized absolute path.

Quick Start

Execute a path normalization on a sample path such as ~/projects/plan.md to obtain an absolute path.

Frequently Asked Questions about path-normalizer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I normalize tilde paths for reliable file IO operations?

Path normalization for tilde prefixes resolves ~/ and ~user/ formats into absolute paths across POSIX and Windows systems. This process ensures file tools receive valid directory locations for read, edit, and write operations without encountering resolution errors.

Why does my file tool fail when I pass a path starting with ~?

File tools fail with tilde paths because they lack native home directory expansion. Normalizing paths starting with ~ resolves the prefix into an absolute path, preventing misreads and ensuring the file tool locates the target file correctly.

Does path normalization work for both POSIX and Windows filesystem tilde formats?

Path normalization supports both POSIX and Windows filesystem tilde formats. It resolves home directory prefixes across both operating systems, converting formats like ~/... and their Windows equivalents into reliable absolute paths for file operations.

How do I convert a tilde-based path to an absolute path for a script?

To convert a tilde-based path to an absolute path, apply home directory resolution to expand the ~ prefix. This normalization process transforms paths like ~/docs/config.txt into their full absolute equivalents, making them safe for script read and write operations.

Are there limitations to normalizing tilde paths without checking file existence?

A key limitation of normalizing tilde paths without file existence checks is that it only guarantees a syntactically correct absolute path. It does not verify the file exists, meaning subsequent read or write operations could still fail if the target file is missing.