Menu

Individual skill

claude-switch-models-setup

0upvotes

Isolates profiles for multi-provider setup and switching models in separate terminal windows (Kimi, MiniMax, DeepSeek, GLM, StepFun, Anthropic). Use for provider switching, csk/csd/csg aliases, CLAUDE_CONFIG_DIR, ~/.claude-profiles, profile drift (missing skills/hooks, symlinks, settings), context-window setup ([1m], CLAUDE_CODE_MAX_CONTEXT_TOKENS), or reducing startup context from preloaded MCP tool schemas.

daymade-claude-code/claude-switch-models-setup/SKILL.md

Read pinned source

Source commit 7c4d326ddd94d504e00e241ba49498e95160afbe

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,522
Repository last updated
Nov 10, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# 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.

For reducing fixed startup context from preloaded MCP tool schemas, read
[references/mcp-startup-context.md](references/mcp-startup-context.md). It owns
same-mode measurement, active-profile discovery, provider compatibility checks,
reversible server suppression, and fresh-process acceptance.

## How It Works
Back to top