agentleFS
surasakchosurasakcho/claude-skills/launch-session/SKILL.md

launch-session

Skill0 starsChanged 5 months agoMITView on GitHub

Start a new detached tmux session, cd into a repo under ~/repos/, and launch Claude Code with a given model and remote-control name. Requires 4 parameters from the user — repo, model, tmux session name, and remote-control session name. Use when the user says "launch session", "start a claude session", "open a tmux claude session", or similar.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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
  1. Distinctive:

    Ask the user for any of these 4 parameters not already provided in the args:

    line 8
  2. Distinctive:

    After the command succeeds, tell the user:

    line 22
  3. Very specific:

    If the tmux session name is already taken (tmux has-session -t <tmux> exits 0), warn the user before proceeding — do not overwrite a live …

    line 29

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

launch-session

Ask the user for any of these 4 parameters not already provided in the args:

  1. repo — repo name under ~/repos/ (e.g. e-biz-factory)
  2. model — Claude model to use: sonnet, opus, haiku, or fable
  3. tmux — tmux session name to create (e.g. ebiz, gamelab)
  4. rc — remote-control session name that will appear on claude.ai (e.g. ebiz-main)

Once all four are confirmed, run exactly this bash command (substituting the four values):

tmux new-session -d -s "<tmux>" -c "$HOME/repos/<repo>" \
  "claude --model <model> --remote-control '<rc>'"

After the command succeeds, tell the user:

  • Attach command: tmux attach -t <tmux>
  • Remote-control: go to claude.ai/code → select session <rc>
  • Repo: ~/repos/<repo>
  • Model: <model>

If the tmux session name is already taken (tmux has-session -t <tmux> exits 0), warn the user before proceeding — do not overwrite a live session without explicit confirmation.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.