Cc switch claude provider
Skill kiakun-collab/kiakun-skills/skills/cc-switch-claude-provider
Kiakun 的 AI Agent Skills 集合(Claude Code / OpenClaw / 通用 SKILL.md):HTML→可编辑 PPTX、图片型 PPT 重构、GPT Image 2 出图、小红书/B站自动化、文件夹向量知识库、游戏 UI 与玩家互动设计等 10+ 技能。
npx -y skills add kiakun-collab/kiakun-skills --skill cc-switch-claude-providerAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Configure Claude Code through local CC Switch with a third-party Anthropic or Claude-compatible base URL and API key. Use when the user wants "just give base URL + key and make Claude Code usable", wants to switch Claude Code to a third-party provider without manual editing, or wants CC Switch provider creation, provider switching, and a real Claude Code smoke test automated.
SKILL.md
3.1 KB, as published. Nobody here has run it
CC Switch Claude Provider
Use this skill to wire a third-party Claude-compatible endpoint into local CC Switch, activate it for Claude Code, and verify that claude can actually answer.
Quick Start
Run the setup script from this skill directory with the user-provided base URL and API key:
python ".\scripts\configure_cc_switch_claude_provider.py" --base-url "<BASE_URL>" --api-key "<API_KEY>"
Use these optional flags when needed:
python ".\scripts\configure_cc_switch_claude_provider.py" `
--base-url "<BASE_URL>" `
--api-key "<API_KEY>" `
--name "<PROVIDER_NAME>" `
--model "<MODEL_ID>" `
--keep-v1
Workflow
- Collect the user's
base URLandAPI key. - Run the script.
- Read the result summary:
provider_id- normalized
base_url - chosen models
- whether
claudesmoke test passed
- If the script reports success, tell the user Claude Code is ready.
- If the script reports failure, relay the concrete error and next fallback it already attempted.
What The Script Does
- Find local
cc-switch.exeandclaude - Back up
<HOME>\.cc-switch\cc-switch.db - Normalize Claude-style endpoints; by default it strips a trailing
/v1 - Query
/v1/modelswhen available - Create or update a Claude provider in CC Switch
- Switch the current Claude provider to the new entry
- Sync
<HOME>\.claude\settings.json - Run a real
claude "Reply with ok only"smoke test - Auto-fallback across likely Claude model IDs if the first model is rejected
Default Behavior
- Default provider name: derived from the endpoint host
- Default provider id: stable slug derived from host
- Default model preference order:
anthropic/claude-sonnet-4.6claude-sonnet-4-6anthropic/claude-sonnet-4.5anthropic/claude-sonnet-4anthropic/claude-3.7-sonnet
- Default smoke-test prompt:
Reply with ok only
When To Override Defaults
- Pass
--keep-v1if the user explicitly says the full endpoint must keep/v1 - Pass
--modelif the provider only allows a specific model - Pass
--nameif the user wants a friendly provider label in CC Switch - Pass
--skip-claude-testonly when the user explicitly does not want a live test
Output Handling
On success, summarize:
- the active provider name
- the active base URL
- the selected primary model
- the smoke-test response
On failure, summarize:
- whether CC Switch write succeeded
- whether provider switch succeeded
- whether direct API probing succeeded
- the exact failing step
Script
- Main automation: scripts/configure_cc_switch_claude_provider.py