Sub-skill of gis-informed-workflow: 4. FAILURE DIAGNOSIS.
Scanned 9/9/2026
Install to Claude Code
Skills Directorynpx -y skills add vamseeachanta/workspace-hub --skill 4-failure-diagnosis --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of 4 Failure Diagnosis?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/vamseeachanta-4-failure-diagnosis-d03fc651)More formats (shields.io, HTML) on the badges page.
---
name: gis-informed-workflow-4-failure-diagnosis
description: 'Sub-skill of gis-informed-workflow: 4. FAILURE DIAGNOSIS.'
version: 1.0.0
category: engineering/gis
type: reference
scripts_exempt: true
---
# 4. FAILURE DIAGNOSIS
## 4. FAILURE DIAGNOSIS
| Error | Cause | Fix |
|-------|-------|-----|
| Depth profile shows `nan` values | Route extends beyond bathymetry grid | Expand GEE export bounds; check route CRS matches raster CRS |
| Route has gaps / discontinuities | Source shapefile multi-part geometry | Explode and sort by chainage; use `gpd.explode()` |
| Metocean extraction returns all zeros | Wrong variable name in NetCDF | Inspect `ds.data_vars` |
| OrcaFlex environment YAML fails validation | Depth profile non-monotonic | Sort profile by chainage; remove duplicate distances |
| Wells fall outside lease block | CRS mismatch | Ensure both layers in same CRS before `sjoin` |
| GEE export empty | AOI too small at requested scale | Reduce scale to match AOI size |
---
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Understand the components, mechanics, and constraints of context in agent systems. Use when designing agent architectures, debugging context-related failures, or optimizing context usage.
Draft release notes and changelog entries from git history or merged PRs between two refs (tags/SHAs/branches), including breaking changes, migrations, and upgrade steps. Use when the user asks for release notes, changelog updates, or a GitHub Release draft.
Documentation style guide enforcer by @planetabhi. Applies and reviews the writing style guide when authoring or editing product documentation and tutorials. Use to check prose for voice, tense, word choice, inclusive language, formatting, code block, UI, Markdown, and number/date conventions.
Quick-reference card for all caveman modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /caveman-help, "caveman help", "what caveman commands", "how do I use caveman".
Explain how claude-mem captures observations, when memory injection kicks in, and where data lives. Use when the user asks "how does claude-mem work?" or "what is this thing doing?".
