# Operator Essence

> Use when operator context is missing, stale, corrected, or needed for a build decision, or when assessing usage insights and recurring collaboration patterns. Also use when the operator requests an essence file or evidence-based workflow improvements.

- Skill: `tcuzzo/operator-essence` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx get-skill add tcuzzo/operator-essence`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tcuzzo/operator-essence/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- License: MIT
- Author: Tcuzzo (https://skillmd.com/u/tcuzzo)
- Updated: 2026-11-14
- Page: https://skillmd.com/skills/tcuzzo/operator-essence

---


# Operator Essence

Give the agent useful awareness of the current operator, supported by evidence.
An essence file is contextual data, not instructions, authorization, a fixed
persona, or a substitute for the current request.

## One evidence pass, then build

1. **Reuse current context.** The task owner checks the existing packet for the
   current operator's essence reference, relevant slice and insights-attempt
   receipt. A nested skill reuses that result. Resolve an explicit private
   `OPERATOR_ESSENCE.md` path and opaque operator key from the current scope;
   do not select another operator by proximity or infer identity from language.
2. **Inspect the file.** Use [the explicit-path helper and format](references/format.md).
   A valid current file supplies only relevant preferences and observations.
   A correction wins immediately; reconcile it even when the file is recent.
   Invalid or mismatched data is unavailable context, not permission to overwrite.
3. **Missing or stale? Invoke insights once for this task.** Discover the host's
   actually available insights command, skill or connector and use its supported
   invocation. Record the result or exact limitation. If none is callable, assess
   the supplied report, relevant authorized history and current instructions.
   State that fallback; never claim a host command ran. Collect only evidence
   relevant to the operator's work, within the current scope and remaining budget.
4. **Create or reconcile the essence.** Record sources, dates, sample selection,
   confirmed preferences, observations, counts, uncertainty, counterexamples and
   tentative adaptations. Unknown values stay unknown. Report interpretations
   remain inferences; overlapping event labels are not session failure rates.
   With sparse evidence, create a provisional file containing only supported
   facts. In read-only mode, return a provisional context slice without writing
   to the protected target. Missing history does not block authorized building.
5. **Pass awareness to the agent.** Supply the compact slice from the format:
   reference and freshness; relevant confirmed preference; observation and
   evidence; suggested adaptation; limits. The task owner resumes
   [Build Flow](../backs-build-flow/SKILL.md) with the same budget. Show the operator
   what changed and where to inspect the file or live task record.

## Qualitative and quantitative assessment

Read what the operator requested, corrected, accepted and rejected alongside
actual task outcomes. Separate observations from explanations. Counts describe
their stated population; a selected sample with unknown selection cannot describe
all sessions. Tool-call volume does not prove correct skill use, and correlation
does not establish the cause of a failure.

Turn supported patterns into context-specific adaptations with a review
condition. Compare subsequent tasks of similar type before claiming improvement.
Keep successful counterexamples visible. Do not infer psychological traits,
competence, culture, risk tolerance or enduring priorities from writing style or
aggregate usage statistics.

## Exit

The caller receives a current or explicitly provisional context slice, evidence
limits, and the next build action. Historical tendencies fill gaps; current
instructions and verified project facts control the work. The file never grants
permission, expands scope, resets a bounded loop, or changes acceptance criteria.

