claude-switch-models-setup
Isolates profiles for multi-provider setup and switching models in separate terminal windows (Kimi, MiniMax, DeepSeek, GLM, StepFun, Anthropic).
Install / Use
npx skills add daymade/claude-code-skills --skill claude-switch-models-setupInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Our assessment of claude-switch-models-setup
claude-switch-models-setup scores 84/100 on our quality scale, 2901st of 4,700 Development & Engineering skills we index.
Its SKILL.md is 40 KB long, well organised into 25 sections with 9 code examples: long enough that it reads more like full documentation than a focused instruction file, which agents can find harder to follow.
With 1,426 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so claude-switch-models-setup is actively maintained.
- Our last check on 2026-11-06 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
ReviewOur scan of the whole file found 1 pattern worth reviewing before you install claude-switch-models-setup. An AI review judged it risky: The skill file includes an example alias `alias cssp='claude-profile step-pay --dangerously-skip-permissions'`, instructing the agent to launch a profile with permission prompts disabled.
- mediumDisables the agent's permission promptsline 216
`alias cssp='claude-profile step-pay --dangerously-skip-permissions'` —
AI review: risky
- The skill file includes an example alias `alias cssp='claude-profile step-pay --dangerously-skip-permissions'`, instructing the agent to launch a profile with permission prompts disabled.
- Disabling permission prompts (--dangerously-skip-permissions) is explicitly defined as risky behavior because it weakens the agent's safeguards.
- The rest of the file is a legitimate multi-provider Claude Code profile setup guide, with no evidence of credential theft, destructive commands, or hidden actions.
AI review by kimi-k2.7-code on 2026-10-03. Automated pattern scan on 2026-10-03. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
claude-switch-models-setup compared with similar skills
All 4 of these similar skills score higher than claude-switch-models-setup; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| claude-switch-models-setup (this skill)by daymade | 84 | 1.4k | 53d ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| Agent-Reachby Panniantong | 100 | 112.3k | 9d ago | CLAUDE.md |
| rufloby ruvnet | 100 | 81.9k | today | CLAUDE.md |
| headroomby headroomlabs-ai | 100 | 79.8k | today | CLAUDE.md |
Frequently asked questions
- How do I install claude-switch-models-setup?
- Run
npx skills add daymade/claude-code-skills --skill claude-switch-models-setup. The install tabs above show the steps for each supported agent. - Which AI agents does claude-switch-models-setup work with?
- It is written for Claude Code, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is claude-switch-models-setup safe to use?
- Our scan of the whole file found 1 pattern worth reviewing before you install claude-switch-models-setup. An AI review judged it risky: The skill file includes an example alias
alias cssp='claude-profile step-pay --dangerously-skip-permissions', instructing the agent to launch a profile with permission prompts disabled. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand. - Is claude-switch-models-setup still maintained?
- The repository was last updated about 2 months ago, so claude-switch-models-setup is actively maintained.
Skill content
View source on GitHubname: claude-switch-models-setup disable-model-invocation: true description: >- Sets up and maintains isolated Claude Code CLI profiles to run Kimi, MiniMax, DeepSeek, GLM, StepFun or Anthropic in separate terminal windows. Use for multi-provider setup, switching models, csk/csd/csg aliases, CLAUDE_CONFIG_DIR, or ~/.claude-profiles. Owns profile-drift troubleshooting (missing skills/hooks, symlink drift, settings drift) and context-window setup ([1m] marker vs CLAUDE_CODE_MAX_CONTEXT_TOKENS).
Claude Code Profiles and Local Skill Activation
Overview
This skill creates an isolated-but-shared profile system for Claude Code CLI. Each profile gets its own .claude.json state file (provider credentials and session history) while sharing skills, projects, hook scripts, agents, and installed plugin state across all profiles — and converging each profile's settings.json (hook registration, marketplaces, env feature flags, permissions, preferences) plus the behavior slice of its .claude.json (e.g. workflowSizeGuideline) from the default profile, so the only intended difference between profiles is the model/provider.
The result: you can open one terminal with Kimi, another with DeepSeek, another with Anthropic — each running as a fully independent Claude Code process, without configuration bleed.
How It Works
CLAUDE_CONFIG_DIRtells Claude Code CLI which directory to use as its config root.- Each profile lives in
~/.claude-profiles/<name>/with an isolated.claude.json. - Content directories (
skills/,projects/,hooks/,agents/,settings/) are symlinked back to the main~/.claude/directory so you only maintain one copy. Note this shares hook scripts, not hook registration — registration lives in each profile's ownsettings.json(next bullet). - Config layer —
settings.json: each profile has its ownsettings.json(Claude Code treats it as config-dir-local), so everything stored there — hook registration,extraKnownMarketplaces,enabledPlugins,envfeature flags,permissions, behavior preferences — silently drifts the moment it changes in the default profile (measured 2026-07-18: 9/9 real profiles had zero hook registrations).sync-profile-settings.pyis the converger: registered as a SessionStart hook, it copies every key from the default profile'ssettings.jsoninto every profile's, except identity keys (top-levelmodelandadvisorModel— the latter is Anthropic-model routing a third-party endpoint can't serve; and env vars that carry provider routing or Anthropic-native isolation —ANTHROPIC_*,CLAUDE_CODE_SUBAGENT_MODEL,ENABLE_TOOL_SEARCH,DISABLE_GROWTHBOOK/TELEMETRY/AUTOUPDATER— which the provider settings file deliberately sets differently). Withinenv, convergence is two-way for non-identity keys: main's keys overwrite the profile's, and a non-identity key main no longer carries is deleted from the profile and reported (identity keys are exempt — main never carries them, so their absence is not deletion evidence; landed v3.60.1). Profile-only top-level keys are preserved; nested collections inside a key main also has (e.g.permissions.allow,enabledPlugins) converge wholesale to main's value, and any profile-only nested entries dropped that way are listed (count on write, detail under--check) so the loss is visible rather than silent. This is what makes "everything except the model works in every profile" actually hold.- Scope is every profile, in every invocation. No argument-free,
--all, or--checkrun ever covers a subset: all of~/.claude-profiles/*plus$CLAUDE_CONFIG_DIR, every time. A run prints one line per profile it actually changed and nothing when there is no drift — so drift shows up in the session-start output instead of hiding, and a silent session start means converged. A$CLAUDE_CONFIG_DIRthat is unset, empty, or not a profile directory is skipped, never created. - Exit codes: the argument-free run exits 0 unconditionally — it is a session-start hook and never blocks a session, including when a main file is corrupt (it warns, converges nothing, and exits 0, because a corrupt main reads as empty and converging toward empty would strip hooks from every profile).
--checkexits 1 on drift and 2 on a corrupt main file or a profile it could not read;--allwrites and exits 2 on those same two failures — the difference between them is that--checkwrites nothing, not which failures return 2.--check --allis the same audit as--check. One unreadable profile is reported and skipped — it never cancels convergence for the others.
- Scope is every profile, in every invocation. No argument-free,
- State layer —
.claude.jsonbehavior keys:settings.jsonis not the only per-profile config file. Claude Code also keeps a per-profile state file (the main profile's is~/.claude.json; each third-party profile's is<profile>/.claude.json— asymmetric paths, verified on disk), and a few behavior settings live only there (workflowSizeGuideline, notification/UI preferences). On 2026-08-17workflowSizeGuideline: smallexisted only on the main profile and 10/11 third-party profiles had no copy — a Kimi session fanned one Dynamic Workflow out to 30+ agents with no size guidance in its system prompt. The same converger therefore also syncs an allowlist of behavior keys into each profile's.claude.json. The safety mechanism is a three-way classifier in the script, not a hand-maintained key list: allowlisted behavior keys sync; state/cache/counter/migration/credential keys (matched by name patterns) are never touched; anything unknown-and-different is reported — one line per drifted key per run, until a human classifies it (the tripwire that surfaces the next behavior key the day it appears). Writes are backup + atomic-replace; measured safe against a live harness rewriting the file (a marker key survived 30+ minutes of an active session). Applies next session — the harness reads this file at startup. - Exception —
plugins/: marketplace content and install state are shared, but each profile keeps its ownknown_marketplaces.json. Claude validates a marketplace'sinstallLocationwithpath.resolve()(which does NOT resolve symlinks), so a single shared file would make every non-writing profile report "corrupted installLocation".claude-plugins-sync.pybuilds and maintains this per-profile structure. claude-plugins-sync.pyalso mirrorsenabledPluginsfrom the default~/.claude/settings.jsoninto each profile'ssettings.json(sharing cache files is not enough; Claude Code treats "enabled" state as config-dir-local). It runs at profile launch and reactively — the LaunchAgent in the next bullet re-runs it on every write to the default profile'ssettings.json, soclaude plugin enable/disable --scope usertypically propagates to every profile within seconds without a relaunch (verified 2026-08-22). The mirror adopts first: enabledPlugins keys that exist only in some profile's settings.json (the wayclaude plugin installwrites them) are written back into the default profile before mirroring — consistent values only; cross-profile conflicts stay per-profile behind a standing warning instead of being silently overwritten (added 2026-09-03, after adopt-less mirroring was confirmed as the mechanical root cause of recurring skill-visibility losses). The SessionStart converger above covers the same key as part of its whole-settings sync;claude-plugins-sync.pyremains the owner of the per-profileknown_marketplaces.jsonstructure.skill-install-audit.pyreconciles the registry / installed / enabled / Codex-manifest /~/.agents/skillslayers read-only, plus the daemon's pinned runtime version and whether the checkouts it judged everything against are themselves behind.prune-source-sync-backups.pyremoves only the.source-sync-backups/buckets git can reproduce; a bucket holding even one blob no repository has is reported and left alone.- Local source sync keeps approved source-backed routes aligned for each host. Before selecting or repairing entries, read the host-specific activation contract. It owns the manifest fields, marketplace expansion, Claude plugin/direct-link distinction, unresolved-name handling, collision safety, and legacy compatibility. Source registration alone does not choose activation policy; do not hand-create links or repurpose the manifest to manage third-party inventory.
- Sync scripts use a shared cross-process lock. This is required because users often open several provider windows from tmux or multiple terminals at once; concurrent launches must serialize marketplace/cache rewrites while still allowing all profiles to start.
- For the full local-source architecture, read
references/local-source-sync-architecture.mdbefore changing these scripts. - Provider routing is done via
~/.claude/settings/<name>.json, which setsANTHROPIC_MODEL,ANTHROPIC_BASE_URL, andANTHROPIC_AUTH_TOKENfor that window. That file is a full settings file rather than an env file, and it is the one layer the converger never touches —claude-profilelaunches withclaude --settings ~/.claude/settings/<name>.json, while the converger only ever writes<profile>/settings.json. So anything that has to be per-profile and has to survive every session start belongs here; put it in the profile's ownsettings.jsonand the next convergence takes it back. Measured 2026-09-15 onpermissions.deny: oneclaude -prun listed 50 tools with an empty--settingsfile and 48 with{"permissions":{"deny":["WebSearch","WebFetch"]}}, the two named tools being the difference. The cost of not knowing this is a detour: the session that worked it out had already forked the converger to add a per-profile exception before noticing that one key in the provider file did the same job with no code change. - Credentials ride in that same file, so anything scripting a profile has to pass
--settingsas well.CLAUDE_CONFIG_DIR=<profile> claude -p ...on its own answersNot logged in · Please run /login, because the token lives in the provider file and nothing else loads it. The message names login; the cause is the missing flag. - The converger has no single-profile mode: every invocation covers all of
~/.claude-profiles/*plus$CLAUDE_CONFIG_DIR, and no flag narrows that. To converge one profile on demand, pointCLAUDE_PROFILES_ROOTat a directory holding only it, or run--checkand read the per-profile lines. The default profile's own files are the source and are never written.
⚠️ Never run the converger against a synthetic main
Scope is every profile — all of ~/.claude-profiles/* plus $CLAUDE_CONFIG_DIR
— and the source of truth is CLAUDE_MAIN_CONFIG_DIR. Point that at a throwaway
directory while CLAUDE_PROFILES_ROOT or $CLAUDE_CONFIG_DIR still reaches a
real profile, and the run converges that real profile toward the synthetic
main: its whole hooks object is replaced by whatever the fake main holds, and
its env gains the fake main's keys. Every guard registered in that profile
stops firing. The output does name hooks among the keys it synced and, when
the overwrite drops profile-only entries, reports how many — but nothing in it
says guards stopped firing, so it reads as the converger doing its job. A
synthetic main is safe only when the profiles root and $CLAUDE_CONFIG_DIR are
synthetic and disposable too.
Before running it by hand, check both halves of the scope:
echo "MAIN=$CLAUDE_MAIN_CONFIG_DIR ROOT=$CLAUDE_PROFILES_ROOT ACTIVE=$CLAUDE_CONFIG_DIR"
An unset CLAUDE_PROFILES_ROOT is not a green light — it defaults to the
real ~/.claude-profiles, so every real profile converges. Stop unless both
CLAUDE_PROFILES_ROOT and $CLAUDE_CONFIG_DIR are synthetic a
Truncated for display — read the full file on GitHub.
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
Agent-Reach
112.3kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
ruflo
81.9k🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated
headroom
79.8kCompress tool outputs, logs, files, and RAG chunks before they reach the LLM. 20% fewer tokens for coding agents, 60-95% fewer tokens for JSON, same answers. Library, proxy, MCP server.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
