ericrisco/rsc-harness / skills/hetzner
hetzner
UnverifiedUse when provisioning or hardening a Hetzner Cloud VPS: picking the plan/location (CX/CPX/CAX/CCX), bringing it up reproducibly with hcloud + cloud-init, locking down SSH, and wiring the Cloud Firewall to hand off a Docker-ready host. NOT app deploys on Coolify (that is `coolify`), NOT Dockerfiles (that is `docker`), NOT another provider (that is `digitalocean`).
Security report
UnverifiedStatic analysis of one exact version. It reduces risk and shows evidence; it does not certify that a skill is safe.
- Commit
260396d2cc71746bd3335fd191cc3f5ffc3e4567- Content hash
0d5fa2c37c383c4682b6b099b851f0d99761342eef9b27d6c8b8faebf291042e- Scanned
- 2026-11-17
- Scanner version
- skillxone-scan-1.0.0
- Policy version
- 0.1-draft
- Decision
- 2 open medium findings to review.
- Verification expires
- Not applicable
Findings (2 medium, 4 low, 1 info)
The skill sets something to run automatically later (scheduled task, login item or shell start-up file).
- systemctl enable --now fail2banSuggested fix: Do not install persistent jobs or edit shell start-up files. Tell the user what to add if they want it.
The skill sets something to run automatically later (scheduled task, login item or shell start-up file).
- systemctl enable --now fail2banSuggested fix: Do not install persistent jobs or edit shell start-up files. Tell the user what to add if they want it.
A command runs with administrator privileges.
- "non-root sudo user created via cloud-init with ssh_authorized_keys"Suggested fix: Avoid sudo where possible. If it is required, explain why so the user can decide.
A command runs with administrator privileges.
# --- non-root sudo user (root SSH gets disabled below) ---Suggested fix: Avoid sudo where possible. If it is required, explain why so the user can decide.
A command runs with administrator privileges.
sudo: ["ALL=(ALL) NOPASSWD:ALL"] # drop NOPASSWD if you want a sudo passwordSuggested fix: Avoid sudo where possible. If it is required, explain why so the user can decide.
A command runs with administrator privileges.
- **No root login.** `PermitRootLogin no` + a sudo user. Root over SSH is theSuggested fix: Avoid sudo where possible. If it is required, explain why so the user can decide.
The skill ships an executable script. Review it before allowing an agent to run it.
#!/usr/bin/env bashSuggested fix: None required. Informational.
Checks run
- prompt-injection
- dangerous-commands
- credentials
- network
- file-access
- integrity
Checks skipped
- dependencies: No dependency manifest in the skill directory.
- gitleaks: gitleaks is not installed on this host.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |