How do I install the Distribute Skill To All Agents skill?

Run npx skillmds add solizardking/distribute-skill-to-all-agents in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Distribute Skill To All Agents safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Distribute Skill To All Agents?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Distribute Skill To All Agents free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Distribute Skill To All Agents?

Solizardking (@solizardking) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Distribute Skill To All Agents by solizardking

Name: Distribute Skill To All Agents
Rating: 4.2 (5 reviews)
Author: Solizardking

Distribute Skill To All Agents

Distribute a skill across the 4 agent skill folders (Codex, Claude Code, Pi, Hermes) so all agents see it. Use when the user says "distribute this skill", "sync skills across agents", or after creating/updating a skill that should be global. Covers the symlink layout and the ~/.pi/agent/skills trap.

Solizardking b18126e 4.0 KB Updated Sep 9, 2026 0 repo stars

File contents

Distribute a Skill Across All Agents

The user has 4 agent skill locations on their machine. A skill must exist in each (or via symlink) to be discoverable by every agent.

The 4 Canonical Locations

Agent	Skills Folder	Notes
Codex / OpenAI Agents	`~/.agents/skills/`	Canonical — author skills here first
Claude Code	`~/.claude/skills/`	Symlink → `~/.agents/skills/` — writing to `.agents/skills` automatically covers Claude
Pi Agent	`~/.pi/agent/skills/`	Symlink → `~/.agents/skills/` — auto-covered. (Path is `/agent/` nested — NOT `~/.pi/skills/`)
Hermes Agent	`~/.hermes/skills/`	Independent copy — the only one needing a manual copy

Workflow

Author the skill in ~/.agents/skills/<skill-name>/SKILL.md (canonical). Follow effective-agent-skills SKILL.md guidance.
Verify the .claude symlink is intact (one-time check):
```
ls -la ~/.claude/skills
# Expect: ~/.claude/skills -> ~/.agents/skills
```
If it's a real directory instead of a symlink, the user has diverged copies — ask before touching.

Copy to .hermes only (.claude and .pi are symlinks — already covered):

SKILL=<skill-name>
cp -r ~/.agents/skills/$SKILL ~/.hermes/skills/

Verify all 4 locations show identical byte counts:
```
for p in ~/.agents/skills/$SKILL ~/.claude/skills/$SKILL ~/.pi/agent/skills/$SKILL ~/.hermes/skills/$SKILL; do
  echo "$p: $(wc -c < $p/SKILL.md) bytes"
done
```
All four numbers must match. If .claude or .pi shows a different byte count, that symlink is broken — investigate before proceeding.

Updating an Existing Distributed Skill

Same flow — re-copy from ~/.agents/skills/ to .hermes/skills/. The .claude and .pi symlinks update automatically. cp -r overwrites by default; use rsync -a --delete if the skill folder has nested files that may have been removed:

rsync -a --delete ~/.agents/skills/$SKILL/ ~/.hermes/skills/$SKILL/

Pitfalls

~/.pi/skills/ is the wrong location. Pi Agent loads from ~/.pi/agent/skills/ only. A skill placed in ~/.pi/skills/ is invisible. If you find skills already there, they're orphans — confirm with the user before deleting.
~/.claude/skills is a symlink, not a folder. cp -r ~/.agents/skills/foo ~/.claude/skills/ will error with "are identical". Skip the explicit Claude copy.
Project-local skills exist too — ./.pi/agent/skills/ (or .pi/skills/) inside a repo overrides the global one on collision (later-discovered wins). This skill only handles GLOBAL distribution.
.pi/agent/skills is a symlink → .agents/skills. Don't cp into it (errors "are identical"); it auto-syncs. Only .hermes/skills is an independent copy — don't unilaterally consolidate Hermes into a symlink unless the user asks.
Hermes snapshots skills at session start. A newly-distributed skill won't appear inside a running Hermes session until restart (it works fine for future sessions and for the other 3 agents immediately).
Filename casing matters on case-sensitive volumes. SKILL.md must be uppercase.

When NOT to Use This Skill

Skill is project-specific → put it in ./.claude/skills/, ./.pi/agent/skills/, etc. inside the repo, not globally.
Editing one agent's skill only (e.g. a Hermes-only workflow) → patch that file directly, don't propagate.
Removing a skill globally → rm -rf from ~/.agents/skills/ (covers .claude + .pi symlinks) and from ~/.hermes/skills/ (and confirm with the user first; deletion is destructive).

