agentleFS
Sign inStart free
MosoFinMosoFin/mosofin-plugins/skills/run-tool/SKILL.md

run-tool

Skill3 starsChanged 22 days agoMITView on GitHub

Run one specific MosoFin catalog operation against a connected company file (maps to the invoke_datasource_api_tool MCP tool). Use when the user names an exact operation to execute (e.g. run get_profit_and_loss, call search_invoices) rather than asking an open data question.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 1

    1. MosoFin/mosofin-mcp-plugin★ 3100% same

    Edited · 0

    None found.

    Wrote their own version · 1

    1. simstudioai/skills★ 2same 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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    Verify the requested tool_name exists in the live catalog (get_datasource_tools) when unsure — on UNKNOWN_TOOL, pick from the valid-names …

    line 17
  2. Very specific:

    Check mock (live vs fixture) and end with a Data sources line (datasource + tool + fetched_at from provenance).

    line 41

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

Run a catalog operation

Wraps the server's invoke_datasource_api_tool — the only data-egress tool. Full spec: docs/mcp-tool-spec.md §3.4. For open-ended questions ("how did July look?"), prefer /mosofin:query-workspace.

Steps

  1. Confirm workspace (list_workspaces) and, when several company files are connected, the company by display_name (get_agent_datasources) if not already confirmed in this chat.
  2. Verify the requested tool_name exists in the live catalog (get_datasource_tools) when unsure — on UNKNOWN_TOOL, pick from the valid-names list; never guess.
  3. Build params:
    • Period reports and searches: concrete start_date + end_date (YYYY-MM-DD) — resolve relative phrases first; ask if ambiguous.
    • As-of reports: optional report_date (default today).
    • Get-by-id: id.
  4. Invoke with datasource, tool_name, params, workspace_id, and data_source_id (both on every call and retry — the server is stateless). Independent invokes may batch in parallel.
  5. Handle results and errors:
    • Unknown tool / MosoFin tools missing / sign-in required → never say "refresh/reconnect". Keep the requested operation and params and follow /mosofin:connect (skills/connect/SKILL.md), then run it once the user is signed in. No data until then.
    • pagination.has_more → re-invoke with params.offset = pagination.next_offset.
    • approval_required → ask the user, retry the same invoke with approved=true. Never pre-set it.
    • entity_required → ask which company from entities[]; retry.
    • datasource_not_active → give the user reconnect_url; no data.
    • invalid_params → fix the named field; retry.
    • tool_policy_disabled → explain; do not retry.
  6. Check mock (live vs fixture) and end with a Data sources line (datasource + tool + fetched_at from provenance). Never fabricate figures on failure.

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