| name | claude-code-install |
| description | A three-part Claude Code setup skill with subskills for installation, skip-login configuration, and custom API-key launcher setup. Use when the user wants Claude Code installed or configured on the current host, with instructions adapted to the actual operating system and runtime environment. |
Claude Code Install
Manual invocation
Invoke this skill explicitly by name ($claude-code-install) because it modifies the local host environment.
Core operating rules
-
Detect the host OS first and choose commands accordingly.
-
On Windows, prefer the PowerShell helpers in scripts/*.ps1; if the user needs a double-clickable entrypoint, use the matching scripts/*.bat wrapper.
-
On Linux or macOS, prefer the POSIX shell helpers in scripts/*.sh.
-
Do not mix command styles across OS families.
-
If the OS is unclear from context, check it before acting.
-
Treat the scripts in scripts/ as optional accelerators and reference implementations, not the only path.
-
Before running a helper script, inspect the actual environment: available shell, available package managers, PATH layout, permission constraints, and existing Claude configuration.
-
If a helper script works in the current environment, use it.
-
If a helper script fails, do not stop at the script failure. Read the relevant subskill guide under references/, infer the required actions, and execute an environment-appropriate plan manually.
Subskills
This skill has exactly three subskills.
-
installation
Install the Claude Code CLI in the current environment.
Primary guide: references/installation.md
Optional helpers: scripts/install-comp.sh, scripts/install-comp.ps1, scripts/install-comp.bat
-
skip-login-config
Configure the host so Claude Code skips first-run onboarding/login locally.
Primary guide: references/skip-login-config.md
Optional helpers: scripts/config-skip-login.sh, scripts/config-skip-login.ps1, scripts/config-skip-login.bat
-
add-custom-api-key
Create a custom launcher or shell/profile function that injects an Anthropic-compatible API key and optional base URL/model overrides.
Primary guide: references/add-custom-api-key.md
Optional helpers: scripts/config-custom-api-key.sh, scripts/config-custom-api-key.ps1, scripts/config-custom-api-key.bat
Known provider registry: references/known-providers.json
Subskill selection
- If the user wants Claude Code installed, use
installation.
- If Claude is already installed but the user wants to bypass onboarding or login prompts on this host, use
skip-login-config.
- If the user wants a wrapper such as
claude-kimi, a custom base URL, a known provider name such as yunwu-global, or a custom API key, use add-custom-api-key.
- If the user wants a complete setup, run the subskills in this order:
installation, then skip-login-config, then add-custom-api-key.
How to execute each subskill
For each subskill:
- Read the corresponding file in
references/ first.
- Detect the OS and shell family.
- Check which runtime tools are actually available.
- Prefer the documented manual steps from the reference guide.
- Use a helper script from
scripts/ only if it matches the environment and clearly reduces work.
- If the helper script fails, continue by applying the guide manually instead of retrying blindly.
- Verify the result with the verification section from the corresponding reference guide.
Example prompts
- "Use the Claude Code install skill to install Claude Code on this machine."
- "Use the skip-login subskill so Claude no longer shows onboarding on this host."
- "Use the custom API key subskill to make a
claude-yunwu launcher that reads the key from an environment variable and targets yunwu-global."
- "Set up Claude Code fully, and adapt the steps if the bundled scripts do not work in this environment."
Resources
- Installation guide:
references/installation.md
- Skip-login guide:
references/skip-login-config.md
- Custom API-key guide:
references/add-custom-api-key.md
- Known provider registry:
references/known-providers.json
- Helper scripts:
scripts/