Complete AI Training
Sign inBecome a member

Your job's AI kit

Get your AI kit

Tell us who you are and what you do. We show you your kit right away and email you the link: skills, prompts, AI agents, MCP servers and courses for your job.

500+ jobs ready, and we make a kit for any other job. No payment needed to look.

Share

Skill · Development

Distribute skill to all agents

Distribute a skill across configured agent skill folders while respecting local symlink layouts.

Agentic Awesome SkillsLicense: MITAdded Sep 5, 2026
IT & Software Development
Use it in my AI

How to use it

  1. Start your plan and connect your AI once
  2. Add the skill to your AI, one time only: press Copy skill and paste it into your AI's instructions: a project in ChatGPT, Claude or Grok, a Gem in Gemini, an agent in Microsoft 365 Copilot, or a rule in Cursor. It stays there for every new chat. In Kimi, paste it at the start of a new chat.
  3. Ask for the task in your own words, or say it directly:
Use the Distribute skill to all agents skill to help me with this.
SKILL.md

Distribute a Skill Across All Agents

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.

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

The 4 Canonical Locations

AgentSkills FolderNotes
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):

    3. ``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):

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

  4. Verify all 4 locations show identical byte counts:

    5. ``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:

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 is destructive. First show the exact skill directories

    • that would be removed, confirm with the user, then use the user's preferred safe deletion method for ~/.agents/skills/ and ~/.hermes/skills/.

Limitations

  • 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.

More development skills

All development skills

Prompts that go with Distribute skill to all agents

All prompts