agentleFS
Sign inStart free
MosoFinMosoFin/mosofin-mcp-plugin/skills/workspaces/SKILL.md

workspaces

Skill3 starsChanged 22 days agoMITView on GitHub

List, confirm, or switch the MosoFin workspace for this conversation (maps to the list_workspaces MCP tool). Use when the user asks which workspaces they have, wants to work in a specific workspace, or wants to switch or add workspaces mid-chat.

5 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions5 projects use a version of this.

    Word for word · 1

    1. MosoFin/mosofin-plugins★ 3100% same

    Edited · 0

    None found.

    Wrote their own version · 4

    1. langchain-ai/open-swe★ 11ksame name
    2. coder/skills★ 14same name
    3. wyattjoh/skills★ 3same name
    4. stacksyncdata/skills★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository8 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 1

    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 list_workspaces is not in this session's tool list, or a call returns Unknown tool (e.g.

    line 13
  2. Distinctive:

    Do not invent workspaces or data.

    line 18
  3. Very specific:

    Keep the user's request and follow /mosofin:connect (skills/connect/SKILL.md): it gives the one sign-in step for this host (Claude Code …

    line 20
  4. Very specific:

    Call list_workspaces with no arguments (discovery).

    line 28
  5. Very specific:

    After confirmation, continue with /mosofin:connections, /mosofin:list-tools, or /mosofin:query-workspace.

    line 48

“Common” is measured: kept by at least 6 in 10 of the 4 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

Workspaces — discover and confirm

Wraps the server's list_workspaces tool: the mandatory first gate before any MosoFin data or skill tool. Full spec: docs/mcp-tool-spec.md §3.1.

If MosoFin tools are missing

If list_workspaces is not in this session's tool list, or a call returns Unknown tool (e.g. mosofin.list_workspaces or codex_apps/mosofin.list_workspaces): the MosoFin connector is not connected or not enabled for this chat. That is not a data-source reconnect.

  • Do not invent workspaces or data.
  • Never say "refresh/reconnect the MosoFin integration".
  • Keep the user's request and follow /mosofin:connect (skills/connect/SKILL.md): it gives the one sign-in step for this host (Claude Code /mcp → Authenticate, Claude Connectors, ChatGPT Apps & Connectors, Grok Build), and picks the request back up when the user says they're done — no need for them to re-run /mosofin:workspaces.

Steps

  1. Call list_workspaces with no arguments (discovery).
  2. Outcomes:
    • 0 workspaces — relay the server message; stop.
    • 1 workspace — auto-confirms server-side. Read the name back and wait for an explicit yes before any data tool runs.
    • 2+ workspaces (selection_required) — ask whether the task is single- or multi-workspace, then which workspace(s) by name. Never auto-pick. Confirm with list_workspaces(workspace_ids=[…], mode="single"|"multi").
  3. To switch or add a workspace later, re-run the same confirm call with the new selection.

Rules

  • Refer to workspaces by name (and role) only. Never show integer tenant ids; show a workspace handle only if the user asks for a machine reference.
  • The server is stateless: every later tool call must carry the confirmed workspace handle as workspace_id, copied exactly as returned (it has no fixed prefix). In multi mode, each call takes one handle — pick the relevant one per call.
  • After confirmation, continue with /mosofin:connections, /mosofin:list-tools, or /mosofin:query-workspace.

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