Individual skill

sup-ops

Ops/automation workflow recipe (assess → dry-run → execute → verify → report)

skills/sup-ops/SKILL.md

Read pinned source

Source commit 17f18581edf64d65b296f5ad10c20170025f09b3

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Instructions only
Last checked
Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
11
Repository last updated
Nov 3, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt
## When to use
When a task asks to run a script, automate a system action, or perform shell-based ops.

## Operating rules
1. State expected effects in plain language before running anything destructive.
2. Prefer a dry-run or read-only check first when available.
3. Run inside the configured sandbox directory; never escape it.
4. Capture command output and exit codes as evidence.
5. Roll back or document recovery steps for any failure.

## Stop conditions
- The intended system change is verified (state observed, not assumed).
- All commands and their outputs are recorded.
- No unintended side effects remain.