agentic-home-cli

All your skills should live in one place.

Coding harnesses scatter skills across ~/.claude, ~/.cursor, and other directories. This CLI brings them together in one shared folder and links each harness to it.

Get started

Requires macOS or Linux, Node.js 18+, Python 3.11+, and Git for merges.

npm install -g agentic-home-cli
agentic sync --dry-run  # preview without changing files
agentic sync            # import and link

Or preview with npx agentic-home-cli sync --dry-run.

Files live in ~/.agentic/skills/ and ~/.agentic/AGENTS.md. Choose another folder with agentic sync --root PATH; later commands remember it. Switching folders retains the old content.

Run agentic sync again to import new skills, merge changes, and repair missing links. Reload your coding tools afterward.

Supported tools

Only existing setups are linked.

| Tool | Skills | Shared instructions | | --- | --- | --- | | Claude Code | ~/.claude/skills | ~/.claude/CLAUDE.md | | Codex | ~/.agents/skills | ~/.codex/AGENTS.md | | Cursor | ~/.cursor/skills | Not supported | | Pi | ~/.pi/agent/skills | ~/.pi/agent/AGENTS.md |

Existing ~/.codex/skills entries are imported too. Skills need a regular SKILL.md file. Hidden catalogs, standalone Markdown skills, custom agent locations, and Cowork aren't managed. Cursor's global instructions stay in Settings.

Resolve conflicts

Matching content combines. Conflicting content needs your choice; no tool takes priority. Unaffected skills sync while conflicting originals stay in place.

agentic status
agentic resolve CONFLICT_ID --take claude
agentic continue

Or edit the reported working copy, then use --file PATH instead of --take claude. Stage edits before continuing. New or changed sources require another review. Remove conflict markers before staging.

Add --json for scripts or agents: no prompts; exit codes are 0 for success, 1 for errors, and 2 for conflicts or blocked files.

Before you sync

• Review skills before sharing them. The CLI doesn't execute their contents.
• Project files, credentials, and unrelated settings stay untouched.
• Deletions don't propagate. Missing files may be restored from the saved baseline.
• AGENTS.override.md in Codex or Pi blocks shared instructions until you reconcile it.
• Backups and conflict copies stay in <root>/.agentic/. Backups preserve content, ordinary permissions, and symlink text, but not extended metadata. Restoration is manual; there is no undo command or automatic pruning.
• Interrupted writes resume on the next mutating command. Recovery refuses newer edits; changes across directories aren't one atomic operation.

Troubleshooting and development

If Python isn't found, set AGENTIC_PYTHON to a Python 3.11+ executable. Check command -v agentic if another CLI uses that name.

From a checkout:

pipx install .
npm test
python3.12 -m unittest discover -s tests -v

Tests use temporary homes. Discovery paths follow tool documentation; loading in each application hasn't been tested end to end.