agentleFS
Sign inStart free
danielrosehilldanielrosehill/Claude-Security-Auditor-Plugin/skills/list-machines/SKILL.md

list-machines

Skill2 starsChanged 7 months agoMITView on GitHub

Use when the user wants to view registered machines and their metadata.

The file

We split this skill into the rules it gives an agent

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

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Check SSH reachability of all machines

    line 13
  2. Very specific:

    If --status is requested, note that connectivity checks add time.

    line 42
  3. Distinctive:

    No files are modified

    line 49

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

List Machines

Display all registered machines in the fleet with optional detailed views and live connectivity checks.

When to use

  • User wants a quick overview of the fleet
  • Check SSH reachability of all machines
  • Export machine inventory in JSON format
  • Review detailed metadata for a single machine

Inputs to gather

  • Machine name (optional; if omitted, list all)
  • View mode (optional):
    • --detailed — full profile metadata
    • --status — live SSH connectivity check (may take time)
    • --json — raw JSON output for scripting

Procedure

  1. Resolve the data directory:
    DATA_DIR="${CLAUDE_USER_DATA:-${XDG_DATA_HOME:-$HOME/.local/share}/claude-plugins}/security-auditor/data"
REPO_BASE="$DATA_DIR"
export REPO_BASE
  2. Invoke the list script:
    cd /home/daniel/repos/github/my-repos/Claude-Security-Auditor-Plugin
bash scripts/list-machines.sh [machine_name] [--detailed|--status|--json]
  3. Format output as a table (default) or pass through JSON/detailed formats as-is.
  4. If --status is requested, note that connectivity checks add time; show a spinner or progress indicator.

Output / side effects

  • Table or JSON of machines with name, description, SSH address, OS, type, and registration date
  • Optional --detailed adds root_access status, last audit timestamp, audit report count
  • Optional --status shows real-time SSH connectivity (reachable/unreachable)
  • No files are modified

Safety / constraints

  • Status checks perform actual SSH connections; may fail if credentials have expired.
  • Large fleets (50+ machines) may be slow in detailed or status modes.

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