Skip to content

Use one skill in every coding project

At the end one skill, kept in Kaizendex, works in two coding projects, in both Claude Code and Codex, and an edit in one place shows everywhere.

You need: the desktop app on Windows, macOS or Linux.

A skill is a folder with a SKILL.md file (instructions) and any scripts it needs. It is the open format that Claude Code, Codex, OpenCode, Cursor and others read. See Skills.

One skill folder in Kaizendex is linked into two projects, in both the .claude/skills and .agents/skills folders.Skills / code-reviewSKILL.mdone copy, in KaizendexProject: shop-website.claude/skills · .agents/skillsProject: blender-tools.claude/skills · .agents/skillslinks
The projects hold links, not copies. There is one skill to keep up to date.
  1. Add a skill to the Skills collection: code-review, with its instructions in SKILL.md.

  2. In the skill’s Use in projects list, turn on shop-website and blender-tools.

  3. The desktop app puts a link to the skill folder in each project’s .claude/skills/ (for Claude Code) and .agents/skills/ (for Codex and others). On Windows it is a junction, which needs no admin rights. Elsewhere it is a symlink.

  4. Open Claude Code in shop-website and Codex in blender-tools. Both find code-review.

  5. Ask Claude Code to improve the skill. It edits the linked file, which is the same file in Kaizendex. The change is in your history and syncs to your other devices.

Good to know

  • Global skills: a global switch puts a skill in every project. Each skill’s description costs the AI some context on every turn, so the app warns you. Keep global skills few.
  • Skills from others (GitHub or the Library) stay on the version you took. An update shows a diff for each file and a safety scan first. Their scripts stay off, and outside any linked folder, until you approve them. By default, a skill never gives the AI new powers: it is only instructions. See AI safety settings.
  • Your own Kaizendex agents use the same skills. There is one skill system, not two.

Make it yours

  • Make a “Blender modeling” skill with its scripts/export_glb.py, and link it to every 3D project.
  • Publish a skill to the Library. See Share agents and skills.
  • Store other things your AI should know (people, decisions, notes) as collections too. See What your AI knows.