Use for conf/symlinks.toml, SymlinkResource target computation, or install/remove/materialization behavior.
Scanned 8/31/2026
Install to Claude Code
Skills Directorynpx -y skills add sneivandt/dotfiles --skill symlink-management --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Symlink Management?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/sneivandt-symlink-management)More formats (shields.io, HTML) on the badges page.
---
name: symlink-management
description: >
Use for conf/symlinks.toml, SymlinkResource target computation,
or install/remove/materialization behavior.
---
# Symlink Management
Sources are relative to `symlinks/`, have no leading dot, and cannot escape that
tree. Explicit targets are home-relative. Reject absolute paths, `..`, missing
sources, duplicate targets, and overlapping parent/child targets.
## Target rules
- A string source receives the normal leading-dot target mapping.
- Use `{ source, target }` for paths that must not receive a dot prefix.
- One canonical source may feed multiple explicit targets.
- Do not create links inside another managed directory link.
## Resource behavior
- The task uses strict resource processing.
- `SymlinkResource` owns platform-specific creation.
- Correct links are already converged; wrong links are repaired only when safe.
- Uninstall materializes managed links into real files/directories rather than
deleting their content.
- Never overwrite an existing non-link target during removal.
## Add a symlink
1. Add the real source under `symlinks/`.
2. Add it to the correct `conf/symlinks.toml` section.
3. Add config-drift coverage where needed.
Use `windows-specific-patterns` for capability/junction behavior. Use the TOML
and dry-run coverage in [Testing](../../../docs/TESTING.md#choosing-coverage).
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Playbook for creating and editing uCoz landing pages via MCP tools (`templates_tool`, `ftp_tool`, `modules_tool`). Use for tasks such as: "build a landing page", "update the homepage as a landing page", "create a promo page on the homepage", "add a lead form / menu / SEO to the homepage". Homepage: `page_list`, `page_get`; first publish — `page_update` with full `page_tmpl`; HTML edits after generation — `patch_template` (module_id=2, template_id=1), not `update_template`. Activate the mail f...
Interact with the Paperclip control plane API to manage tasks, coordinate with other agents, and follow company governance. Use when you need to check assignments, update task status, delegate work, post comments, set up or manage routines (recurring scheduled tasks), or call any Paperclip API endpoint. Do NOT use for the actual domain work itself (writing code, research, etc.) — only for Paperclip coordination.
Digital Audio Workstation usage, music composition, interactive music systems, and game audio implementation for immersive soundscapes.
Instantly.ai cold email outreach API - manage campaigns, leads, accounts, and analytics. Use for cold email automation, lead management, campaign creation/monitoring, and email account warmup.
Discover the pull requests this Paperclip instance opened (never community contributions), report what each is for and how confident we are that it is merge-ready, and automatically drive the non-ready ones back to green with /prepare-paperclip-pr — without ever merging.
