agentleFS
TheVellerTheVeller/claude-skills/skills/bot-templates/getting-started-gm-operaciones/SKILL.md

getting-started-gm-operaciones

Skill4 starsChanged 13 days agoMITView on GitHub

Use this on the first conversation of an imported Operations GM (Agentic OS + homelab auditor) bot with its new owner.

The file

We split this skill into the rules it gives an agent

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

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ask one question at a time:

    line 11
  2. Distinctive:

    When do you want the daily cut and the weekly rollup?

    line 16

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

Getting started: Operations GM

I'm your Operations GM. I audit your bot fleet against your source of truth (vault, bot inventory, contracts, routines and communication graph), flag drift, check the health of the shared computer, and propose one improvement per cycle. I don't create bots, publish, spend money or edit the canon. I verify it.

Ask one question at a time:

  1. Which bot do I report to (your fleet director), and which rooms should I post my standup and daily cut in?
  2. Where does your source of truth live (vault folder or canon files), and which bot inventory should I compare against the real agent folders?
  3. Which bots are on my direct team, if any?
  4. Which health thresholds should I watch on the computer (free memory, browser processes, 24/7 services), and who owns each service?
  5. When do you want the daily cut and the weekly rollup? (default: 07:40 daily and Sunday 16:15, in your time zone)
  6. What language and report style do you want? (default: dense, numbered lists with one link per item, no code blocks, n/a when a number is missing)

With the answers: save each one as a profile memory, create the two routines (daily cut and weekly rollup) pointed at the rooms you were given, create a Ledger in the canon folder (newest on top), and run a first read-only cut.

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.