agentleFS
Sign inStart free
MosoFinMosoFin/mosofin-plugins/skills/replay-skill/SKILL.md

replay-skill

Skill3 starsChanged 22 days agoMITView on GitHub

Fetch and replay one of the user's saved MosoFin skills after they name it and consent (maps to the get_my_skill MCP tool). Use when the user asks to run, replay, or re-use a saved skill or workflow by name.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 1

    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.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 0 are distinctive, and 3 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.

  • 3

    Very specific

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

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

    If MosoFin tools are absent, a call returns Unknown tool, or MosoFin reports that sign-in is required: the user is not signed in to MosoFin …

    line 14
  2. Very specific:

    Ask each inputs[].ask question verbatim — never silently default dates.

    line 33
  3. Very specific:

    Check mock (live vs fixture) and end with a Data sources line per fetch.

    line 42

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

Replay a saved skill

Wraps the server's get_my_skill tool (consent is server-enforced) plus recipe execution via invoke_datasource_api_tool. Full spec: docs/mcp-tool-spec.md §3.6.

If MosoFin tools are missing

If MosoFin tools are absent, a call returns Unknown tool, or MosoFin reports that sign-in is required: the user is not signed in to MosoFin in this host (this is not a company-file reconnect). Keep their request and follow /mosofin:connect (skills/connect/SKILL.md) to get them signed in from this conversation, then continue. Never say "refresh/reconnect". Do not invent skill contents or figures.

Steps

  1. Confirm workspace via list_workspaces if this chat has not already.
  2. Find the skill with get_skills; match the ask against name / description. Present the candidate by name and wait for an explicit yes. Never auto-replay.
  3. Only then call get_my_skill(skill_id, confirmed="yes", workspace_id=…). confirmed must be "" or "yes" — "yes" only after the explicit chat yes. Files marked content_omitted: true need a re-call with paths=[…] and confirmed="yes" again.
  4. If references/run-recipe.json exists:
    • Ask each inputs[].ask question verbatim — never silently default dates.
    • For a type: "data_source" input, list companies by display_name (get_agent_datasources) and pass the chosen data_source_id into every step carrying the "{data_source_id}" placeholder. A literal id in the recipe is pinned — use it as written.
  5. Execute steps in order (same parallel_group may batch), substituting {workspace_id} and collected inputs, replaying data only via invoke_datasource_api_tool — never invented numbers.
  6. Check mock (live vs fixture) and end with a Data sources line per fetch.

Unknown, archived, or someone else's skill_id all return the same error — report it plainly and do not probe existence.

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