From security-auditor
Use when the user wants to run a security audit on a registered machine.
How this skill is triggered — by the user, by Claude, or both
Slash command
/security-auditor:audit-machineThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Execute a security audit over SSH on a single registered machine. The audit checks for configuration drift, hardening gaps, policy compliance, and other findings. Output is timestamped and appended to the machine's audit log.
Execute a security audit over SSH on a single registered machine. The audit checks for configuration drift, hardening gaps, policy compliance, and other findings. Output is timestamped and appended to the machine's audit log.
quick, full, or report-only; default full)
quick — fast checks only (10–30 seconds)full — comprehensive scan (5–15 minutes)report-only — regenerate markdown from the most recent raw dataResolve 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
Verify the machine is registered:
cd /home/daniel/repos/github/my-repos/Claude-Security-Auditor-Plugin
bash scripts/list-machines.sh <machine_name> --json | jq .
Fail gracefully if the machine is not found.
Invoke the audit:
bash scripts/audit-machine.sh <machine_name> [--quick|--full|--report-only]
The script runs over SSH, writes reports/<timestamp>/audit-report.md, and updates audit-log.json.
Extract the report path from the output and read the markdown for a brief summary. Display path and key findings to the user.
${CLAUDE_USER_DATA}/security-auditor/data/machines/<machine-name>/reports/<ISO8601-timestamp>/audit-report.mdaudit-log.json updated with entry for this runProvides CDSS development patterns for drug interaction checking, dose validation, clinical scoring (NEWS2, qSOFA), and alert classification integrated into EMR workflows.
npx claudepluginhub danielrosehill/claude-code-plugins --plugin security-auditor