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 Trapped Other

ASecurity

Use when determining how the trapped-radiation environment applies to a non-LEO/GEO/MEO orbit (HEO, GTO, interplanetary transfer) under ECSS-E-ST-10-04C: determine the orbit regime from perigee/apogee altitude, split the trajectory into segments inside versus beyond the geomagnetically trapped domain using the magnetopause standoff distance, verify both trapped species (proton and electron) are covered wherever trapped-domain dwell exists, and hand off out-of-domain segments to the interplane...

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

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-trapped-other --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of E1004 Trapped Other?

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

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

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

Download with Pro
Files
SKILL.md
---
name: e1004-trapped-other
description: "Use when determining how the trapped-radiation environment applies to a non-LEO/GEO/MEO orbit (HEO, GTO, interplanetary transfer) under ECSS-E-ST-10-04C: determine the orbit regime from perigee/apogee altitude, split the trajectory into segments inside versus beyond the geomagnetically trapped domain using the magnetopause standoff distance, verify both trapped species (proton and electron) are covered wherever trapped-domain dwell exists, and hand off out-of-domain segments to the interplanetary radiation leaves rather than silently dropping them. Trigger: HEO, GTO, geostationary transfer orbit, highly elliptical orbit, interplanetary trajectory, escape trajectory, trapped radiation, magnetopause standoff, Van Allen belt crossing, e-st-10-04, ecss, space environment, radiation 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, trapped-radiation, heo, gto, interplanetary, magnetopause, radiation-environment]
  version: 0.1.0
  author: Aero Agent Skills
---

# ECSS Trapped Radiation Environment for Other Orbits (space-systems/ecss/e1004-trapped-other)

Use when the task is categorizing the trapped-radiation environment under
ECSS-E-ST-10-04C clause 9.2 for a mission orbit that does not sit wholly
inside a single trapped-belt region already covered by a dedicated leaf --
highly elliptical orbits (HEO), geostationary transfer orbits (GTO), and
trajectories that eventually leave the magnetosphere entirely
(interplanetary transfer, lunar transfer, escape trajectories).

## Domain quick reference

- The dedicated sibling leaves (`e1004-trapped-leo`, `e1004-meo-meov2`,
  and the GEO leaf) each assume the spacecraft stays within one
  characteristic band of the trapped-belt structure for the whole orbit.
  HEO and GTO instead sweep radially through the slot region, the outer
  electron belt, and the inner proton belt on every revolution, and an
  interplanetary transfer additionally leaves the trapped-belt structure
  behind entirely partway through the mission.
- The Earth's magnetosphere -- and with it the trapped-radiation
  population -- does not extend indefinitely. Its outer boundary, the
  magnetopause, sits at a nominal subsolar standoff distance on the
  order of 10 Earth radii, compressed to roughly 6 Earth radii or less
  under strong solar-wind/storm forcing. Beyond that boundary there is
  no trapped population to characterize; the applicable environment
  becomes the interplanetary one (GCR, SEP -- see the sibling
  `e1004-gcr` and SEP leaves), not a trapped-belt model.
- A trajectory segment's dwell must therefore be split into two
  domains: inside the magnetopause standoff distance ("trapped
  domain", where a trapped-belt flux model applies) and outside it
  ("interplanetary domain", where it does not). Treating a
  beyond-magnetopause segment as still trapped overstates trapped dose;
  silently dropping it instead of handing it to the interplanetary
  leaves understates total mission radiation exposure.
- Wherever trajectory dwell falls inside the trapped domain, both
  trapped species -- proton and electron -- must be covered by the
  analysis, since HEO/GTO/interplanetary-transfer trajectories cross
  both the proton and electron belt structure on every pass through the
  trapped domain, unlike an orbit confined to a single belt where one
  species can sometimes dominate.
- This leaf scopes orbit-regime categorization, trapped-domain segment
  splitting against the magnetopause boundary, and required-species
  coverage verification only. Per-segment flux/fluence table lookup for
  the crossed L-shells is the same interpolation problem already solved
  by the LEO/MEO/GEO leaves and should be reused per segment, not
  reimplemented here.

## Workflow

1. Record the mission's perigee and apogee altitude (apogee `None` for
   an escape/hyperbolic trajectory with no bounded apogee), and whether
   the assessment should use the nominal or storm-compressed
   magnetopause standoff distance.
2. Categorize the orbit regime from perigee/apogee altitude: reject
   (and redirect to the dedicated leaf) an orbit that lies wholly
   within the LEO, MEO, or GEO band; otherwise categorize it as `"gto"`
   (low perigee, apogee near the geosynchronous band), `"heo"` (apogee
   above the geosynchronous band), or `"interplanetary_transfer"`
   (unbounded apogee).
3. Break the trajectory into radial-distance/dwell-time segments (one
   per sampled point along the orbit or transfer trajectory) and split
   their total dwell time into trapped-domain seconds and
   interplanetary-domain seconds using the magnetopause standoff
   distance for the chosen (nominal or compressed) solar-wind
   condition.
4. Feed each trapped-domain segment's radial distance (converted to
   McIlwain L-shell) into the same per-L-shell flux interpolation used
   by the LEO/MEO/GEO leaves to get its differential flux, then
   dwell-time-weight across the trapped-domain segments the same way
   the MEO leaf dwell-weights L-shell crossings.
5. Verify that both required trapped species (proton and electron) are
   covered by the analysis case wherever trapped-domain dwell is
   nonzero; flag missing species coverage as a finding rather than
   silently omitting one species from the resulting spectrum.
6. Route every interplanetary-domain segment's dwell time to the
   interplanetary radiation leaves (GCR, SEP) instead of discarding it,
   and record the excluded-segment count so the hand-off is auditable.
7. Mark the mission's trapped-environment assessment compliant only
   when the orbit regime was successfully categorized, at least one
   trajectory segment was supplied, and no required-species-coverage
   finding remains open.

## Pitfalls

- Applying a single-L-shell LEO/MEO/GEO flux lookup to a GTO/HEO orbit
  without dwell-time weighting across the full range of L-shells it
  crosses each revolution, which misrepresents both the flux magnitude
  and which belt region dominates.
- Treating trajectory dwell beyond the magnetopause standoff distance
  as still part of the trapped-belt population, overstating trapped
  proton/electron dose for the mission's interplanetary-transfer
  segments.
- Silently dropping beyond-magnetopause dwell time instead of routing
  it to the GCR/SEP leaves, which understates total mission radiation
  exposure even though the trapped-belt contribution for that segment
  is correctly excluded.
- Using the nominal (uncompressed) magnetopause standoff distance for a
  worst-case radiation design margin instead of the storm-compressed
  distance, which understates trapped-domain dwell time for segments
  near the nominal boundary.
- Covering only the proton or only the electron trapped population for
  an HEO/GTO/interplanetary-transfer trajectory, when both belts are
  crossed on every pass through the trapped domain.

## Behavior contract (gate 3)

The orbit-regime categorization, magnetopause-domain segment splitting,
and required-species-coverage logic is exercised by the gate 3 contract
test: scripts/test_e1004_trapped_other.py against
scripts/e1004_trapped_other_logic.py (stdlib unittest, offline). Run:
python3 scripts/test_e1004_trapped_other.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 →