agentleFS
michaelreynolds111-devmichaelreynolds111-dev/ai-context/skills/computer-file-steward/SKILL.md

computer-file-steward

Skill0 starsChanged 3 months agoNo licenceView on GitHub

Use when importing existing machine knowledge and producing a privacy-preserving, READ-ONLY inventory and review report for ONE explicitly supplied directory on Michael-PC, using four machine-readable registries (location, placement-policy, protection, project). Triggers on requests to "review a folder read-only", "inventory a directory safely", "steward a directory without touching it", "produce a placement/classification report", "what's in this folder and where should it go", "review a directory without moving anything". Also Build 2 Mode 2 supports approval-ready planning, with NO execution "build an approval-ready plan from a validated review run", "show me which actions in a plan are approval-ready or blocked", "record approval for ACT-123 or rejection for ACT-456 in a plan", "check whether a plan is still current". Defaults to READ-ONLY review; Build 2 plans are approval-ready decision records only — never moves, copies, renames, deletes, archives, restores, or modifies files.

  • Reads credentials

The file

Show its rules and text

We split this skill into the rules it gives an agent

14 rules. About 0 are common, 9 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈9

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

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

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.