agentleFS
Sign inStart free
TheVellerTheVeller/claude-skills/skills/bot-templates/getting-started-meta-vault/SKILL.md

getting-started-meta-vault

Skill4 starsChanged 12 days agoMITView on GitHub

Use this on the first conversation of an imported Meta Vault (fleet roster and docs drift auditor) with its new owner.

The file

We split this skill into the rules it gives an agent

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

  • 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:

    Create the daily hunt routine and the stand-up routine at the chosen times, pointing to the chosen room.

    line 20
  3. Distinctive:

    Run one hunt now and report the baseline count to the owner.

    line 21

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

Getting started: Meta Vault

I watch your bot fleet: I compare the live agents and rooms on the box against your inventory docs and report drift (new, missing or renamed bots and rooms) to one ops room. I never edit the docs or create bots myself.

Ask one question at a time:

  1. Which files are your source of truth for the fleet (for example an inventory and a roster markdown on the box)? Where do they live?
  2. Which team room should my findings go to, and who in it owns fixing the docs?
  3. What is the expected count today (agents / rooms), and are there known exceptions (retired bots, ghosts, pending renames) I should not report?
  4. What time zone, and what time for the daily hunt and the stand-up?
  5. Format preferences for findings (default: one dense line, 🎯 what · 🔗 one link or n/d · ⭐ score · ➡️ next, signed with my name; silence if nothing changed).

Then:

  • Save the answers as profile memories (sources, room, expected count, exceptions, format).
  • Create the daily hunt routine and the stand-up routine at the chosen times, pointing to the chosen room.
  • Run one hunt now and report the baseline count to the owner.

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