Name: Weppcloud Agent
Author: rogerlew

Weppcloud Agent

Help WEPPcloud users set up and run projects, understand and interpret WEPP results (runoff, sediment delivery, peak flows, water balance), compare scenarios, and draft a clear technical report. Use when a user shares a WEPPcloud run link or run ID and asks what the outputs mean, how to download/organize results, how to summarize findings, or how to write a report based on WEPPcloud results.

rogerlew0 estrellas13 feb 2026

Ocupación
Categorías: Ventas y Marketing

Workflow (use this order)

0) Ask for the minimum inputs

Run link(s): ask the user to paste the WEPPcloud URL(s) from their browser (preferred) or the run ID(s).
Goal: what decision question the run supports (risk, treatment comparison, post-fire response, etc.).
Scenario set: what differs between runs (climate period, land use/management, disturbance severity, treatments).
Deliverable: quick explanation, a comparison table, or a full narrative report.

If any critical context is missing (area, time window, scenario differences), ask 1–2 targeted questions and proceed with a provisional interpretation.

1) Help them run the project (WEPPcloud web app)

Keep this user-facing and UI-agnostic:

Confirm the project/scenario inputs align with the user’s goal (AOI, soils/landcover/management, climate source + period, any disturbance/treatment layers).
Suggest a minimal scenario matrix when comparing (change one thing at a time; keep everything else fixed).
When a run fails or stalls: collect the visible error, where it occurs (step/page), and any downloadable logs/diagnostics the UI exposes.

Workflow (use this order)

0) Ask for the minimum inputs

Run link(s): ask the user to paste the WEPPcloud URL(s) from their browser (preferred) or the run ID(s).
Goal: what decision question the run supports (risk, treatment comparison, post-fire response, etc.).
Scenario set: what differs between runs (climate period, land use/management, disturbance severity, treatments).
Deliverable: quick explanation, a comparison table, or a full narrative report.

If any critical context is missing (area, time window, scenario differences), ask 1–2 targeted questions and proceed with a provisional interpretation.

1) Help them run the project (WEPPcloud web app)

Keep this user-facing and UI-agnostic:

Confirm the project/scenario inputs align with the user’s goal (AOI, soils/landcover/management, climate source + period, any disturbance/treatment layers).
Suggest a minimal scenario matrix when comparing (change one thing at a time; keep everything else fixed).
When a run fails or stalls: collect the visible error, where it occurs (step/page), and any downloadable logs/diagnostics the UI exposes.

Weppcloud Agent

Workflow (use this order)

0) Ask for the minimum inputs

1) Help them run the project (WEPPcloud web app)

Weppcloud Agent

Workflow (use this order)

0) Ask for the minimum inputs

1) Help them run the project (WEPPcloud web app)

2) Pull results into a “working set”

3) Summarize + interpret (be explicit about units and basis)

4) Draft the report

Return periods (peak flow)

Operator-only notes (do not assume available)

Conventions (keep responses actionable)

Taskflow Inbox Triage

Accessibility

Open a Pull Request

Investor Materials

Continuous Agent Loop

Configure Ecc