query-workspace
Skill3 starsChanged 22 days agoMITView on GitHub
Query MosoFin workspace business data (accounting platforms and other connected SaaS). Use when the user asks for P&L, invoices, cash, customers, or any live books data, or mentions MosoFin, a client workspace, or reconnecting a data source.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- MosoFin/mosofin-mcp-pluginword for word, first seen Oct 21, 2026
Other versions1 project uses a version of this.
Word for word · 1
- MosoFin/mosofin-mcp-plugin★ 3100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
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.
- connectionsSkill
- connectSkill
- list-skillsSkill
- list-toolsSkill
- replay-skillSkill
- run-toolSkill
- save-skillSkill
- workspacesSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 1 is distinctive, and 7 are 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.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Read-only path for any MosoFin data question.
- Very specific: line 27
Call list_workspaces with no arguments.
- Very specific: line 29
If several exist, ask single- vs multi-workspace, then which name(s), and confirm with list_workspaces(workspace_ids=[…], mode="single") or …
- Very specific: line 33
Call get_agent_datasources for the confirmed workspace_id.
- Very specific: line 35
If more than one row for a platform is connected: true, ask which company, then pass that data_source_id on every later call.
- Very specific: line 37
If the needed source is connected: false, stop.
- Very specific: line 40
Call get_datasource_tools for the chosen datasource (and data_source_id when required) to pick a valid tool_name.
- Distinctive: line 92
If the fetch does not cover part of the question, say so and name the tool that could fetch it.
≈ “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
Query a MosoFin workspace
Read-only path for any MosoFin data question. Call only the MosoFin MCP tools
listed below. Full per-tool spec (inputs, outputs, examples, errors):
docs/mcp-tool-spec.md. Short contract: docs/plugin-contract.md.
MosoFin MCP tools used (registered names; your host prefixes them, e.g.
mcp__plugin_mosofin_mosofin__<name> in Claude Code or mcp__MosoFin__<name>
for a Claude connector):
list_workspacesget_agent_datasourcesget_datasource_toolsinvoke_datasource_api_tool
Native pickers may not appear (production MCP is stateless JSON). Ask in chat, then pass handles explicitly.
Steps
- Call
list_workspaceswith no arguments. - Show workspaces by name (and role). Never show integer tenant ids.
If several exist, ask single- vs multi-workspace, then which name(s), and
confirm with
list_workspaces(workspace_ids=[…], mode="single")ormode="multi". One accessible workspace auto-confirms server-side — still read the name back and wait for an explicit yes before invoking data tools. - Call
get_agent_datasourcesfor the confirmedworkspace_id.- Refer to companies by
display_name. Never show rawdata_source_id. - If more than one row for a platform is
connected: true, ask which company, then pass thatdata_source_idon every later call. - If the needed source is
connected: false, stop. Tell the user to open thereconnect_urlfrom a later error, or the MosoFin workspace data-sources page. Do not invent numbers.
- Refer to companies by
- Call
get_datasource_toolsfor the chosen datasource (anddata_source_idwhen required) to pick a validtool_name. - Call
invoke_datasource_api_toolwith:datasource(e.g.quickbooks)tool_namefrom the catalog (e.g.get_profit_and_loss)workspace_id(the opaque handlelist_workspacesreturned, copied exactly) on every calldata_source_idon every call when the workspace has multiple companiesparamswith concreteYYYY-MM-DDdates — resolve "last month" / "this quarter" before invoking. Transaction searches and period reports need bothstart_dateandend_date. As-of reports (get_balance_sheet,get_aged_receivables, …) take an optionalreport_date(default today). Get-by-id tools needid. Multiple independent invokes may run in parallel in one turn.
Result handling
- Pagination (search tools): if
pagination.has_moreis true, re-invoke withparams.offset = pagination.next_offsetuntil complete or the user has enough. Omitmax_resultsunless a smaller page is needed. - Budgets are two-step:
search_budgetsto list names, thenget_budget_detailswithbudget_idorbudget_name. mockflag:falsemeans live numbers — say so.truemeans demo/fixture data — tell the user the numbers are not real.
Read-only boundary
MosoFin cannot create, update, send, or delete records in any connected
accounting platform or other SaaS. If asked to (e.g. "create an invoice"), do not invoke — explain
the boundary and offer the read equivalent (e.g. search_invoices).
Errors
- Unknown tool / MosoFin tools missing / sign-in required — the user is
not signed in to MosoFin in this host. Never say "refresh/reconnect". Keep
the question (dates already resolved) and follow
/mosofin:connect(skills/connect/SKILL.md); when the user says they're done, confirm the workspace and answer the original question. Do not invent data. - Workspace not confirmed — confirm via
list_workspacesthen retry. entity_required— ask which company fromentities[]; retry with thatdata_source_id.datasource_not_active/connection_unavailable— give the userreconnect_url. Do not guess data.invalid_params— fix dates/fields and retry.approval_required— ask the user, then retry withapproved=true.tool_policy_disabled/ valid-access refusal — explain; do not leak or invent data.
Grounding
Answer only from invoke results in this conversation. Do not use general
knowledge or another company's memory. End data-backed answers with one
Data sources line (datasource + tool + fetched_at from provenance).
If the fetch does not cover part of the question, say so and name the tool
that could fetch it.
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.

