symlink-claude-config

Convert a copy-based Claude configuration directory into a live symlink view of ~/.claude.

1|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/KangOxford/auto-quant-research --skill symlink-claude-config
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: symlink-claude-config
Source: https://github.com/KangOxford/auto-quant-research/tree/main/execution-layer/skills/symlink-claude-config
Command: npx skills add https://github.com/KangOxford/auto-quant-research --skill symlink-claude-config

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Convert a copy-based Claude configuration directory into a live symlink view that points to the canonical ~/.claude directory. After migration, changes on the source side are reflected on the public view with zero manual syncing.

Core Features & Use Cases

  • Live symlink view to mirror canonical Claude config in public directories while preserving the internal memory paths.
  • Safe handling of secrets: skips sensitive files like .credentials.json, .notion_token, and history-related data.
  • mv-authorization aware: coordinates with a permission hook to obtain explicit user approval before moving files during migration.

Quick Start

Run the symlink-claude-config.sh script against the public Claude config directory to create a live symlink view of ~/.claude.

Frequently Asked Questions about symlink-claude-config

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

FAQPage Schema
How do I create a live symlink view of the Claude config directory?

A symlink view mirrors the canonical ~/.claude directory into a public path. It eliminates manual syncing by automatically reflecting source configuration changes while preserving internal memory paths.

How does the Claude config migration process handle sensitive files like credentials?

The Claude config migration process automatically skips sensitive files like .credentials.json, .notion_token, and history data. This safe file selection ensures secrets remain protected in the canonical directory while only non-sensitive configurations are exposed publicly.

How do I get permission to move files during Claude config migration if hooks block it?

The workflow coordinates with permission hooks using an explicit mv-authorization step to obtain user approval before moving files. This bypasses blocked operations by requesting explicit consent during the Claude config migration.

Can I share my Claude configuration setup across a public team directory?

Yes, teams can share Claude setups across public directories by converting copy-based configs into symlink views. This provides shared access while enforcing memory preservation and protecting sensitive credentials from exposure.

Why are my Claude configuration changes not syncing to the public directory?

Claude configuration changes fail to sync to a public directory when using copy-based setups instead of live symlinks. Converting the directory to a symlink view pointing to ~/.claude ensures source modifications reflect automatically with zero manual syncing.