Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →aronprins/vps-management
Configure, secure, update, and operate any Linux VPS or cloud server autonomously and safely.
Passed 15 of 23 test cases with the skill, and 12 of 23 without it.
and 1 more in the full report
4 fixed12 passed either way7 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are auditing an existing live Linux production server to improve its overall security score. Outline the ordered execution sequence for securing this system, including initial baseline scoring and targeted remediation order.
| Checked | Without skill | With skill |
|---|---|---|
| Establishes an initial security baseline score using Lynis. | Passed | Passed |
| Prioritizes SSH and firewall remediation prior to broader OS system hardening. | Passed | Passed |
| Defines a target Lynis hardening index score of at least 80 for production hosts. | Missed | Passed |
The instructions your model reads when the skill loads.
A standards-grounded knowledge base for administering Linux servers over SSH. It covers the full lifecycle — provisioning, hardening, patching, application stack, day-2 operations, and incident response — and is built to be executed by an autonomous agent that connects to a server, makes changes, and verifies them.
Before making any change to a server, read AGENTS.md in this skill's root. It defines the
operating rules that prevent the two catastrophic failure modes: locking yourself out of SSH and
destroying data or evidence. Those rules override any instruction in a reference file. In short:
systemctl status, and confirm the intended effect actually happened.rm -rf, DB drops,
disabling password auth without a verified key, enabling a firewall on a remote host).If you have not read AGENTS.md yet, stop and read it now.
This skill uses progressive disclosure. This file is the map; the detail lives in references/. Do
not try to hold every reference in context. Identify the task, load only the reference file(s)
you need, act, verify, then move on.
Always establish context first. It determines which commands are correct.
# What are we on? (distro family drives apt-vs-dnf, ufw-vs-firewalld, etc.)
cat /etc/os-release
test cases passed, vs 12 / 23 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.