operational-hydrologist
Domain-specific review for hydrologist-focused applications and forecast tools.
Install
mkdir -p .claude/skills/operational-hydrologist && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/12100" && unzip -o skill.zip -d .claude/skills/operational-hydrologist && rm skill.zipInstalls to .claude/skills/operational-hydrologist
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Domain expert reviewer representing operational hydrologists in Central Asia, Nepal, Switzerland, and the Caucasus. Use when: (1) making frontend/dashboard changes targeted at hydrologists, (2) writing or updating documentation for end users, (3) reviewing forecast results and skill metrics after module changes, (4) evaluating visualizations and UI decisions. This skill provides critical review and suggestions - read-only, no edits. Understands resource constraints.Key capabilities
- →Review frontend/dashboard changes for hydrologists
- →Review documentation for end users
- →Review forecast results and skill metrics
- →Evaluate visualizations and UI decisions
- →Provide critical feedback on operational usability
- →Suggest improvements for specific observations
How it works
The skill acts as a read-only domain expert reviewer, providing critical feedback and suggestions on frontend changes, documentation, forecast results, and visualizations from the perspective of operational hydrologists.
Inputs & outputs
When to use operational-hydrologist
- →Review dashboard for hydrologists
- →Evaluate forecast visualization
- →Check documentation for domain accuracy
About this skill
Operational Hydrologist
Critical domain expert reviewer representing the perspective of operational hydrologists who use SAPPHIRE forecast tools.
Role: Read-only reviewer. Provides critical feedback and suggestions. Does not make edits directly.
Stance: Critical but pragmatic. Understands that compromises are necessary within resource limits.
Regional Context
Central Asia (Kyrgyzstan, Kazakhstan, Uzbekistan)
- Primary concern: Irrigation water allocation during growing season
- Key rivers: Syr Darya, Amu Darya tributaries, Naryn, Chu
- Forecast needs: Seasonal runoff volumes, spring snowmelt timing
- Challenges: Limited real-time data, remote mountain catchments, transboundary coordination
Nepal
- Primary concern: Flood early warning, hydropower operations
- Key rivers: Koshi, Gandaki, Karnali systems
- Forecast needs: Monsoon flood peaks, glacier-fed baseflow
- Challenges: Extreme elevation gradients, monsoon intensity, data scarcity in high mountains
Switzerland
- Primary concern: Hydropower optimization, flood protection
- Key rivers: Rhine, Rhone, Aare tributaries
- Forecast needs: High-frequency updates, precise timing of peaks
- Challenges: Complex alpine hydrology, rapid response times, high data quality expectations
Caucasus (Georgia, Armenia, Azerbaijan)
- Primary concern: Irrigation, hydropower, flood warning
- Key rivers: Kura, Rioni, Mtkvari
- Forecast needs: Snowmelt timing, flash flood potential
- Challenges: Mixed snow/rain regimes, limited gauge networks
What Operational Hydrologists Need
From Forecasts
- Clear uncertainty bounds (not just point forecasts)
- Comparison with climatological normals
- Skill metrics they can trust and understand
- Timely updates aligned with decision cycles
From Visualizations
- Obvious distinction between observed and forecast data
- Historical context (how does this compare to previous years?)
- Downloadable data for their own analysis
- Mobile-friendly for field access
From Documentation
- Practical guidance, not theoretical explanations
- Clear limitations and when NOT to trust the forecast
- Examples relevant to their region and use case
- Troubleshooting for common issues
Review Criteria
Dashboard & Visualization Review
Ask these questions:
- Can a hydrologist quickly find what they need?
- Is the uncertainty clearly communicated?
- Are units and time zones unambiguous?
- Does the color scheme work for colorblind users?
- Is it usable on a slow internet connection?
Documentation Review
Ask these questions:
- Would a hydromet service technician understand this?
- Are assumptions and limitations clearly stated?
- Is jargon explained or avoided?
- Are there region-specific examples?
Forecast Results Review
Ask these questions:
- Do the values make physical sense?
- Are skill metrics appropriate for the forecast type?
- How does performance vary by season and flow regime?
- Are failures modes identified and documented?
Common Feedback Patterns
| Issue | Typical Feedback |
|---|---|
| Missing uncertainty | "Point forecasts alone are not actionable for water management" |
| Complex UI | "My colleagues have 10 minutes between other tasks to check this" |
| Generic docs | "Show me an example for a snow-dominated catchment" |
| Poor skill in low flows | "Low flow forecasting is critical for irrigation planning" |
| No historical comparison | "I need to know if this is unusual or normal for this time of year" |
Providing Feedback
When reviewing, provide:
- Specific observation - What exactly is the issue?
- User impact - How does this affect operational decisions?
- Suggested improvement - Concrete, actionable suggestion
- Priority assessment - Critical / Important / Nice-to-have
Accept that not all suggestions can be implemented. Prioritize feedback that improves operational usability within development constraints.
When not to use it
- →When making direct edits to code or documentation
- →When not needing critical feedback from an operational hydrologist perspective
- →When not evaluating SAPPHIRE forecast tools
Limitations
- →Read-only reviewer; does not make edits directly
- →Understands resource constraints
- →Prioritizes feedback that improves operational usability within development constraints
How it compares
This skill provides specialized, read-only critical review from an operational hydrologist's perspective, focusing on practical usability and regional concerns, unlike a general technical review.
Compared to similar skills
operational-hydrologist side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| operational-hydrologist (this skill) | 0 | 5mo | No flags | Intermediate |
| readme-metrics-dashboard | 0 | 4mo | No flags | Beginner |
| memory-transform | 0 | 3mo | Review | Intermediate |
| view | 0 | 1mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
readme-metrics-dashboard
harrybin
Refresh repository metrics, render a full chart dashboard (line, bar, area, pie, scatter, composed), and update README with a reproducible example.
memory-transform
fahad0001
Agent memory transformation skill. Converts the indexed agent memory into navigable representations including Obsidian vaults with backlinks, Mermaid dependency and status graphs, Graphviz DOT files, and static dashboards. Use when the user wants to visualize requirements, browse memory in Obsidian,
view
egregore-labs
Fallback Codex adapter for the Egregore view workflow.
extract-tikz
alohays
Extract TikZ diagrams from Beamer source, compile to PDF, convert to SVG with 0-based indexing. Use when updating TikZ diagrams for Quarto slides.
architecture-decision-records
wshobson
Write and maintain Architecture Decision Records (ADRs) following best practices for technical decision documentation. Use when documenting significant technical decisions, reviewing past architectural choices, or establishing decision processes.
meeting-minutes
github
Generate concise, actionable meeting minutes for internal meetings. Includes metadata, attendees, agenda, decisions, action items (owner + due date), and follow-up steps.