agentleFS
Sign inStart free
danielrosehilldanielrosehill/Claude-Security-Auditor-Plugin/skills/remove-machine/SKILL.md

remove-machine

Skill2 starsChanged 7 months agoMITView on GitHub

Use when the user wants to deregister a machine from the fleet.

The file

We split this skill into the rules it gives an agent

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

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Verify the machine exists:

    line 30

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

Remove Machine

Deregister a machine from the fleet. The profile and audit reports are archived (not deleted) for compliance and historical reference.

When to use

  • Machine is decommissioned
  • Machine is no longer under audit scope
  • Consolidating redundant entries

Inputs to gather

  • Machine name (required)
  • Confirmation: are you sure? (Y/n) — this is irreversible without manual recovery from trash

Procedure

  1. Resolve the data directory:
    DATA_DIR="${CLAUDE_USER_DATA:-${XDG_DATA_HOME:-$HOME/.local/share}/claude-plugins}/security-auditor/data"
MACHINE_DIR="$DATA_DIR/machines/<machine_name>"
TRASH_DIR="$DATA_DIR/.trash"
  2. Verify the machine exists:
    [ -d "$MACHINE_DIR" ] || { echo "Machine not found"; exit 1; }
  3. Prompt for confirmation. If the user declines, abort.
  4. Archive the profile:
    mkdir -p "$TRASH_DIR"
TIMESTAMP=$(date -u +%Y-%m-%dT%H:%M:%SZ)
mv "$MACHINE_DIR" "$TRASH_DIR/<machine_name>-$TIMESTAMP"
  5. Confirm removal to the user and show the archive path.

Output / side effects

  • Machine profile and all audit reports moved to ${CLAUDE_USER_DATA}/security-auditor/data/.trash/<machine_name>-<timestamp>/
  • Machine no longer appears in fleet lists
  • Archive can be manually restored if needed

Safety / constraints

  • This is destructive (removes active tracking). Always confirm with the user.
  • Historical audit data is preserved in trash for compliance retention.
  • Trash directory should be backed up before cleanup.

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