Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
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

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

E1004 Geomag

ASecurity

Use when defining the geomagnetic field environment model for a mission under ECSS-E-ST-10-04C: select the applicable geomagnetic field model (an IGRF-class internal field model alone at low/mid geocentric distance, or that model combined with an external/magnetospheric field model at high geocentric distance) from the mission orbit's geocentric distance, determine the correct IGRF epoch and apply secular variation to update the reference internal field for the mission's target date, verify t...

2 stars
0 votes
0 copies
0 views
Added 9/27/2026
ai-agentspythonshellexpress

Works with

claude code

Security Analysis

A100/100

Scanned 9/27/2026

Install to Claude Code

$npx -y skills add ashfordeOU/aero-agent-skills --skill e1004-geomag --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of E1004 Geomag?

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

Security grade badge for E1004 Geomag
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ashfordeou-e1004-geomag/badge)](https://www.skillsdirectory.com/skills/ashfordeou-e1004-geomag)

More formats (shields.io, HTML) on the badges page.

Download with Pro
Files
SKILL.md
---
name: e1004-geomag
description: "Use when defining the geomagnetic field environment model for a mission under ECSS-E-ST-10-04C: select the applicable geomagnetic field model (an IGRF-class internal field model alone at low/mid geocentric distance, or that model combined with an external/magnetospheric field model at high geocentric distance) from the mission orbit's geocentric distance, determine the correct IGRF epoch and apply secular variation to update the reference internal field for the mission's target date, verify the target date remains within the secular-variation extrapolation validity window, compute the dipole-approximation B,L equatorial field magnitude for radiation-belt characterization, and validate that the analysis case's declared model and epoch handling meet these requirements. Trigger: geomagnetic field, IGRF, secular variation, B L coordinates, magnetospheric field, external field model, Tsyganenko, dipole approximation, e-st-10-04, ecss, space environment."
license: Apache-2.0
compliance: STANDARDS-REF
standards:
  - id: ecss
    reference-only: true
gated: false
domain: space-systems
pack: space-systems
compatibility: "agentskills.io SKILL.md; any SKILL.md host (Claude Code, Hermes, OpenClaw)"
metadata:
  domain: space-systems
  subdomain: ecss
  tags: [ecss, e-st-10-04c, geomag, igrf, secular-variation, b-l-coordinates, external-field, space-environment]
  version: 0.1.0
  author: Aero Agent Skills
---

# ECSS Geomagnetic Field Environment (space-systems/ecss/e1004-geomag)

Use when the task is selecting and applying a geomagnetic field model
under ECSS-E-ST-10-04C clause 5.2, to characterize the Earth's
internal magnetic field (and, where applicable, the external
magnetospheric contribution) for a mission orbit, including epoch
selection, secular-variation handling, and B,L coordinate usage.

## Domain quick reference

- The geomagnetic field has an internal (core-origin) component and
  an external (magnetospheric) component. The internal component
  dominates at low and mid geocentric distance and is well
  represented by an IGRF-class spherical-harmonic model alone. At
  high geocentric distance -- approaching and beyond the magnetopause
  region -- the external/magnetospheric contribution (solar-wind
  interaction, ring current, tail currents) becomes significant and
  an internal-only model understates the actual field; an external
  field model (e.g. a Tsyganenko-class model) must be added.
  Geomagnetic shielding of incident particle flux (Stormer cutoffs) is
  the sibling e1004-stormer leaf; trapped-belt long-term flux models
  are the sibling e1004-trapped-leo leaf -- both consume the field
  geometry this leaf characterizes rather than redefining it.
- IGRF-class models are published as spherical-harmonic (Gauss)
  coefficient sets at fixed 5-year epochs, each accompanied by a
  secular-variation (SV) coefficient set describing the field's
  linear rate of change. Coefficients between two published epochs
  are interpolated; coefficients for dates after the latest published
  epoch are extrapolated by applying the SV rate, and that
  extrapolation is only certified accurate for a bounded number of
  years (nominally the 5 years following the latest epoch) until the
  next IGRF generation is released.
- B,L coordinates express a field point by the local field magnitude
  B and the McIlwain L-shell parameter; L labels the dipole field
  line the point lies on and is the standard coordinate for
  characterizing trapped-radiation-belt structure. A dipole
  approximation gives the equatorial field magnitude on a given
  L-shell as the epoch equatorial surface field strength divided by L
  cubed.
- This leaf scopes internal/external model selection by geocentric
  distance regime, IGRF epoch and secular-variation handling, and the
  B,L dipole-approximation field computation only. It does not
  implement the full spherical-harmonic synthesis of the real IGRF
  coefficient set -- that is an external reference implementation
  (see the informative e1004-ref-geomag reference-data leaf) -- nor
  does it compute Stormer cutoffs or belt fluxes.

## Workflow

1. For each geomagnetic analysis case, record its case id, the
   mission orbit's geocentric distance (Earth radii), the target
   date (decimal year) the field is needed for, the model the
   analysis declares it used, the epoch equatorial surface field
   strength (B0) for the nearest IGRF epoch, and the secular-variation
   rate for that epoch.
2. Classify the case's geocentric distance into a field regime:
   "internal_only" at or below the internal/external threshold
   distance, "internal_plus_external" above it.
3. Select the model required for that regime (IGRF-class internal
   field model alone, or that model combined with an
   external/magnetospheric field model) and compare it against the
   case's declared model; flag a mismatch rather than accepting an
   internal-only analysis at high geocentric distance.
4. Determine the nearest IGRF epoch at or before the target date and
   the elapsed time since that epoch; verify the target date falls
   within the secular-variation extrapolation validity window
   (target date not before the earliest published epoch, and not more
   than the extrapolation limit beyond the latest published epoch).
5. Apply secular variation: scale the epoch equatorial field strength
   by the secular-variation rate over the elapsed time to obtain the
   field strength applicable to the target date.
6. Where a case supplies an L-shell value, compute the dipole
   equatorial field magnitude at that L-shell from the
   secular-variation-adjusted equatorial field strength.
7. Mark the case compliant only when its declared model matches the
   regime's required model and its target date is within the epoch
   validity window; roll every case's compliance into the assessment
   record and do not close the geomagnetic field model definition
   while any case remains non-compliant.

## Pitfalls

- Using an internal-only IGRF model for a high-altitude or
  magnetopause-adjacent orbit instead of adding the
  external/magnetospheric contribution, understating the actual field
  (and, downstream, misjudging particle trajectories that depend on
  it).
- Applying secular variation beyond its certified extrapolation
  window instead of flagging that a newer IGRF generation is needed,
  silently carrying growing error into the field estimate the further
  the target date drifts past the latest published epoch.
- Treating the B,L dipole approximation as exact near the real,
  non-dipolar field (e.g. in the South Atlantic Anomaly) rather than
  as a simplified coordinate for belt characterization only.
- Selecting an epoch by nearest calendar rounding instead of the
  correct interpolation/extrapolation rule, which silently drops the
  secular-variation correction that dominates the difference between
  adjacent epochs.

## Behavior contract (gate 3)

The regime classification, model-selection, IGRF epoch validity,
secular-variation, and B,L field-computation logic is exercised by
the gate 3 contract test: scripts/test_e1004_geomag.py against
scripts/e1004_geomag_logic.py (stdlib unittest, offline). Run:
python3 scripts/test_e1004_geomag.py

## Compliance

- ECSS standards are freely downloadable (ESA); cite the source and
  paraphrase per standards-map.yaml.
- compliance: STANDARDS-REF, gated: false.

Attribution

ashfordeOUashfordeOU
View sourceMore from ashfordeOU →
SSkills DirectorySkills Directory

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

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

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

Related Skills

Caveman

Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy. Levels: lite, full, ultra and the wenyan variants. Use for /caveman, "caveman mode", "talk like caveman", "be brief" or "less tokens".

1074701 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', ...

694821 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.

3351 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, 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.

691 votes

math-skill

A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling

381 votes
View all in ai-agents →