windows-symlinks

Create Windows directory junctions and symbolic links to synchronize configuration directories.

Updated Jan 31, 2026
One-click install
npx skills add https://github.com/JordiNodeJS/.github-config --skill windows-symlinks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: windows-symlinks
Source: https://github.com/JordiNodeJS/.github-config/tree/main/.github/skills/windows-symlinks
Command: npx skills add https://github.com/JordiNodeJS/.github-config --skill windows-symlinks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Windows configuration work often requires creating directory junctions and symbolic links to share and mirror tool configurations. This Skill provides safe, repeatable patterns to create junctions (no admin) and standard symbolic links (admin) to keep .agents, .cursor, .github, and .opencode in sync.

Core Features & Use Cases

  • Junctions (no admin required) to mirror directories across multiple tool configurations.
  • Symbolic links (admin required) for cross-drive access or file linking.
  • Safe verification, cleanup guidance, and Git-friendly workflows for maintaining single sources of truth.

Quick Start

Use the Windows commands below to set up a junction and a symbolic link for a sample directory structure.

  • Create a junction mirroring .agents/skills to .agent/skills: Remove-Item -Recurse -Force '..agent\skills' -ErrorAction SilentlyContinue New-Item -ItemType Junction -Path '..agent\skills' -Target (Resolve-Path '..agents\skills').Path
  • Create a symbolic link example: New-Item -ItemType SymbolicLink -Path '..target\dir' - Target (Resolve-Path '..source\dir').Path

Frequently Asked Questions about windows-symlinks

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

FAQPage Schema
How do I create a Windows directory junction without admin rights?

To create a Windows directory junction without admin rights, use the PowerShell command New-Item -ItemType Junction -Path <link> -Target <source>. Junctions allow you to mirror directories like .cursor and .agents across projects without requiring elevated privileges.

What is the difference between a Windows junction and a symbolic link for mirroring directories?

A Windows directory junction mirrors local directories without requiring admin rights, making it ideal for syncing local config folders. A symbolic link requires admin privileges but supports cross-drive access and individual file linking for broader filesystem mapping.

Can I use symbolic links to mirror .github and .opencode config folders across projects?

Yes, you can mirror .github and .opencode configuration folders across projects using symbolic links, but creating symbolic links requires admin rights. For local same-drive mirroring without admin rights, use directory junctions instead.

How do I safely remove an existing directory junction before recreating it in PowerShell?

To safely remove an existing directory junction before recreating it in PowerShell, use Remove-Item -Recurse -Force '<path>' -ErrorAction SilentlyContinue. This suppresses errors if the directory does not exist, ensuring a clean setup for the new junction.

When should I not use a directory junction for sharing configuration files?

You should not use a directory junction when you need cross-drive access or individual file linking, as junctions only mirror local directories. For cross-drive or file-level configuration sharing, use symbolic links, which require admin rights.