General research
AuraScore 79/100

Clean Hydrogen Blending Feasibility Research Briefing Email

Distills complex engineering literature and pilot project findings into a feasibility briefing email for gas infrastructure leads.

Use this template when summarizing technical research papers, metallurgical studies, and safety trials regarding clean fuel or hydrogen injection into natural gas utility networks. It delivers clear technical risk evaluations for engineering and innovation leaders.

Template

Role: Principal Clean Energy Technology Analyst specializing in gas utility decarbonization and infrastructure integration.

Context

  • Infrastructure Asset: {{target_pipeline_network}}
  • Injection Threshold: {{hydrogen_blend_percentage}}
  • Critical Engineering Challenge: {{primary_technical_constraint}}
  • Allocated Capital Threshold: {{capex_ceiling_estimate}}
  • Incentives & Subsidies: {{regulatory_subsidy_mechanism}}
  • Email Recipient: {{project_sponsor_email_recipient}}

Task

Synthesize technical research findings and operational feasibility data into a structured advisory email to {{project_sponsor_email_recipient}}, evaluating whether blending {{hydrogen_blend_percentage}} hydrogen into {{target_pipeline_network}} is viable within {{capex_ceiling_estimate}} while resolving {{primary_technical_constraint}}.

Method

  1. Review recent engineering trials, material integrity reports, and industry safety standards for {{hydrogen_blend_percentage}} injection.
  2. Assess the risk profile and retrofit requirements specifically associated with {{primary_technical_constraint}} on {{target_pipeline_network}}.
  3. Model the net economic picture combining {{capex_ceiling_estimate}} against potential offsets from {{regulatory_subsidy_mechanism}}.
  4. Write a subject line communicating project name, technical focus, and recommendation status.
  5. Draft a concise opening providing a definitive "Viable / Viable with Conditions / Non-Viable" research verdict.
  6. Create a structured technical synthesis covering materials integrity, safety modifications, and metering accuracy.
  7. Outline the economic reconciliation balancing capital retrofit expenditures against {{regulatory_subsidy_mechanism}}.
  8. Formulate 3 distinct milestone recommendations for pilot stage-gating.

Constraints

  • MUST maintain an objective, evidence-based engineering tone rather than promotional language.
  • MUST NOT omit explicit safety and metallurgical risk indicators related to {{primary_technical_constraint}}.
  • Email length MUST remain between 350 and 500 words.
  • Explicitly state whether the project remains within {{capex_ceiling_estimate}}.

Output format

  • Subject Line: [Project Feasibility: Asset / Blend / Recommendation Tag]
  • Salutation: Addressed to {{project_sponsor_email_recipient}}
  • Section 1: Feasibility Determination (1-2 sentences with clear verdict)
  • Section 2: Technical Research Findings (3 structured bullet points detailing material, sensor, and safety considerations)
  • Section 3: Commercial & Subsidy Alignment (brief summary of {{capex_ceiling_estimate}} vs {{regulatory_subsidy_mechanism}})
  • Section 4: Phase-Gate Recommendations (3 numbered tactical next steps)
  • Sign-off: Professional signature block

Self-review

  • Is the feasibility verdict unambiguous in the opening section?
  • Are technical realities regarding {{primary_technical_constraint}} accurately framed for {{target_pipeline_network}}?
  • Is the financial synthesis grounded strictly in {{capex_ceiling_estimate}} and {{regulatory_subsidy_mechanism}}?
AuraScore breakdown
79/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 engineering10/12 · Adequate

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

Output specification6/14 · Thin

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 efficiency5/10 · Thin

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.

research-analysis
research-general
energy-utilities
hydrogen-blending
gas-utilities
technical-research