Agent skill · Data & Analytics

harmonica

Gravity and magnetic data processing and forward modelling using Fatiando a Terra. Use when Claude needs to: (1) Compute gravity forward models (point masses, prisms, tesseroids), (2) Apply terrain/Bouguer corrections, (3) Grid scattered potential field data with equivalent sources, (4) Perform upward/downward continuation, (5) Calculate magnetic anomalies from magnetized bodies, (6) Apply derivative filters (gradients, tilt angle), (7) Process regional or local gravity surveys.

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill harmonica --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 7 KB
Bundled scripts: none
Version: 1.0.0
Declared author: Geoscience Skills
Requires: [harmonica>=0.6.0, numpy, verde]
Path: skills/analysis/harmonica/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Harmonica - Gravity and Magnetics ## Quick Reference ```python import harmonica as hm import numpy as np # Forward model - prism gravity prism = [-500, 500, -500, 500, -2000, -500] # (west, east, south, north, bottom, top) gravity = hm.prism_gravity(coordinates, prism, density=500, field='g_z') # Terrain correction layer = hm.prism_layer((easting, northing), surface=topo, reference=0, properties={'density': 2670}) terrain_effect = layer.gravity(coordinates, field='g_z') # Equivalent source gridding eqs = hm.EquivalentSources(depth=10000, damping=10) eqs.fit(coordinates, gravity_data) grid = eqs.grid(spacing=5000, data_names=['gravity']) # Upward continuation (requires gridded xarray) upward = hm.upward_continuation(gravity_grid, height_displacement=1000) ``` ## Key Functions | Function | Purpose | |----------|---------| | `point_gravity` | Gravity from point masses | | `prism_gravity` | Gravity from rectangular prisms | | `tesseroid_gravity` | Gravity from spherical prisms (regional/global) | | `prism_magnetic` | Magnetic anomaly from prisms | | `prism_layer` | Create layer of prisms from topography | | `EquivalentSources` | Grid scattered data with equivalent sources | | `upward

What's inside
Steps it walks through
  1. Quick Reference
  2. Key Functions
  3. Essential Operations
  4. Forward Model - Rectangular Prism
  5. Terrain Correction
  6. Equivalent Source Gridding
  7. Magnetic Forward Model
  8. Derivative Filters
  9. Coordinate System
  10. When to Use vs Alternatives
  11. Common Workflows
  12. Process Gravity Survey with Terrain Correction and Gridding
  13. Common Issues
  14. Tips
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the harmonica skill do?

Gravity and magnetic data processing and forward modelling using Fatiando a Terra. Use when Claude needs to: (1) Compute gravity forward models (point masses, prisms, tesseroids), (2) Apply terrain/Bouguer corrections, (3) Grid scattered potential field data with equivalent sources, (4) Perform upward/downward continuation, (5) Calculate magnetic anomalies from magnetized bodies, (6) Apply derivative filters (gradients, tilt angle), (7) Process regional or local gravity surveys.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill harmonica --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going