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 Maint Stations

ASecurity

"Use when design physical maintenance stations for a crewed spacecraft

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

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-maint-stations --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of E1011 Maint Stations?

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

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

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

Download with Pro
Files
SKILL.md
---
name: e1011-maint-stations
description: "Use when design physical maintenance stations for a crewed spacecraft
  per ECSS-E-ST-10-11C §4.7.8: verify that each station's access zone meets minimum
  reach depth, lateral clearance, and vertical clearance thresholds for intravehicular,
  extravehicular, or hybrid zone types; confirm that registered tools are compatible
  with the station zone type and that large-envelope single-hand tools are flagged
  for operating-arc review; validate that lighting levels meet the minimum lux
  requirement for the zone; and categorize all maintenance tasks by frequency and
  zone type while flagging tasks that reference tools not on record at the station.
  Trigger: ecss, e-st-10-system-scope, maintenance-stations, access-zone, workspace,
  tooling, lighting, human-factors."
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, maintenance-stations, access-zone, workspace, tooling, human-factors]
  version: 0.1.0
  author: Aero Agent Skills
---

# ECSS Human Factors — Physical Maintenance Stations (space-systems/ecss/e1011-maint-stations)

Use when the task is to design and verify physical maintenance stations for a
crewed spacecraft per ECSS-E-ST-10-11C §4.7.8 — establishing that each
station's spatial envelope, tooling inventory, lighting, and assigned maintenance
tasks together satisfy the human-factors requirements for crew accessibility and
task performance.

## Domain quick reference

- §4.7.8 treats each maintenance station as a bounded workspace defined by three
  axes: forward reach depth (the crewmember's working distance into the
  station), lateral clearance (the side-to-side working width), and vertical
  clearance (headroom and vertical working range). Minimum values differ by zone
  type: intravehicular activity (IVA) stations accommodate an unsuited
  crewmember, while extravehicular activity (EVA) and hybrid stations must
  accommodate a pressure-suited crewmember whose suit envelope adds to all
  dimensional requirements. HYBRID stations must meet EVA minimums and serve
  both activity modes.
- Tools used at a station must be rated for the station's zone type. A tool that
  is IVA-only cannot be assigned to an EVA or HYBRID station. Tools whose
  single-hand operating arc exceeds 300 mm must be verified for clearance or
  re-designated as two-hand operations so that the full torque arc lies within
  the station envelope.
- Lighting is a separate physical parameter: IVA stations require at least
  150 lux at the work surface; EVA stations require at least 100 lux
  (supplemented where necessary by portable or suit-mounted illumination).
  A lighting value that is absent from the station record is a non-compliant
  finding, not a pass.
- Maintenance tasks are categorized by frequency (routine, on-condition,
  corrective) and by zone type. Each task names the tools it needs; if any
  named tool is not on record at the station, the task is flagged and the
  station is not compliant until the tool is added or the task reference is
  corrected.

## Workflow

1. Inventory every maintenance station in the spacecraft layout and assign it a
   zone type (IVA, EVA, or HYBRID) based on the crew access method documented
   in the maintenance concept.
2. For each station, record the three dimensional parameters: reach depth (mm),
   lateral clearance (mm), and vertical clearance (mm). Compare each against
   the applicable threshold. Flag any axis below the minimum; EVA and HYBRID
   stations use the larger EVA thresholds on all three axes.
3. Register every tool assigned to the station. For each tool, verify it is
   rated for the station zone type. For any tool whose maximum operating
   envelope exceeds 300 mm and is not designated as a two-hand operation, raise
   a finding to verify the arc fits within the station's available clearance.
4. Record the illuminance level (lux) at the work surface. Compare against the
   zone-type minimum. A missing or unverified lighting value is a non-compliant
   finding.
5. Assign maintenance tasks to the station. Categorize each task by frequency
   and zone type. Cross-check each task's required tool list against the tools
   on record at the station; flag any task that references a tool not on record.
6. A station is compliant when all dimensional checks pass, no tooling
   incompatibilities remain, lighting is verified above the minimum, and no
   task references an unresolved tool. Aggregate the findings per station and
   resolve each before the station enters the design review.

## Pitfalls

- Applying IVA dimensional thresholds to a HYBRID station — a HYBRID station
  serves suited crewmembers and must use the larger EVA thresholds even if
  IVA access is also present.
- Treating an absent lighting record as compliant — a lighting value must be
  explicitly measured and recorded; the absence of a finding is not evidence
  of adequacy.
- Assigning a tool to a station without checking zone-type compatibility —
  a tool that works well unsuited may be unusable in a pressure suit; the
  per-tool compatibility flag must be set before the tool is accepted at a
  station.
- Leaving task-to-tool references unresolved — a task that names a tool not
  on record at the station cannot be verified as executable; this is a
  blocking finding, not a documentation gap.

## Behavior contract (gate 3)

Access zone, tooling, lighting, and task-categorization logic is exercised by
the gate 3 contract test: scripts/test_e1011_maint_stations.py against
scripts/e1011_maint_stations_logic.py (stdlib unittest, offline). Run:
python3 scripts/test_e1011_maint_stations.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 →