AGENT SKILL

distribute-skill-to-all-agents

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

License 许可
MIT
所属仓库
MHassan0000/Skills
最近更新
2026-08-07
Stars
★ 1
Forks
0

01 前言 Front Matter

name
distribute-skill-to-all-agents
risk
critical
tags
[ "skills", "distribution", "agents" ]
tools
[ "claude", "codex" ]
author
davidondrej
source
community
license
MIT
category
development
date_added
2026-07-07
description
Distribute a skill across configured agent skill folders while respecting local symlink layouts.
source_repo
davidondrej/skills
source_type
community
license_source
https://github.com/davidondrej/skills/blob/main/LICENSE

03 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

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):
    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):
    SKILL=<skill-name>
    cp -r ~/.agents/skills/$SKILL ~/.hermes/skills/
    
  4. 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 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.

04 同仓库更多 Skills

MHassan0000
MHassan0000/Skills

vercel-react-best-practices

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

★ 1
MHassan0000
MHassan0000/Skills

stop-slop

Remove AI writing patterns from prose. Use when drafting, editing, or reviewing text to eliminate predictable AI tells and produce more human-like writing.

★ 1
MHassan0000
MHassan0000/Skills

ogilvy-copywriting

Apply David Ogilvy's advertising principles when writing or reviewing copy, headlines, product descriptions, landing pages, ads, emails, or any persuasive text. Use when the goal is copy that sells, not copy that wins awards. Covers positioning, headlines, promises, brand voice, long-form copy, and visual logic. Source: How to Create Advertising That Sells (1972) + Ogilvy on Advertising.

★ 1
MHassan0000
MHassan0000/Skills

frontend-design

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.

★ 1
MHassan0000
MHassan0000/Skills

webapp-testing

Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

★ 1
MHassan0000
MHassan0000/Skills

web-artifacts-builder

Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.

★ 1