setup-agent-skills
Skill0 starsChanged 15 days agoMITView on GitHub
Set up shared skills on this computer. Use when installing this repository's skills, linking them into Claude Code or Codex, or troubleshooting those links.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- ambroselittle/agent-skillstheir own version, first seen Oct 30, 2026
- clinton3141/skillstheir own version, first seen Oct 25, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- ambroselittle/agent-skills★ 0same name
- clinton3141/skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository5 other files it gives its agents.
- librenms-os-supportSkill
- repo-docsSkill
- repo-workflowSkill
- unslopSkill
- writing-for-agentsSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 32
If the user has explicitly requested replacing a destination, preserve the old item at a unique backup path outside the active skills …
- Distinctive: line 40
Use symbolic links. For a whole-directory link:
- Distinctive: line 52
Use directory junctions. In Command Prompt, for a whole-directory link:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Set up shared agent skills
Locate and inspect
- Find the repository root from the working directory or this skill's location. Confirm its
skills/directory and use the absolute path as the source. Work on the requested computer; if it is inaccessible, report the missing access before changing paths. - Discover immediate skill folders by their
SKILL.mdentry points. Exclude tool-managed folders such assynced/and.trash/. - Inspect both destination paths and their parents, including link targets and directory contents:
- Claude Code:
~/.claude/skills/ - Codex:
~/.agents/skills/
- Claude Code:
Continue when the source, skill inventory and state of each destination are known. Keep the tool configuration directories as real directories; link only their skills paths.
Choose links
Handle each destination independently:
| Destination state | Action |
Link to this repository's skills/ | Leave it in place |
| Absent | Create the parent and link the whole skills/ directory |
| Real directory | Preserve it and link each discovered skill folder into it |
| Link elsewhere | Preserve it and report its target; ask which setup is wanted if the session has not already specified it |
| File or unexpected item | Preserve it and report the conflict |
For individual skills, leave a link resolving to the intended source in place. Create a link only at an absent path; preserve and report any other name collision. Inspect dangling links as existing paths too.
If the user has explicitly requested replacing a destination, preserve the old item at a unique backup path outside the active skills directory, then create the requested link. Restore the backup if creation fails. Otherwise preserve existing user data in place.
Create links for the current platform
Substitute the discovered source path in these examples. Run commands only for destinations already established as absent.
macOS and Linux
Use symbolic links. For a whole-directory link:
mkdir -p "$HOME/.claude" "$HOME/.agents"
ln -s "/absolute/path/to/repository/skills" "$HOME/.claude/skills"
ln -s "/absolute/path/to/repository/skills" "$HOME/.agents/skills"For an existing real skills directory, link each missing skill folder with the same ln -s pattern, using skills/SKILL_NAME as both the source suffix and destination suffix.
Windows
Use directory junctions. In Command Prompt, for a whole-directory link:
if not exist "%USERPROFILE%\.claude" mkdir "%USERPROFILE%\.claude"
if not exist "%USERPROFILE%\.agents" mkdir "%USERPROFILE%\.agents"
mklink /J "%USERPROFILE%\.claude\skills" "C:\absolute\path\to\repository\skills"
mklink /J "%USERPROFILE%\.agents\skills" "C:\absolute\path\to\repository\skills"For an existing real skills directory, create a junction for each missing skill folder, using skills\SKILL_NAME as both the source suffix and destination suffix.
Verify and report
Resolve each whole-directory link or individual skill link and confirm every discovered skill's SKILL.md is readable through each tool's destination. Account for every skill and tool as linked, already correct or blocked by a named conflict.
Report the resulting paths, any backups and unresolved collisions. Suggest restarting the affected tool if it has not discovered the skills. A rerun with unchanged sources and destinations should make no changes.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.