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

argus-status

Skill140 starsChanged 27 days agoMITView on GitHub

Use when checking an Argus project's progress, pending questions, active role, diagnostics, selected artifacts, intervention state, recovery options, or graceful stop status.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 1 is distinctive, and 4 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.

  • 4

    Very specific

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

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

    Call argus_status. Report daemon state, active role, completed and pending work, pending operator questions, and continuous objective …

    line 10
  2. Very specific:

    Call argus_artifacts when the user asks for outputs.

    line 12
  3. Very specific:

    Call argus_doctor only when status exposes a runtime/backend fault or the user requests diagnostics.

    line 14
  4. Very specific:

    Call argus_stop only on an explicit stop request.

    line 18
  5. Distinctive:

    Do not count provider, transport, interrupted, or resource failures as task failures.

    line 22

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

Inspect And Control Argus

  1. Resolve the project ID from the user's explicit ID or call argus_project_list for the exact work directory.
  2. Call argus_status. Report daemon state, active role, completed and pending work, pending operator questions, and continuous objective separately.
  3. Call argus_artifacts when the user asks for outputs. Report only existing allowlisted artifacts returned by Argus.
  4. Call argus_doctor only when status exposes a runtime/backend fault or the user requests diagnostics.
  5. Send ordinary steering or answers through argus_message; Manager remains the operator front door.
  6. Call argus_stop only on an explicit stop request. Keep force=false unless the user explicitly requests a force stop after understanding interruption risk.

Do not count provider, transport, interrupted, or resource failures as task failures. Do not translate training loss or activity into a successful result.

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