alexion
b7363ed7e1
Bring the declarative half of ~/.claude into modules/claude-code and apply
it when the Module is enabled: the global agent instructions (context =
./CLAUDE.md), the skills tree (skills = ./skills), the attention-bell hook,
and settings.json (model = opus plus the Stop/Notification/SessionStart
hook wiring).
Runtime state (projects, plugins, cache, history, sessions) and the
.credentials.json secret are left out, so login survives rebuilds and no
secret enters the repo. Verified against the built home-files that
~/.claude/{CLAUDE.md,settings.json,skills,hooks/attention-bell.sh} are
generated, the hook executable.
2.1 KiB
name, description, disable-model-invocation
| name | description | disable-model-invocation |
|---|---|---|
| setup-skills | Add relevant skills from the shared skills library to the current project. | true |
Adds opt-in, project-specific skills from ~/.claude/skills/library/ into
the current project's .claude/skills/, tracked in
.claude/skills-lock.yaml (see LOCKFILE.md for its schema).
Only ever adds — checking already-installed skills for updates is
update-skills's job, not this one's.
Steps
-
Read
.claude/skills-lock.yamlin the current project, if it exists. Note every skill name already listed — these are already installed and must not be re-proposed. -
List every skill under
~/.claude/skills/library/*/SKILL.mdand read each one'snameanddescription. -
Inspect the current project (file tree, manifests like
pyproject.toml/package.json, file extensions present, etc.) and judge which library skills — excluding ones already installed — seem relevant, the same way you'd reason about any unfamiliar codebase. Propose that shortlist to the user with your reasoning, one line per skill. If the user asks to see the full catalog instead, list every library skill (minus already-installed ones) with its description. -
Let the user confirm, adjust, or pick freely from the full list.
-
For each confirmed skill:
- If
.claude/skills/<name>/already exists in the project and is not in the lockfile, skip it and tell the user why (a same-named skill already lives there and isn't tracked — remove or rename it first if they want the library version). - Otherwise, copy
~/.claude/skills/library/<name>/to.claude/skills/<name>/in the project, run~/.claude/skills/setup-skills/hash-dir.sh .claude/skills/<name>, and append{name, hash: <output>}to.claude/skills-lock.yaml(create the file, an empty YAML list, if it doesn't exist yet).
- If
-
Report what was added and what was skipped, and why.
Done when every confirmed skill is either copied and recorded in the lockfile, or explicitly skipped with a stated reason.