---
name: sync-local-skills-to-github
description: Use the canonical skills repo at ~/code/skills as the shared source of truth for custom skills on both laptops.
---

# Shared Skills Sync

Use this when the user wants the same custom skills available to Hermes, Claude, Codex, Pi, and Agents on both laptops.

The canonical shared skills clone lives at ~/code/skills on both laptops.
The canonical remote repo is https://github.com/srijanshukla18/skills.

Core idea:
- the repo is the shared source of truth
- local agent skill folders are install targets first, and possible sources for new custom skills second
- keep the workflow simple and idiomatic
- avoid agent-specific special cases unless they are truly necessary
- when design choices add complexity, ask the user instead of assuming

Local roots to inspect:
- ~/.hermes/skills
- ~/.claude/skills
- ~/.codex/skills
- ~/.agents/skills
- ~/.pi/agent

What belongs in the canonical repo:
- user-authored custom skills
- locally modified shared skills that are meant to exist on both laptops

What does not belong in the canonical repo by default:
- bundled or packaged skill catalogs
- third-party upstream repos copied into local skill folders
- ambiguous skills when it is not clear whether they are custom or packaged

How to decide what is custom:
- use SKILL.md modification time as the primary signal
- sort skills by modification time within each local root
- look for obvious clusters and obvious time gaps
- treat the newer side of a clear gap as more likely to be user-authored
- prefer updating skills that already exist in the canonical repo
- if the pattern is ambiguous, ask the user instead of guessing

Default recurring workflow:
1. Pull the canonical repo at ~/code/skills.
2. Inspect the local skill roots on that machine.
3. Use modification times to separate likely custom skills from packaged catalogs.
4. Update shared skills that already exist in the canonical repo when the local copy is clearly newer.
5. Do not auto-publish ambiguous new local-only skills during cron runs.
6. Install the repo skills into every local agent root.
7. The install model should be symlink-based for all agent roots so the local copy points back to ~/code/skills.
8. Keep both laptops aligned by running the same workflow on both machines.
9. If a change was pushed from one laptop, the other laptop should pull and apply the same install step.

Rules for simplicity:
- prefer one install model across agents when possible
- prefer plain language workflow over helper scripts in this skill
- prefer small explicit decisions over hidden automation
- prefer reporting ambiguity over inventing more machinery

Cron behavior:
- if nothing changed, return exactly [SILENT]
- if shared skills changed, report only the changed skills and the push result
- if there is ambiguity or conflict, report that plainly

Important note:
- skills are shared through the skills repo, not through the Hermes bus
- the local canonical path is ~/code/skills on both laptops
- ask before making invasive or system-level changes