agentleFS
Sign inStart free
camoacamoa/vibe-config/skills/machine-check/SKILL.md

machine-check

Skill1 starsChanged 23 days agoMITView on GitHub

Checks whether this computer is ready to run a local Drupal site (operating system, container runtime, DDEV, Node.js, npm) and lists what the person still has to install. Use before setting up a site, or when a setup step fails because a tool is missing.

The file

We split this skill into the rules it gives an agent

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

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run it once before you set up a local site, and again after the person installs something.

    line 10
  2. Very specific:

    When ready is true, go on to the next stage.

    line 35

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

Machine check

When to run it

Run it once before you set up a local site, and again after the person installs something.

How to run it

From this skill folder:

bash scripts/check-machine.sh

It prints one JSON object and exits 0 whenever the check ran, whatever it found. bash scripts/check-machine.sh --summary prints a short plain-text summary instead. Show the summary to the person. Read the JSON yourself.

How to read the JSON

  • os: macos, wsl2, linux or unsupported.
  • ready: true when the container runtime runs, DDEV is installed, Node.js 24 LTS or later is installed, and npm is installed.
  • checks.container: the container runtime, with three keys.
    • running: true when the runtime answers.
    • provider: DDEV's platform name when DDEV did the check, such as orbstack or linux-docker. Otherwise orbstack, colima, docker-desktop or unknown. It is none when neither DDEV nor Docker is installed.
    • via: how it checked: ddev-dockercheck, docker-info or none.
  • checks.ddev, checks.node, checks.npm: each has installed (true or false) and version (empty when not installed). A Node.js older than 24 makes ready false and adds a node step.
  • next_steps: an array of objects with piece, step and person_runs. piece is os, container, ddev, node or npm. step is the step's text, naming the command to run or the web address to open. When person_runs is true, ask the person to do the step. Run the check again afterwards.

When ready is true, go on to the next stage.

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