Operating safely on live systems
Guards for destructive operations, secrets hygiene and concurrent-session safety — short pointer
- What
- Guards for destructive operations, secrets hygiene and concurrent-session safety — short pointer
- Cost
- Free
- Needs
- nothing — this is a reference lookup; no license declared in the source repo — read it yourself before reusing its content
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — a short pointer to @riekelt's operating-safely ruleset: the guards for acting on live systems and shared state — look at the target before deleting or overwriting, name the specific instance instead of bulk teardown, per-instance confirmation for destructive operations, secrets hygiene (names and structural checks only, never print values, never decrypt to disk), one writer per file during concurrent sessions, and incident-mode discipline where read-only triage is always allowed but the confirmation bar for destructive operations never drops with urgency. Honest caveats: **no license declared in the repository — license unknown**, so this is a short fiche linking to the source, without reusing its content; the file declares itself as required background for the companion `principal-engineering` skill, so read that too. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: nothing — this is a reference lookup; no license declared in the source repo — read it yourself before reusing its content Install "Operating safely on live systems" for me. Fetch the SKILL.md from the source repository into a temporary folder, review it for anything suspicious, and report in two or three sentences what the operating-safely ruleset covers (destructive-operation guards, secrets hygiene, concurrent-session safety, confirmation authority, incident mode) so I can follow it as a discipline. Do not copy the ruleset's content into my project — this is a reference lookup only. Repository: https://github.com/riekelt/principal-engineer/blob/main/plugins/principal-engineer/skills/operating-safely/SKILL.md GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Rules: don't touch anything outside the temp folder. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.