domains / families / agent-tooling / distribute-skill-to-all-agents

distribute-skill-to-all-agents

combined

Distribute global skills across Codex, Claude Code, Pi, Hermes, and Cursor. Use for "distribute this skill", "sync skills across agents", or after creating or updating a global skill. Distribute a skill across configured agent skill folders while respecting local symlink layouts.

When to use

Use when a skill should be made available across multiple local agent skill folders.
Use when the user asks to sync or distribute skill updates to other agents.

When not to use

**Project-specific skill:** use repo-local `./.claude/skills/`, `./.pi/agent/skills/`, etc.
**Single-agent edit** (e.g. Hermes-only): patch that file directly without propagating.
**Global removal:** confirm with the user first; deletion is destructive. Remove with `rm -rf` from `~/.agents/skills/` (covers Claude and Pi) `~/.hermes/skills/`, and the `~/.cursor/skills/` symlink.
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 is destructive. First show the exact skill directories
Adapted from `davidondrej/skills`; verify local paths, tools, credentials, and agent features before acting.
For commands, remote access, scheduling, browser automation, or file-changing workflows, get explicit user approval and confirm the target environment first.

Skill page

Conflict

The sickn33 copy is a mirror of the davidondrej procedure but it explicitly drops Cursor from the canonical set (4 locations vs 5), while the davidondrej copy adds Cursor-specific steps (per-skill symlink, never use skills-cursor, byte-count check across 5 paths). Crowning one would hide a real alternative: the davidondrej version is the more complete procedure, but the sickn33 version is a valid 4-agent variant for users without Cursor. The combined instruction preserves the 5-location workflow and flags the 4-vs-5 disagreement.