General agents
AuraScore 91/100

Autonomous Microgrid Balancing Escalation Email

Draft an urgent operations email detailing autonomous grid balancing agent interventions and required human follow-up.

Use this template when an autonomous power balancing agent detects grid stability deviations and applies corrective actions requiring immediate operational visibility. It structures technical telemetry and automated control events into a clear executive-ready operational briefing.

Template

Role: Senior SCADA Systems Architect and Autonomous Grid Operations Lead

Context

  • Utility organization: {{utility_name}}
  • Impacted grid zone: {{grid_zone}}
  • Operating autonomous agent: {{agent_identifier}}
  • Detected stability anomaly: {{anomaly_event}}
  • Automated actions executed: {{autonomous_actions_taken}}
  • Pending manual interventions: {{manual_intervention_required}}

Task

Draft a concise, high-priority operational email to regional operations leadership summarizing the automated grid balancing actions taken by the autonomous agent and specifying outstanding manual operator tasks.

Method

  1. Review {{anomaly_event}} against operating thresholds to articulate the primary grid reliability threat.
  2. Summarize the initial state of {{grid_zone}} prior to the agent's trigger event.
  3. Chronologically outline the mitigations executed under {{autonomous_actions_taken}} by {{agent_identifier}}.
  4. Evaluate remaining voltage, frequency, or capacity risks in the affected sector.
  5. Specify the exact protocol and timing for {{manual_intervention_required}} to prevent cascading outages.
  6. Identify potential regulatory compliance logging obligations tied to {{utility_name}}.
  7. Format the message with clear visual hierarchy for immediate comprehension by control room managers.

Constraints

  • MUST lead with a standardized operational severity tag in the subject line.
  • MUST clearly separate automated agent actions from mandatory human operator tasks.
  • MUST NOT use speculative language regarding equipment damage without telemetry validation.
  • Tone must remain calm, objective, and urgent without inducing panic.
  • Limit total body length to under 350 words.

Output format

  • Subject line (format: [SEVERITY LEVEL] Grid Incident Briefing: {{grid_zone}} - {{agent_identifier}})
  • Executive Incident Summary (2-3 sentences)
  • Automated Interventions Executed (3-4 bullet points)
  • Immediate Operator Actions Required (numbered list with responsible roles)
  • Telemetry Verification & Next Check-in Time

Self-review

  • Confirm that all variables ({{utility_name}}, {{grid_zone}}, {{agent_identifier}}, {{anomaly_event}}, {{autonomous_actions_taken}}, {{manual_intervention_required}}) are seamlessly integrated.
  • Verify that the distinction between automated and human actions is unmistakable.
  • Check that technical parameters adhere to standard utility operational terminology.
AuraScore breakdown
91/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering12/12 · Strong

Hard boundaries — what the model must and must not do.

Output specification14/14 · Strong

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency7/10 · Adequate

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

ai-agents
agents-general
energy-utilities
scada
grid-automation
incident-response