编程

Climate Risk Assessment

试用

Assess physical and transition climate risk for a site, product, or portfolio with scenario-based structure. Use when asked to run a climate risk assessment,...

它能做什么

Climate risk work goes wrong by being either vague ("weather may worsen") or falsely precise ("flood losses of $4.7M in 2043"). This skill structures an assessment as hazard × exposure × vulnerability, across explicit time horizons and named scenarios, with impact expressed as ranges plus a confide…

技能文档

Climate Risk Assessment Skill

Climate risk work goes wrong by being either vague ("weather may worsen") or falsely precise ("flood losses of $4.7M in 2043"). This skill structures an assessment as hazard × exposure × vulnerability, across explicit time horizons and named scenarios, with impact expressed as ranges plus a confidence label. It supports decision-making; it is not an engineering or actuarial study.

What This Skill Produces

  • A risk register for the asset(s): hazard × exposure × vulnerability, scored per horizon and scenario
  • Physical risks (acute + chronic) and transition risks (policy, market, technology, reputation) treated separately
  • Financial-impact ranges with an explicit confidence level per estimate
  • Adaptation and mitigation options with rough cost/benefit direction
  • A stated-assumptions register so the assessment can be challenged and updated

Required Inputs

Ask for these if not provided; with a thin brief, proceed using labelled assumptions (e.g. "assumed coastal location — confirm") rather than refusing:

  • Subject — the site(s), product, or portfolio, with location(s) and asset life / planning horizon
  • Exposure basics — what is physically and economically at stake: asset value, revenue dependence, supply chain nodes, workforce
  • Known sensitivities — past climate-related disruptions, insurance history, single points of failure
  • Transition context — sector, carbon intensity, regulatory exposure, customer decarbonization pressure
  • Financial scale — revenue or asset value bands, so impact ranges land in the right order of magnitude

Assessment Framework

1. Structure every risk as hazard × exposure × vulnerability. A hazard (e.g. riverine flood) only becomes a risk when exposure (asset in the floodplain) meets vulnerability (no defenses, 6-week recovery). Score each component, not just the headline.

2. Use three horizons: 2030 / 2040 / 2050. Near-term physical risk is mostly locked in regardless of scenario; scenario divergence dominates from ~2040. Say which effect drives each rating.

3. Label scenarios and use them consistently:

LabelCharacterPhysical riskTransition risk
OrderlyEarly, coordinated policy (~1.5–2°C)Lower long-termFront-loaded but predictable
DisorderlyLate, abrupt policy (~<2°C, delayed)ModerateSharp, repricing shocks in 2030s
HothouseWeak policy (~3°C+)High and compoundingLow policy risk, high physical + liability

Assess at least orderly and hothouse — they bracket the outcome space. Note that transition and physical risk peak in different scenarios; a single-scenario view always understates one of them.

4. Express impact as a range with confidence. Use order-of-magnitude bands tied to the subject's financial scale (e.g. "1–5% of site revenue per event"), and tag each estimate High / Medium / Low confidence with the reason (data quality, model dependence, deep uncertainty).

5. Identify adaptation options per material risk. Categories: harden (physical protection), diversify (sites, suppliers), transfer (insurance, contracts), retreat (relocate, exit), and accept (with monitoring trigger). Note rough cost direction and by when a decision is needed.

Output Format

Climate risk assessment: [subject]

1. Scope and assumptions — subject, horizons, scenarios used, and every assumption made from a thin brief, labelled.

2. Physical risk register — table: hazard | type (acute/chronic) | exposure | vulnerability | rating per horizon × scenario | confidence.

3. Transition risk register — same structure across policy, market, technology, and reputation risks (include transition opportunities where real).

4. Financial impact summary — the top 5 risks with impact ranges, confidence, and which scenario/horizon drives each.

5. Adaptation options — per material risk: option, category, cost direction, decision-by date.

6. Monitoring triggers — observable signals (regulation drafts, insurance repricing, hazard events) that should force a reassessment.

Include this line in the artifact: "Verify scenario selection, disclosure use, and any figures intended for reporting against the applicable standard/regulation (e.g. ESRS E1, TCFD/ISSB) with your compliance team; use engineering-grade studies before capital decisions."

Quality Checks

  • Every risk decomposes into hazard, exposure, and vulnerability — no monolithic "climate risk" entries
  • All three horizons and at least two labelled scenarios are covered, and the driver of each rating is stated
  • Every financial estimate is a range with a confidence label and a reason for that confidence
  • Transition and physical risks are assessed separately and both appear in the top-risks summary
  • Each material risk has at least one adaptation option with a decision-by date
  • Assumptions and monitoring triggers are explicit enough for a future reassessment

Anti-Patterns

  • Do not give point estimates for long-horizon losses — ranges with confidence, always
  • Do not assess only one scenario — a single pathway hides either transition or physical risk
  • Do not conflate hazard with risk — a flood map is not a loss estimate until exposure and vulnerability are in
  • Do not let 2050 risks crowd out 2030 decisions — state what must be decided this planning cycle
  • Do not present this as an engineering, actuarial, or compliance-grade study — it structures judgment, it does not replace specialist analysis

Based On

TCFD/ISSB and ESRS E1 climate-risk practice (physical/transition split, scenario analysis, hazard–exposure–vulnerability structure).

相关技能

把自然语言描述转为结构化 JSON,并由 mcp-diagram-generator MCP 服务生成 Draw.io、Mermaid 或 Excalidraw 图表文件。

作者 nssa.io1.0k 次安装47 星标

在本地磁盘以分类纯 Markdown 文件保存需要长期留存的事实,与智能体内置记忆并存。

作者 Iván559 次安装18 星标

诊断生产力系统反复失效的根因,给出最小干预——容量测算、瓶颈定位、可靠的本地记录。

作者 Iván855 次安装69 星标

以 AI 机器人身份加入视频会议,提供语音、虚拟形象与屏幕共享四种模式。

作者 johnpatternai22 次安装8 星标

从 AdMapix API 拉取广告创意、应用、榜单和收入预估等数据,原样返回结构化 JSON。

作者 fly0pants4.3k 次安装296 星标

执行 Git 操作(提交、分支、合并、变基、冲突解决与恢复)时强制套用安全规则。

作者 Iván535 次安装31 星标

mohitagw15856 的更多技能

浏览全部技能

Extract a brand's visual and verbal identity into an applicable guideline kit — tokens, voice rules, and do/don't pairs — then apply it consistently to any a...

作者 mohitagw158562 次安装

Write an AI usage policy people can actually follow — approved tools, data rules, disclosure duties, and review obligations, in one page instead of legal fog...

作者 mohitagw15856

Write an executive summary for any document, report, or proposal. Use when asked to write an executive summary, management summary, briefing paper, or one-pa...

作者 mohitagw158562 次安装

Convert a git log, commit list, or release notes into a polished, user-facing changelog. Use when writing release notes, generating a CHANGELOG.md entry, or...

作者 mohitagw158562 次安装

Document or design a database schema with entity relationships, table definitions, constraints, indexes, and access patterns. Use when asked to design a data...

作者 mohitagw158561 次安装

Design a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colle...

作者 mohitagw158561 次安装