5 ms·

Have your agent make a plugin marketplace -- mine is here (feel free to crib): https://github.com/photostructure/coding-skills https://github.com/photostructure

Have your agent make a plugin marketplace -- mine is here (feel free to crib): https://github.com/photostructure/coding-skills https://github.com/photostructure/coding-skills Be sure to increment unofficial plugin versions when you make edits: codex's auto-update works reasonably well, claude not so much, but when asked, both can fix their own config. And like others have said, imho the skills that are incanted as macros are much more reliably useful. I use my technical project plan skill suite in 90% of my sessions via direct reference, and the stage -> cross-model second-opinion review is how I land all my commits.

threecheese 9d ago
Codex and Claude Code support plugin symlinks for local development; if you don’t mind keeping a local clone of your skills repo they can just use it. Claude needs a shim, as it wants to cache plugins; it’ll run a shell command (!) locally to get the plugin path. Codex supports this natively. Here’s the spec I used for my skills repo: https://claude.ai/public/artifacts/d37077a6-2cdd-4961-b504-b7b1c6c0711c https://claude.ai/public/artifacts/d37077a6-2cdd-4961-b504-b...