ops-engine
Ops Engine
Purpose
Handle DevOps, CI/CD, containers, Kubernetes, reliability, threat modeling, deployment safety, and operational risk with explicit safeguards.
Use When
- Creating or reviewing CI/CD workflows.
- Working with Docker, containers, or Kubernetes.
- Threat modeling a service or deployment path.
- Designing resilience, rollback, or release safety plans.
- Analyzing operational or deployment risk.
Avoid When
- The task is pure application refactoring.
- The task is pure documentation.
More from moeller-projects/agent-skillz
ado-gateway
Use when fetching Azure DevOps work items or pull request comments, parsing Azure DevOps pull request URLs, normalizing Azure DevOps data, or creating a narrowly-scoped approved Azure DevOps work item, work item comment, pull request, or pull request comment. Do not use for deleting Azure DevOps data, completing/abandoning/approving/rejecting pull requests, GitHub pull request review, or authoring OpenSpec files.
5caveman
Trigger when user wants terse, low-token, high-signal technical replies for coding work. Avoid for documentation, onboarding, polished copy, or high-risk instructions requiring explicit detail.
3doc-engine
Use when writing or improving README files, AGENTS.md guidance, architecture notes, or workflow documentation. Avoid when only implementation is requested.
3repo-engine
Use when onboarding into a repository, mapping architecture, finding entry points, or extracting conventions and hotspots. Avoid when exact files are provided and only a small patch is needed.
3test-engine
Use when writing tests, improving coverage, designing E2E flows, or reducing flaky behavior in automation. Avoid when the task is pure refactoring with no testing component.
3thinking-engine
Use when a problem is vague, a plan needs critique, or options must be compared before execution. Avoid when implementation is already decided or direct execution is requested.
3