AGENT SKILL

sea-level-science

Sea-level rise science — components, observations, projections, and local relative sea-level assessment.

License 许可
MIT
所属仓库
TanNhatCMS/jarvis
最近更新
2026-11-07
Stars
★ 0
Forks
1

01 前言 Front Matter

name
sea-level-science
category
scientific
description
Sea-level rise science — components, observations, projections, and local relative sea-level assessment.

03 SKILL.md 正文

Overview

Sea level is rising from thermal expansion, melting glaciers and ice sheets, and changing land water storage — but "global mean" hides enormous local variation. This skill covers the budget components, observation systems (tide gauges, altimetry, gravimetry), projection methods, and how to compute relative sea level for a specific coastline.

When to use

  • Assessing coastal flood risk or planning coastal infrastructure
  • Interpreting IPCC sea-level projections for a specific location
  • Distinguishing global, regional, and local (relative) sea-level change
  • Evaluating claims about acceleration, ice-sheet collapse, or "sunken" islands
  • Communicating sea-level science to planners and the public

Core concepts

  • The budget: thermal expansion (~40% of recent rise) + glaciers + Greenland + Antarctica + land-water storage = observed rise; closure of the budget (within uncertainties) is the field's consistency check.

  • Global mean (GMSL): ~3–4 mm/yr in the satellite era, accelerating; tide gauges extend the record back to the 19th century with sparser coverage.

  • Relative sea level (RSL): what a coastline experiences = GMSL + regional ocean dynamics + vertical land motion (subsidence/uplift, glacial isostatic adjustment). Subsiding deltas can see 10× the global rate.

  • Gravitational fingerprints: melting ice sheets redistribute mass, changing Earth's gravity field and rotation — sea level actually falls near a melting ice sheet and rises disproportionately far away.

  • Projections: process-based (ice-sheet models, emulators) vs semi-empirical; structured expert judgment for low-confidence/high-impact ice-sheet processes (marine ice-cliff instability); deep uncertainty beyond 2050, dominated by Antarctica.

  • Extremes, not means: coastal damage comes from extreme sea levels (tide + surge + waves + mean rise); a small mean rise sharply increases the frequency of historically rare flood levels.

  • Paleo sea-level constraints: last-interglacial (~125 kyr ago) sea level was 6–9 m higher with similar-to-modest warming — the geological existence proof that meters of rise are in Earth's repertoire.

  • Ice-sheet tipping language: "tipping point" implies irreversibility on human timescales — West Antarctic retreat may be committed but plays out over centuries; distinguish committed change from imminent catastrophe.

  • Nuisance flooding: sunny-day/high-tide flooding is the present-tense face of sea-level rise — its rapidly growing frequency is often more persuasive (and more plannable) than 2100 projections.

Practical workflow

1. Observe: build the local record

  1. Get tide-gauge data (PSMSL); check datum continuity, record length (≥30 years for a trend), and known jumps.
  2. Complement with satellite altimetry (TOPEX/Jason/Sentinel-6) for the offshore signal since 1993.
  3. Estimate vertical land motion: continuous GNSS co-located with the gauge, or InSAR for spatial patterns — never assume the land is stable.

2. Attribute the components

  1. Compare the local trend with GMSL; the residual is regional dynamics + land motion.
  2. Use GRACE/GRACE-FO gravimetry for ice-sheet and glacier mass loss; Argo for thermosteric expansion.
  3. Check the budget closes: components should sum to the observed trend within uncertainties — persistent misclosure means a missing process or bad data.

3. Project local relative sea level

  1. Start from probabilistic global projections (IPCC AR6 / NASA sea-level tool) for the scenario set of interest.
  2. Downscale: apply regional ocean-dynamic patterns from CMIP ensembles and gravitational fingerprints per ice-sheet source.
  3. Add local vertical land motion (extrapolated GNSS rate, with uncertainty) — in subsiding cities this dominates the 21st-century signal.
  4. Present as probability distributions over time, not single lines; show multiple scenarios.

4. Translate to flood risk

  1. Combine RSL projections with extreme-value analysis of storm tides (tide + surge) — compute how the return period of today's 100-year flood level shrinks.
  2. Note threshold behavior: flood frequency grows faster than linearly with mean rise.
  3. Communicate with scenarios + time horizons planners use (e.g., 2050/2100, low/high) and the deep-uncertainty caveat for ice sheets.

5. Evaluate a coastal-protection proposal

  1. Demand the design sea level: which scenario, which percentile, which year, including land motion — "designed for 1 m of rise" is meaningless without these.
  2. Check the extreme-value basis: are storm-surge statistics updated for the rising baseline, or is the 100-year level from a 1980s analysis?
  3. Require adaptive-pathways thinking: what triggers the next upgrade, and is the design compatible with higher-end ice-sheet outcomes?

6. Quick-reference checklist

  • [ ] Local tide-gauge record checked (≥30 years, datum continuity)
  • [ ] Vertical land motion estimated (GNSS/InSAR) — never assumed zero
  • [ ] Global, regional-dynamic, and land-motion components separated
  • [ ] Budget closure checked (components sum to observed trend)
  • [ ] Projections localized (fingerprints + regional dynamics + land motion)
  • [ ] Multiple scenarios shown as distributions, not single lines
  • [ ] Mean rise translated into extreme-flood frequency change
  • [ ] Deep ice-sheet uncertainty communicated, not hidden

Common pitfalls

  • Global number, local plan: applying 3.7 mm/yr to a subsiding delta underestimates risk by an order of magnitude — always localize.
  • Ignoring land motion: tide gauges measure relative sea level; without GNSS you can't separate ocean rise from sinking land.
  • Linear extrapolation: sea-level rise is accelerating and scenario-dependent — straight-line extension of the past misleads.
  • Conflating erosion with sea-level rise: beaches erode from sediment-budget changes too; attribute carefully before prescribing.
  • Overconfident long-term numbers: beyond ~2050, Antarctic dynamics dominate uncertainty — present ranges and storylines, not false precision.
  • Mean-only thinking: stakeholders care about flood frequency; always translate mean rise into extreme-event frequency change.
  • Bathtub-model flooding: flat "inundation maps" ignore defenses, drainage, and groundwater — they overstate some risks and miss others (like septic-system failure from rising water tables).
  • Attributing every coastal problem to sea-level rise: erosion, subsidence from groundwater pumping, and sediment starvation often dominate locally — fix the attribution before prescribing the remedy.

04 同仓库更多 Skills

TanNhatCMS
TanNhatCMS/jarvis

web-scrape

Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open/fetch fails on JS-heavy pages, or when you need clean markdown/structured extraction from a site. Requires FIRECRAWL_API_KEY.

★ 0
TanNhatCMS
TanNhatCMS/jarvis

design-taste-frontend

tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML/CSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, "AI-made", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.

★ 0
TanNhatCMS
TanNhatCMS/jarvis

test-driven-development

Use when implementing any feature or bugfix, before writing implementation code

★ 0
TanNhatCMS
TanNhatCMS/jarvis

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

★ 0
TanNhatCMS
TanNhatCMS/jarvis

requesting-code-review

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

★ 0
TanNhatCMS
TanNhatCMS/jarvis

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).

★ 0