BC remote-systems-administration
Administer and troubleshoot remote Linux, FreeBSD, NetBSD, OpenBSD, and macOS systems safely, one host or a fleet at a time. Use when a task requires SSH, Ansible, Paramiko, POSIX diagnostics, service management, software updates, system configuration, firewall changes, or evidence-led remote operations. Do not use for local-only desktop administration, container or cluster orchestration (route to kubernetes), or cloud consoles that expose no remote shell.
Administer and troubleshoot remote Linux, FreeBSD, NetBSD, OpenBSD, and macOS systems safely, one host or a fleet at a time.
As a process C 55/100 · Has gaps — weak spots: result and completion, inputs and preconditions, progress reporting
How to improve
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 4
✓ No critical or high findings
Medium and low: 4
-
low Risky intent
intent-offensive-securityreferences/ansible-administration-and-safety.md:99Offensive-security / dual-use content (legitimate for authorised testing; review intended use)Sources: [connection details](https://docs.ansible.com/projects/ansible/latest/inventory_guide/connection_details.html), [privilege escalation](https://docs.ansible.com/projects/ansible/latest/playboo
-
low Risky intent
intent-offensive-securityreferences/ansible-runbooks-and-advanced-operations.md:498Offensive-security / dual-use content (legitimate for authorised testing; review intended use)Windows SSH is a supported alternative in current Ansible, but it needs Windows OpenSSH and correctly matched `ansible_connection: ssh` plus `ansible_shell_type: powershell` or `cmd`. Treat it as a se
-
low Risky intent
intent-offensive-securityreferences/ansible.md:35Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- [Privilege escalation](https://docs.ansible.com/projects/ansible/latest/playbook_guide/playbooks_privilege_escalation.html)
-
low Risky intent
intent-offensive-securitySKILL.md:22Offensive-security / dual-use content (legitimate for authorised testing; review intended use)3. **Protect access first.** Before changing SSH, routing, DNS, a firewall, privilege escalation, or a network interface, establish a tested rollback and a second recovery path. Keep the current sessi
Files scanned: 20. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 55/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 50When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (bash, python) that frontmatter does not declare
- 100Steps. 35 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2241 tokens
- 100Running it twice. No mutating operations
- low No test case covers injection arriving through data
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 460: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 35 items
- +4Reference files are cited in the instructions (17 of 17)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 89.