---name: distribute-skill-to-all-agentsdescription: Distribute a skill across the 4 agent skill folders (Codex, Claude Code, Pi, Hermes) so all agents see it. Use when the user says "distribute this skill", "sync skills across agents", or after creating/updating a skill that should be global. Covers the symlink layout and the ~/.pi/agent/skills trap.--- # Distribute a Skill Across All Agents The user has 4 agent skill locations on their machine. A skill must exist in each (or via symlink) to be discoverable by every agent. ## The 4 Canonical Locations | Agent | Skills Folder | Notes | |---|---|---| | Codex / OpenAI Agents | `~/.agents/skills/` | **Canonical** — author skills here first | | Claude Code | `~/.claude/skills/` | **Symlink → `~/.agents/skills/`** — writing to `.agents/skills` automatically covers Claude | | Pi Agent | `~/.pi/agent/skills/` | **Symlink → `~/.agents/skills/`** — auto-covered. (Path is `/agent/` nested — NOT `~/.pi/skills/`) | | Hermes Agent | `~/.hermes/skills/` | Independent copy — the only one needing a manual copy | ## Workflow 1. **Author the skill in `~/.agents/skills/<skill-name>/SKILL.md`** (canonical). Follow `effective-agent-skills` SKILL.md guidance. 2. **Verify the `.claude` symlink is intact** (one-time check): ```bash ls -la ~/.claude/skills # Expect: ~/.claude/skills -> ~/.agents/skills ``` If it's a real directory instead of a symlink, the user has diverged copies — ask before touching. 3. **Copy to `.hermes` only** (`.claude` and `.pi` are symlinks — already covered): ```bash SKILL=<skill-name> cp -r ~/.agents/skills/$SKILL ~/.hermes/skills/ ``` 4. **Verify all 4 locations** show identical byte counts: ```bash for p in ~/.agents/skills/$SKILL ~/.claude/skills/$SKILL ~/.pi/agent/skills/$SKILL ~/.hermes/skills/$SKILL; do echo "$p: $(wc -c < $p/SKILL.md) bytes" done ``` All four numbers must match. If `.claude` or `.pi` shows a different byte count, that symlink is broken — investigate before proceeding. ## Updating an Existing Distributed Skill Same flow — re-copy from `~/.agents/skills/` to `.hermes/skills/`. The `.claude` and `.pi` symlinks update automatically. `cp -r` overwrites by default; use `rsync -a --delete` if the skill folder has nested files that may have been removed: ```bash rsync -a --delete ~/.agents/skills/$SKILL/ ~/.hermes/skills/$SKILL/ ``` ## Pitfalls - **`~/.pi/skills/` is the wrong location.** Pi Agent loads from `~/.pi/agent/skills/` only. A skill placed in `~/.pi/skills/` is invisible. If you find skills already there, they're orphans — confirm with the user before deleting. - **`~/.claude/skills` is a symlink, not a folder.** `cp -r ~/.agents/skills/foo ~/.claude/skills/` will error with "are identical". Skip the explicit Claude copy. - **Project-local skills exist too** — `./.pi/agent/skills/` (or `.pi/skills/`) inside a repo overrides the global one on collision (later-discovered wins). This skill only handles GLOBAL distribution. - **`.pi/agent/skills` is a symlink → `.agents/skills`.** Don't `cp` into it (errors "are identical"); it auto-syncs. Only `.hermes/skills` is an independent copy — don't unilaterally consolidate Hermes into a symlink unless the user asks. - **Hermes snapshots skills at session start.** A newly-distributed skill won't appear inside a running Hermes session until restart (it works fine for future sessions and for the other 3 agents immediately). - **Filename casing matters on case-sensitive volumes.** `SKILL.md` must be uppercase. ## When NOT to Use This Skill - Skill is project-specific → put it in `./.claude/skills/`, `./.pi/agent/skills/`, etc. inside the repo, not globally. - Editing one agent's skill only (e.g. a Hermes-only workflow) → patch that file directly, don't propagate. - Removing a skill globally → `rm -rf` from `~/.agents/skills/` (covers `.claude` + `.pi` symlinks) and from `~/.hermes/skills/` (and confirm with the user first; deletion is destructive).

Frequently asked questions