One skill, four runtimes

EEIU sketch · 2026-05-24 · HEAT KB · 00-SYSTEMS/polyskill/

1 Same skill, four homes

before after Claude .md v3.1 Codex .md v2.8 Gemini .md v3.0 Hermes .md v2.4 bridge canonical .md v3.1 — sole truth ↑ Claude reads ↑ Codex reads ↑ Gemini reads ↑ Hermes reads

Same procedure used to be copy-pasted into four places, each drifting apart.

👉 One file. Four eyes. Zero drift.

2 Where the source lives

~/knowledge-base/.claude/skills/<name>.md the only file you edit ↓ symlinks ↓ ~/.claude/skills/...md Claude Code ~/.codex/skills/.../SKILL.md Codex app ~/.gemini/.../SKILL.md Antigravity MCP bridge Hermes

One canonical markdown file; symlinks (or an MCP bridge) point each runtime at it.

👉 Edit once, see it everywhere.

3 The bridge script

bootstrap-cross-runtime.sh <skill-name> ~/.claude/ skills + commands ~/.codex/ skills + dispatch ~/.gemini/ antigravity + slash command wrappers (so /your-skill resolves) existing files preserved · idempotent ~10 seconds per skill

One bash script writes all the symlinks and command wrappers — preserves real files.

👉 One command per skill. Or all at once.

4 Auto-bridge for new skills

you write new-skill.md watcher launchd · 10s bridge all 4 runtimes no command, no waiting

Drop a new skill file in the KB folder; launchd notices and bridges it in 10 seconds.

👉 Write. Wait 10 s. Use.

5 Heatie onboarding

1 min git pull install polyskill 1 min Codex marketplace 1 min bulk bootstrap 149 skills 10 s launchd watcher → auto from now ~ 3 minutes total

Five commands. Done in three minutes. Future skills bridge themselves.

👉 One time. Never again.
EEIU sketch · /image-sketch-html00-SYSTEMS/polyskill/