agentleFS
Sign inStart free
MicrosoftKnown publishermicrosoft/ArgusAgent/plugins/argus/skills/argus-run/SKILL.md

argus-run

Skill140 starsChanged 27 days agoMITView on GitHub

Use when work needs persistent multi-step execution, independent review, resumable project state, or long-running research and engineering coordination through Argus.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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. Distinctive:

    Use the installed Argus MCP tools.

    line 8
  2. Very specific:

    Call argus_project_list with the exact current work directory.

    line 11
  3. Very specific:

    Call argus_message with the user's complete objective.

    line 14
  4. Very specific:

    If the MCP server is unavailable, run argus --doctor and report the exact installation or backend failure.

    line 20
  5. Distinctive:

    Never claim completion from dispatch, daemon activity, loss, or intermediate artifacts.

    line 24

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

Use the installed Argus MCP tools. Do not imitate the Argus roles in the host session and do not write Argus state files directly.

  1. Call argus_project_list with the exact current work directory.
  2. Reuse the most recently active exact-workdir project when one exists; otherwise call argus_project_create with that directory and a concise name.
  3. Call argus_message with the user's complete objective. Manager owns chat versus task routing, lifetime, workflow, domain, and execution handoff.
  4. Report the project ID and whether the turn was handled inline or dispatched.
  5. For dispatched work, stop the current turn. Do not create an unchanged polling loop; use the argus-status Skill when status is requested.

If the MCP server is unavailable, run argus --doctor and report the exact installation or backend failure. Do not silently replace Argus with an ad hoc single-agent workflow.

Never claim completion from dispatch, daemon activity, loss, or intermediate artifacts. Argus completion comes from its persisted Reviewer/Manager state.

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