Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Seismic Data Analysis

ASecurity

Earthquake seismology workflows — phase picking, location, magnitude, focal mechanisms, and seismic hazard basics.

2 stars
0 votes
0 copies
1 views
Added 9/29/2026
ai-agentspythonrustgo

Security Analysis

A100/100

Scanned 9/29/2026

$npx -y skills add aicodedecode/awesome-muse-skills --skill seismic-data-analysis --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Seismic Data Analysis?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Seismic Data Analysis
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/aicodedecode-seismic-data-analysis/badge)](https://www.skillsdirectory.com/skills/aicodedecode-seismic-data-analysis)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: seismic-data-analysis
description: Earthquake seismology workflows — phase picking, location, magnitude, focal mechanisms, and seismic hazard basics.
category: scientific
---

## Overview

Seismology extracts Earth's interior and earthquake physics from ground-
motion recordings. This skill covers the observational pipeline: reading
seismograms (phase identification), locating earthquakes, measuring
magnitude, determining focal mechanisms, and the basics of seismic hazard
assessment — with ObsPy as the working tool.

## When to use

- Locating earthquakes from station arrival times and building a local catalog
- Measuring magnitudes consistently and understanding their saturation limits
- Determining fault-plane solutions (focal mechanisms) from first motions or waveforms
- Processing active-source or ambient-noise data for subsurface imaging
- Assessing seismic hazard: Gutenberg–Richter, ground-motion prediction, site response

## Core concepts

- **Body waves:** P (compressional, fastest, first arrival) and S (shear, slower, larger amplitude); their differential time (S−P) gives distance — the oldest and most robust location constraint.
- **Location as inverse problem:** minimize travel-time residuals over a velocity model; depth trades off with origin time and is the worst-constrained parameter, especially outside the network.
- **Magnitude scales:** M_L (local, saturates ~M7), m_b/M_s (teleseismic body/surface wave), M_w (moment magnitude — physical, non-saturating, the standard). Never mix scales in one analysis.
- **Seismic moment and focal mechanisms:** M₀ = μAD (rigidity × area × slip); the moment tensor's double-couple part gives the beach-ball fault-plane solution — two nodal planes, one the real fault.
- **Gutenberg–Richter:** log₁₀N = a − bM; b ≈ 1 globally — the statistical backbone of hazard; catalog completeness magnitude M_c must be established before fitting.
- **Site response:** soft soils amplify shaking (and liquefy); bedrock motion ≠ surface motion — hazard without site terms misleads.

- **Array methods:** beamforming and FK analysis use wavefront coherence across stations — slowness and back-azimuth from arrays locate events with few stations and characterize wavefields single stations can't.
- **Receiver functions:** P-to-S conversions at interfaces image crustal and mantle discontinuities — a passive, cheap alternative to active-source profiling for Moho depth and crustal structure.
- **Ambient-noise tomography:** cross-correlating background noise between station pairs extracts surface-wave Green's functions — velocity models without earthquakes, from whatever stations exist.

## Practical workflow

### 1. From waveforms to picks

```python
from obspy import read
from obspy.signal.trigger import classic_sta_lta
st = read("station.mseed")
# Filter, then STA/LTA or AIC pickers for P; verify S by polarization/rotation
```

1. Preprocess: detrend, taper, bandpass appropriate to the distance (local: 1–20 Hz; teleseismic: 0.01–1 Hz).
2. Pick P with STA/LTA or kurtosis/AIC pickers; pick S on rotated horizontal components — verify every automatic pick visually for events that matter.
3. Assign pick weights by quality; a few good picks beat many bad ones.

### 2. Locate

1. Use a calibrated 1D velocity model for the region (or 3D if available); start locations from S−P distances.
2. Invert with a standard locator; inspect residuals — systematic residuals at one station mean a bad pick or a wrong model, not a bad event.
3. Report uncertainties honestly: formal errors understate true uncertainty when the velocity model is wrong — bootstrap or perturb the model for realistic bounds.

### 3. Measure magnitude and mechanism

1. Compute M_L from Wood-Anderson amplitudes with distance corrections; compute M_w from moment-tensor inversion or spectral fitting for significant events.
2. For focal mechanisms: first-motion polarities (needs good azimuthal coverage) or full-waveform inversion; report both nodal planes and the preferred plane with justification.
3. Check mechanism consistency with regional tectonics — a thrust mechanism in a strike-slip regime demands scrutiny, not celebration.

### 4. Hazard basics

1. Build a declustered catalog; determine M_c (maximum-curvature or goodness-of-fit); fit a- and b-values with uncertainties.
2. Apply ground-motion prediction equations (GMPEs) appropriate to the tectonic regime; include site terms (Vs30).
3. Distinguish probabilistic (PSHA: rates over time) from deterministic (scenario earthquake) hazard — they answer different engineering questions.

### 5. Build a local earthquake catalog

1. Run continuous detection (STA/LTA or template matching / ML pickers like PhaseNet) with association (REAL, GaMMA) — modern ML pickers find 5–10× more events than STA/LTA.
2. Locate with a regional 1D model first; upgrade significant events to 3D or double-difference relocation for fault-structure imaging.
3. Compute completeness (M_c) in space and time before any rate or b-value analysis — detection capability varies with network evolution.

### 6. Quick-reference checklist

- [ ] Preprocessing appropriate to epicentral distance (filter bands)
- [ ] Automatic picks visually verified for events that matter
- [ ] Velocity model appropriate to the region; residuals inspected
- [ ] Depth uncertainty assessed honestly (especially outside the network)
- [ ] Magnitude scale stated and consistent (no mixed scales)
- [ ] Catalog completeness (M_c) established before b-value fitting
- [ ] Catalog declustered before PSHA rate calculations
- [ ] Focal-mechanism preferred plane justified (aftershocks/geodesy)

## Common pitfalls

- **Mixing magnitude scales:** M_L 6.0 ≠ M_w 6.0 — catalogs mixing scales produce fake b-value kinks.
- **Trusting depth outside the network:** events outside or at the edge of the station network have essentially unconstrained depths — flag, don't publish.
- **Automatic picks without review:** a misidentified phase (e.g., depth phase as direct P) corrupts location and depth systematically.
- **Ignoring M_c:** fitting Gutenberg–Richter below completeness invents b-value variations from detection thresholds.
- **Beach-ball overinterpretation:** the auxiliary plane is not the fault — use aftershock distributions, geodesy, or directivity to choose.
- **Hazard without declustering:** aftershock sequences violate the Poisson assumption of PSHA — decluster first.
- **ML picker worship:** neural pickers are excellent but inherit training-data biases — validate against analyst picks for your region's event types before trusting the catalog.
- **Clock errors:** GPS timing failures produce systematic mislocations blamed on structure — check timing quality flags, especially for temporary deployments.

Attribution

aicodedecodeaicodedecode
View sourceSee grades on GitHubMore from aicodedecode →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698621 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →