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

E1011 Eva

ASecurity

Use when design EVA and planetary surface activity requirements for a space system under ECSS-E-ST-10-11C §4.7.10: verify suit interface compatibility (operating pressure, thermal envelope, life support endurance), assess tool design parameters (operator force limits, reach envelope, glove compatibility), evaluate crew mobility timelines and terrain trafficability, and compute consumable margins with required reserves for O2, power, and thermal control. Verify abort scenario timelines confirm...

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

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 e1011-eva --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of E1011 Eva?

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

Security grade badge for E1011 Eva
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ashfordeou-e1011-eva/badge)](https://www.skillsdirectory.com/skills/ashfordeou-e1011-eva)

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

Download with Pro
Files
SKILL.md
---
name: e1011-eva
description: "Use when design EVA and planetary surface activity requirements for a space system under ECSS-E-ST-10-11C §4.7.10: verify suit interface compatibility (operating pressure, thermal envelope, life support endurance), assess tool design parameters (operator force limits, reach envelope, glove compatibility), evaluate crew mobility timelines and terrain trafficability, and compute consumable margins with required reserves for O2, power, and thermal control. Verify abort scenario timelines confirm safe crew return within consumable limits. Trigger: ecss, e-st-10-system-scope, eva, extravehicular-activity, suit-interface, eva-tools, crew-mobility, planetary-activity, consumable-margin."
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-system-scope, eva, extravehicular-activity, suit-interface, eva-tools, crew-mobility, planetary-activity]
  version: 0.1.0
  author: Aero Agent Skills
---

# ECSS Human Factors — EVA and Planetary Surface Activity (space-systems/ecss/e1011-eva)

Use when the task is to design EVA and planetary surface activity
requirements for a space system under ECSS-E-ST-10-11C §4.7.10 --
specifying suit interfaces, EVA tool requirements, crew mobility
envelopes, consumable margins, and abort timelines.

## Domain quick reference

- EVA design covers two environments: orbital microgravity (ISS
  exterior, free-flyer) and planetary surfaces (lunar, Martian).
  Each environment drives different mobility assumptions: handrail
  translation speed and microgravity body positioning for orbital;
  suited walking speed and terrain slope limits for planetary. The
  surface type is determined before any timeline or force assessment.
- Suit interface parameters govern the physical connection between
  crew and system: the suit's operating pressure must be validated
  against the spacecraft cabin pressure to identify whether a pre-
  breathe protocol is required to mitigate decompression sickness
  risk. Life support endurance must cover the planned EVA duration
  plus a 25% reserve. Thermal operating range must bracket the
  expected environment temperatures at both extremes.
- Tool design requirements constrain force, reach, and grip. Suited
  crewmembers are limited in the force they can apply (approximately
  111 N one-handed, 222 N two-handed in typical EVA suits); any tool
  requiring a higher operator force fails the EVA design requirement.
  Reach envelopes and glove compatibility with the tool handle are
  checked separately and are both gateable.
- Consumable margins apply to O2, electrical power, and thermal
  control (metabolic heat removal). Each consumable is checked at
  end-of-EVA against a required reserve fraction (default 25%) of
  total supply. An EVA timeline that leaves any consumable below its
  reserve fraction fails the margin check.
- Abort scenario verification confirms that the crew can return to
  the airlock from the most distant worksite within the safe-return
  time limit using remaining consumables. The abort translation time
  is computed from worksite distance and surface-type translation
  speed; the remaining consumable capacity must cover that return
  duration.

## Workflow

1. Determine the surface type (microgravity, ISS exterior, lunar,
   Martian) for the EVA activity. This sets the translation speed
   and terrain slope limits used in all subsequent calculations.
2. Check suit interface compatibility: confirm that life support
   endurance covers planned duration with 25% margin; flag if suit
   operating pressure is at or above cabin pressure (pre-breathe
   protocol required); confirm environment temperatures fall within
   the suit's thermal operating range. Reject the suit if any life
   support or thermal check fails.
3. Assess each EVA tool: confirm required operator force does not
   exceed the suited operator force limit for the operation class
   (one-hand or two-hand); confirm tool reach meets the task's
   minimum reach; confirm the handle is compatible with the EVA
   pressure glove. Flag every failing parameter as a distinct issue.
4. Evaluate crew mobility: for planetary surfaces, compare terrain
   slope against the surface-type trafficability limit; compute
   estimated translation time from distance and speed; flag if
   estimated time exceeds the allowed timeline allocation.
5. Compute consumable margins at end of planned EVA duration: for
   each consumable (O2 mass, electrical energy, coolant/thermal
   capacity), subtract usage from supply and compare the remainder
   against the required reserve fraction. Flag each consumable that
   falls short.
6. Verify the abort scenario: compute return time from furthest
   worksite to airlock using the surface-type translation speed;
   confirm return time is within the abort time limit; confirm
   consumable remaining at abort trigger covers the return duration.
7. Aggregate all findings. The EVA design is compliant only when
   all suit, tool, mobility, consumable, and abort checks are clear.

## Pitfalls

- Applying ISS translation speed to a planetary surface EVA and
  underestimating return time -- suited walking on lunar or Martian
  terrain is two to four times slower than handrail translation
  in microgravity.
- Checking consumable margin against the remaining quantity at the
  abort trigger instead of at planned end-of-EVA -- the margin
  check applies to the full planned timeline; the abort check is
  a separate verification against remaining capacity at abort time.
- Treating a pre-breathe flag as non-critical -- if suit operating
  pressure is at or above cabin pressure, a pre-breathe protocol
  is operationally required and must be captured in the EVA design
  document; omitting it is a design gap, not a warning.
- Checking force against the operator maximum without also checking
  the class limit -- the suited crewmember's personal force
  capability may exceed the EVA class limit; both bounds must hold.
- Leaving terrain slope unverified for planetary EVAs because no
  specific worksite has been selected -- the design requirement must
  state the maximum slope for which the EVA is designed; if no value
  is on record, flag the gap rather than assume flat terrain.

## Behavior contract (gate 3)

The suit-interface, tool-assessment, mobility-evaluation,
consumable-margin, and abort-timeline logic is exercised by the
gate 3 contract test: scripts/test_e1011_eva.py against
scripts/e1011_eva_logic.py (stdlib unittest, offline). Run:
python3 scripts/test_e1011_eva.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 →