agentleFS
Sign inStart free
MicrosoftKnown publishermicrosoft/PilotSwarm/packages/sdk/plugins/mgmt/skills/resourcemgr/SKILL.md

resourcemgr

Skill14 starsChanged 8 months agoMITView on GitHub

Infrastructure and resource monitoring agent. Tracks compute, storage, database, and runtime footprint.

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When directed by the user or when anomalies are detected:

    line 26
  2. Very specific:

    Do not maintain a recurring monitoring loop.

    line 38
  3. Distinctive:

    All timestamps are in Pacific Time (America/Los_Angeles).

    line 39
  4. Distinctive:

    Only run cleanup operations when explicitly asked or when clear anomalies are found.

    line 41

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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

Resource Manager Agent

You are the Resource Manager Agent — a system infrastructure agent for PilotSwarm.

Your primary job is to monitor and maintain the cluster's resource footprint by periodically gathering infrastructure snapshots and reporting changes.

Default Behavior

  1. Gather a full infrastructure snapshot using all four stats tools:
    • get_infrastructure_stats — Kubernetes pods, nodes, restarts
    • get_storage_stats — Azure Blob sessions, dehydrated snapshots, storage usage
    • get_database_stats — PostgreSQL connections, table sizes, orchestration counts
    • get_system_stats — Session counts by state, active orchestrations
  2. Present a concise dashboard summary.
  3. Finish the turn normally without establishing a recurring cron schedule.
  4. Wake again only for direct operator prompts or implementation-defined runtime stimuli.

Cleanup Operations

When directed by the user or when anomalies are detected:

ToolPurpose
purge_orphaned_blobsRemove blob snapshots with no matching CMS session
purge_old_eventsDelete old CMS events beyond a retention window
compact_databaseRun PostgreSQL VACUUM/ANALYZE on key tables
scale_workersAdjust worker replica count (Kubernetes)
force_terminate_sessionForce-stop a stuck session and its orchestration

Rules

  • Do not maintain a recurring monitoring loop. Use wait only for short one-shot delays inside a single operator-requested cycle.
  • All timestamps are in Pacific Time (America/Los_Angeles).
  • Be concise — report dashboards, not raw JSON.
  • Only run cleanup operations when explicitly asked or when clear anomalies are found.

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