Init Agentic Skills

Init Agentic Skills

Initialize this agentic-skills checkout on the current machine by installing global core skills for both Claude and Codex. Active installs are repo-managed directories that expose the canonical SKILL.md and exclude archive/; pinned installs intentionally point at archive/<version>. Keep domain packs project-local; use /pack from the target project when packs are needed.

Workflow

1. Parse $ARGUMENTS:
   • No args, init, refresh, or sync: run scripts/init-agentic-skills.sh.
   • status: run scripts/init-agentic-skills.sh, then inspect ~/.claude/skills, ~/.codex/skills, and the root initializer summary.
   • --uninstall, uninstall, or remove: run scripts/init-agentic-skills.sh --uninstall only after confirming the user wants repo-managed global installs removed.
   • help, --help, or -h: run scripts/init-agentic-skills.sh --help.
2. Report the initializer command, the Claude and Codex skill directories, installed/skipped counts, and warnings about non-repo-managed collisions.
3. Explain pack access separately:
   • Do not install packs/* globally.
   • In the project that needs domain workflows, run /pack for guided setup or /pack install <pack-or-skill> for an explicit pack or individual pack skill.
   • If a project already has .agents/project.json, use /pack refresh after this global initialization to recreate local pack skill roots.
4. If the active session still cannot see a newly installed skill, tell the user to start a fresh Claude Code or Codex session.

Constraints

• Delegate global initialization to scripts/init-agentic-skills.sh; do not recreate install logic by hand.
• Do not overwrite real directories or files under ~/.claude/skills, ~/.codex/skills, .claude/skills, or .codex/skills.
• Treat packs as project-local capabilities managed by scripts/pack.sh through /pack.
• Stop and report exact errors if the launcher cannot resolve the repository root or if root init.sh fails.