skul add github.com/sjquant/ai-bundles core --agent codexPull a shared bundle into a project for the tool you use.
AI tooling CLI
skul lets teams reuse AI bundles across Claude Code, Cursor, OpenCode, Codex, GitHub Copilot, and Kiro.
Keep shared prompts, skills, agents, and root instructions in one bundle repo, apply them per project, and leave tool-local files out of Git.
Typical session
Start with one bundle repo, apply it where needed, and keep project-level AI setup consistent without copy-pasting folders.
skul add github.com/sjquant/ai-bundles core --agent codexPull a shared bundle into a project for the tool you use.
skul add core --agent codex --include skills/diagnoseInstall one bundle item when you only need a specific skill.
skul applyRe-apply the same bundle setup in linked worktrees without manual copying.
skul updateRefresh bundles when your team ships new prompts, skills, or agents.
Install an entire bundle, or pick only the skill, agent, command, or root instruction you need.
Ship the same AI setup to Claude Code, Cursor, OpenCode, Codex, GitHub Copilot, and Kiro from one source repo.
Keep local AI files out of Git while still giving every project the setup it needs.
Refresh shared prompts, skills, and agents without copy-pasting folders across repos.
Supported AI tools
Reuse the same bundle source across the tools your team already works in instead of rebuilding prompt folders for each one.
Share Claude Code skills, commands, and agents across repos without committing them.
Keep Cursor project setup consistent without maintaining a second copy of the same prompts.
Ship Codex skills and agents from the same source bundle you already use elsewhere.
Support OpenCode projects without inventing a separate packaging workflow.
Share Copilot skills, agents, and instructions while keeping repository policy files controlled.
Materialize Kiro skills, agents, and root instructions from the same reusable bundle source.
How it helps
`skul` is useful when AI setup needs to be shared across repos, tools, and teammates without turning every project into a prompt graveyard.
Keep reusable prompts, skills, and agents in one repo instead of scattering copies across projects.
Materialize the files each tool expects, or narrow installation to selected bundle items.
Re-apply or remove managed files predictably when shared AI setup changes.
Docs
Install first, try one bundle, then keep the command reference nearby when you are ready to wire skul into daily work.
Install the CLI and get your machine ready in a few minutes.
Install skulApply your first shared AI bundle and target the tools you actually use.
Read quick startKeep the full command surface nearby once skul becomes part of your daily workflow.
Browse commands