operational-safety
SolidProgressive-disclosure operational-safety-depth modules for the work-loop. Holds failure-mode-keyed checklists the quality-engineer reviewer reasons from (state-and-idempotency, blast-radius, environment-isolation, cost-and-teardown, drift-and-rollback, observability-and-smoke), plus cloud-implementation-craft, the module also inlined into the implementer's EXECUTE brief. Each is grounded in standing operational taxonomy (AWS Well-Architected, Google SRE, the Terraform/Pulumi Day-1/Day-2 split). The orchestrator loads only the matching modules and inlines them into the reviewer's REVIEW brief — and cloud-implementation-craft into the implementer's EXECUTE brief — when infra/destructive work is detected; the subagent never self-discovers this skill. Not a reviewer prompt itself — it is the depth library the reviewer and implementer reason from. Carves against security-checklists on the reliability-vs-security lens.
Install
Quality Score: 80/100
Skill Content
Details
- Author
- eugenelim
- Repository
- eugenelim/agent-ready-repo
- Created
- 2 months ago
- Last Updated
- today
- Language
- Python
- License
- Apache-2.0
Integrates with
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
security-checklists
Progressive-disclosure security-depth modules for the security-reviewer. Holds boundary-keyed checklists (access-control, authn-session, injection, path-and-file, secrets-and-crypto, outbound-ssrf, supply-chain, config-misconfig, exceptional-conditions, llm-agent, agentic-skills) as references/, each anchored on a current standard (OWASP Top 10:2025, ASVS 5.0, API Security Top 10:2023, Proactive Controls 2024, CWE Top 25, OWASP LLM Top 10:2025, OWASP Top 10 for Agentic Applications:2026, OWASP Agentic Skills Top 10 v1.0 (AST01–AST10)). The work-loop's orchestrator loads only the boundary-matching modules and inlines them into the security-reviewer's brief; the subagent never self-discovers this skill. Not a reviewer prompt itself — it is the depth library the reviewer reasons from.
ops
Execute a milestone's interactive 🔧 Operational and 🔎 Investigation tasks — the judgment-bound work that is NOT auto-dispatched. Two modes in one pass: Operational changes production/environment state through a sanctioned surface (config/catalog/entity authoring, backfills, alarm config, dependency installs, session/machine setup); Investigation produces a defensible decision from live data (diagnoses, spikes, zero/anomaly triage) and files follow-on tasks. Enforces: autonomous runs STAGE (never verdicts, never ✅ Done), read-only diagnosis before any write, falsify every "it's fine", audited read-modify-write, reconcile+capture, "Done ≠ deployed ≠ seeded ≠ working". Records durable research to a staging journal. Use when the user says "work the ops tasks", "run ops/tooling for milestone X", "work the operational/investigation tasks", or starts an overnight or interactive ops run on a project's task board.
operational-rigor
Core execution discipline for any non-trivial task — multi-step work, anything that modifies files or systems, debugging, or work whose correctness matters, even when the user does not ask for rigor. The latest load moment is observable — you are about to take your first mutating action (edit, write, state-changing command); loading earlier is better, and if you notice you are already past it, load now. Governs the task contract, action gating, scope containment, verification by execution, adversarial self-review, and honest completion claims. Do NOT load for single-step questions, pure explanation, or trivial edits; for delegating to subagents or reviewing agent output, also load delegation-and-review.