Has anyone else ended up maintaining the same AI skill in multiple places?
I use Claude Code, Codex, Cursor, Gemini CLI, Kimi, and several other AI tools.
Over time, I accumulated a huge collection of skills and workflows.
The annoying part wasn't creating them.
It was keeping them synchronized.
A skill would exist in one format for Claude Code, another for Cursor, another for Gemini, and so on.
Eventually, I got tired of duplicating everything and built an open-source project called AI Omni Skills.
The idea is to keep a single source of truth and generate the formats required by different AI tools.
Now I update a skill once and regenerate whatever structure a specific tool expects.
I'm curious:
How are you managing skills today?
Are you duplicating them across tools?
What integrations would you want to see?
Repo: https://github.com/moatazhamada/ai-omni-skills
Moataz Mohamed
Posted on • Originally published at linkedin.com
How I Stopped Duplicating AI Skills Across Claude Code, Cursor, Codex, Gemini CLI, and Other Tools
For further actions, you may consider blocking this person and/or reporting abuse
Top comments (1)
Shared skills across tools are going to matter more than tool loyalty. The real asset is the operating procedure: constraints, checks, examples, and stop conditions. Rewriting that for every IDE or CLI is pure drag.