switch-login
Skill2 starsChanged 20 days agoMITView on GitHub
Move this Claude Code session to the other Claude account, leaving other sessions alone. Use only when the user runs /switch-login.
In this repository15 other files it gives its agents.
- global/CLAUDE.mdCLAUDE.md
- black-octoberSkill
- branch-cascadeSkill
- build-orderSkill
- full-review-auditSkill
- meta-improveSkill
- newSkill
- pr-monitorSkill
- publish-mobile-appSkill
- remindSkill
- reopen-prSkill
- research-spikeSkill
- setup-switch-loginSkill
- skill-syncSkill
- splice-youtube-quotesSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Run this and nothing else, then end your turn with one short line:
- Very specific: line 31
If the session was not started through the shell wrapper (claude-login.sh, sourced from ~/.bashrc or ~/.zshrc), the script resumes it in a …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Switch login
Run this and nothing else, then end your turn with one short line:
bash ~/.claude/skills/switch-login/scripts/switch.sh [rc|no-rc]Pass rc when the user asks for Remote Control (/rc) after the switch, and no-rc
when they ask for it off. With no argument, the resumed session gets Remote Control
when this one has it on, so a user on the Claude app keeps access.
The resumed session keeps its conversation name, or gets <machine> - <project>
(for example PC - Aiur) from the new skill's scripts/convo-name.sh when it had none.
It restarts this session in the same pane on the other account (claude =
default profile; claude2 = the profile in $CLAUDE_LOGIN2_DIR; transcripts
are shared), with the conversation resumed. Other panes are not affected. An
unfinished /goal is restored by the resume, and the resumed session is started
with a message to keep working toward it. When
CLAUDE_LOGIN2_NAME is set, claude-$CLAUDE_LOGIN2_NAME is a named command for
the same second profile; this machine-local variable is the source of truth for
the account name.
If the session was not started through the shell wrapper (claude-login.sh, sourced
from ~/.bashrc or ~/.zshrc), the script resumes it in a new tmux session on the
other account with Remote Control on (this needs the new skill and tmux), and this
pane's session stops. Tell the user to pick it up in the Claude app. If it prints a
command instead, show that command in a code block and tell the user to exit and run it.
Setup: run /setup-switch-login, or scripts/setup.sh. See README.md in this directory.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.