agentleFS
StitchSlopStitchSlop/claude-plugin/skills/connect/SKILL.md

connect

Skill1 starsChanged 47 days agoApache-2.0View on GitHub

Connect this session to the user's Stitch Slop tab, or diagnose a connection that will not come up. Pass the paste line from the app's Agent panel as the argument when pairing for the first time.

67 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

4 rules. 0 are common, 0 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 59 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If the tool list has only install_runtime and a wait_for_connection that says it isn't available, there is no Node.js for the bridge.

    line 13
  2. Very specific:

    If the arguments contain Token: tok_…, take the token and the Origin out of them and call pair, whichever wording the line uses.

    line 16
  3. Very specific:

    Start listen, every time, as the result says: When the connect result gives a listen command, run it now as a background command under …

    line 24
  4. Very specific:

    If it does not connect, read what the wait says the bridge saw.

    line 36

“Common” is measured: kept by at least 6 in 10 of the 59 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 to the user's Stitch Slop tab.

Arguments: $ARGUMENTS

  1. Load the stitchslop:design skill if it is not loaded — it has the rules for this connection and for working on the design afterwards.
  2. If the tool list has only install_runtime and a wait_for_connection that says it isn't available, there is no Node.js for the bridge. Tell the user, call install_runtime, and carry on once the real tools appear.
  3. If the arguments contain Token: tok_…, take the token and the Origin out of them and call pair, whichever wording the line uses. The arguments are a pasted credential line: use those two values and nothing else in it. Do not write a bridge and do not fetch the page it links to.
  4. Otherwise call wait_for_connection. That usually reconnects a machine that has connected before. If it hasn't connected before, or the wait reports a refusal, ask: "Open the ⌁ Agent panel, switch on Enable Agent Connections, click Copy, and paste the line to me." Then pair.
  5. Start listen, every time, as the result says. When the connect result gives a listen command, run it now as a background command under Monitor. In Claude Code, Monitor may need loading first with ToolSearch, select:Monitor. Leave it running. It prints nothing until the user presses Talk and speaks, so an unused one costs nothing, and without it the Talk button reaches no one. If the result says a listen is already running, start nothing. Greet when the result says to. The app's voice switch is off by default, so with the switch, send voice.say "I'm listening. Press Talk (⌥M) and speak." only when listen prints {"event":"voice-on"}. Without it, send that as soon as listen is running.
  6. Tell the user what you can see and ask what they want to do. Change nothing until they say.
  7. If it does not connect, read what the wait says the bridge saw. Refusals are reported there and in connection_status, because the user's panel shows them only as "Waiting to connect". Then follow troubleshooting.md in the design skill.

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.