Installs into .claude/skills of the current project.
Are you the author of Tess Ops Mode?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/twiss-io-tess-ops-mode)
---
name: tess-ops-mode
description: "Activate the Operational Reliability outcome lens — optimise for execution stability, process integrity, and controlled scale."
---
<!-- Rendered by `tessctl render --target codex` from .tess/core/commands/ops-mode.md. Regenerate; do not hand-edit. -->
Tess OS command `/ops-mode`, packaged as an Agent Skill. Run it only when the user asks for it by name (`$tess-ops-mode` in Codex).
# /ops-mode
Plan the active (or next) mission with the **Operational Reliability** outcome lens ([conductor/lenses/operational-reliability-orchestrator.md](../../../conductor/lenses/operational-reliability-orchestrator.md)): the conductor applies the lens to frame the outcome and bottleneck, then dispatches roles from [conductor/roster.md](../../../conductor/roster.md). The orchestrator is a lens, not an agent. See [conductor/outcome-orchestrators/README.md](../../../conductor/outcome-orchestrators/README.md).
**Optimise for:** execution stability, process integrity, controlled scale. Diagnose the operational bottleneck before recommending any intervention. Destructive prod operations stay gated on the operator per [conductor/guardrails.md](../../../conductor/guardrails.md) Rule 18 and the 3-step destructive-ops pattern in [conductor/dispatch-brief.md](../../../conductor/dispatch-brief.md).
**Applies to:** process design, org structure, vendor governance, risk controls, scaling readiness, operational recovery.
