agentleFS
Sign inStart free
PatrickJaiinPatrickJaiin/claude-code-connect/skills/connect/SKILL.md

connect

Skill2 starsChanged 4 months agoMITView on GitHub

Connect this (parent) Claude Code session to another session that is in /listen mode - list listening sessions, read the child session's summary, send it prompts, and read its replies. Use when the user runs /connect.

  • Deletes or force-pushes

64 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use connect-apps, skill-share and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • ArogyaReddySkill

    connect-apps

    Connect Claude to external apps like Gmail, Slack, GitHub. Use this skill when the user wants to send emails, create issues, post messages, or take actions in external services.

    Also in 19 projects that use this

  • ArogyaReddySkill

    skill-share

    A skill that creates new Claude skills and automatically shares them on Slack using Rube for seamless team collaboration and skill discovery.

    Also in 17 projects that use this

  • ComposioHQSkill

    agent-deep-links

    Build, validate, and troubleshoot deep links for Codex, Cursor, VS Code, Visual Studio, and similar tools. Use when users ask for clickable links (especially in Slack) that open threads, files, folders, or app settings.

    Also in 3 projects that use this

  • ComposioHQSkill

    helium-mcp

    Search real-time news with bias scoring, get live stock/ETF/crypto data with AI analysis, ML options pricing, balanced news synthesis, and meme search via the Helium MCP server.

    Also in 3 projects that use this

  • trendinuxSkill

    twitter-algorithm-optimizer

    Analyze and optimize tweets for maximum reach using Twitter's open-source algorithm insights. Rewrite and edit user tweets to improve engagement and visibility based on how the recommendation system ranks content.

    Also in 12 projects that use this

  • LangChainSkill

    langsmith-fetch

    Fetches LangSmith traces for debugging agent behavior. Use when troubleshooting agent issues, reviewing conversation history, or investigating tool calls.

    Also in 18 projects that use this

  • +1 more from ComposioHQ
  • +5 more from ArogyaReddy

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 56 edited versions we read keep these.

  • 2

    Distinctive

    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:

    When the user asks you to send something to the child (e.g.

    line 18
  2. Distinctive:

    Write the prompt to a temp file (use the scratchpad dir), phrased as a clear standalone instruction — the child has its own context but …

    line 20
  3. Very specific:

    If the user wants to stop the child's listen mode: touch ~/.claude/claude-connect/sessions/<name>/stop.

    line 31

“Common” is measured: kept by at least 6 in 10 of the 56 edited versions of this file we could read. “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

Connect — attach to a listening child session

Drive another Claude Code session that ran /listen. Communication is via files under ~/.claude/claude-connect/sessions/<name>/. All scripts referenced below live in this skill's scripts/ directory.

Finding and attaching

  • /connect with no arguments → run bash <skill-dir>/scripts/list.sh, show the user each session's name, status (LISTENING / WORKING / STALE), working directory, and summary preview, then ask which to attach to. If exactly one is LISTENING, suggest it.
  • /connect <name> (or after the user picks) → read ~/.claude/claude-connect/sessions/<name>/summary.md and meta.json, present the child's summary to the user, and remember <name> as the connected session for the rest of this conversation. Warn (but still attach) if the session looks STALE.
  • /connect <name> <prompt...> → attach as above, then immediately send the rest of the arguments as the first prompt.

Sending a prompt and reading the reply

When the user asks you to send something to the child (e.g. "ask it to run the tests", "tell it to refactor X"):

  1. Write the prompt to a temp file (use the scratchpad dir), phrased as a clear standalone instruction — the child has its own context but none of this conversation's.
  2. NNN=$(bash <skill-dir>/scripts/send.sh <name> <prompt-file>) — prints the sequence number.
  3. bash <skill-dir>/scripts/await.sh <name> $NNN with the Bash timeout parameter set to 600000. It prints one of:
    • === REPLY NNN === + body → show the child's reply to the user (quote it substantially, don't over-compress; make clear it's the child speaking).
    • === TIMEOUT (state: working) === → the child is still working; run await.sh again. Keep re-running while state is working unless the user interrupts.
    • === CHILD NOT LISTENING === → the child session's heartbeat went stale (its user may have interrupted it or closed the session). Tell the user; the prompt file stays queued and the child will pick it up if /listen is resumed there.

Multiple exchanges just repeat this — sequence numbers advance automatically.

Disconnecting

If the user wants to stop the child's listen mode: touch ~/.claude/claude-connect/sessions/<name>/stop. To merely detach while leaving the child listening, just stop sending prompts. To clean up a dead session's files: rm -rf ~/.claude/claude-connect/sessions/<name>.

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.

Check your setup, free