What problem does it solve? Publishing a skill once is easy, but keeping installed copies across multiple Hermes and Claude Code profiles in sync with the canonical repo is not — copies silently drift, installs fail with opaque resolution errors, and skills that appear published never actually load. This Skill documents the end-to-end workflow for authoring, publishing, and propagating skills via a GitHub tap so the repo stays the single source of truth. ## Core Features & Use Cases - Tap repo setup: Defines the exact skills/<name>/SKILL.md layout the GitHub provider expects, plus commands to create the repo, commit with explicit paths, and register the tap per profile. - Drift-free propagation: Recommends symlinking tap skills into ~/.claude/skills and ~/.hermes/skills instead of copying, so edits in the repo take effect immediately without re-installing. - Pitfall catalog: Documents known failure modes — git add -A being blocked, skills search not covering taps, and install failing with "Could not fetch from any source" — with manual copy workarounds. - Use Case: You maintain a monorepo of reusable skills and want every profile to load the latest version after each push, without re-running installs or discovering weeks later that a skill never propagated. ## Quick Start Ask the agent to publish a new skill to your GitHub tap repo and symlink it into your local Hermes and Claude Code profiles.
