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 Crew Provisions

ASecurity

"Use when specifying crew station provisions under ECSS-E-ST-10C §4.7.5:

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-crew-provisions --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of E1011 Crew Provisions?

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

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

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

Download with Pro
Files
SKILL.md
---
name: e1011-crew-provisions
description: "Use when specifying crew station provisions under ECSS-E-ST-10C §4.7.5:
  identify each station by type (piloting, mission, payload, maintenance), verify
  seat dimensions against the crew anthropometric envelope, confirm restraint load
  capacities for shoulder harness, lap belt, and footrest, assess console reach and
  height against the seated crew envelope, and validate egress clearance against the
  minimum path width. Flag each station that fails a geometry, load, or clearance
  requirement before proceeding to detailed design. Trigger: ecss, e-st-10-system-scope,
  crew-stations, seat-restraints, console-layout, egress, anthropometry, crew-accommodation."
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, crew-stations, seat-restraints, console-layout, egress, anthropometry, crew-accommodation]
  version: 0.1.0
  author: Aero Agent Skills
---

# ECSS System Engineering — Crew Station Provisions (space-systems/ecss/e1011-crew-provisions)

Use when the task is specifying and verifying crew station provisions under
ECSS-E-ST-10C §4.7.5 — assigning station types, checking seat geometry and
restraint loads against the crew anthropometric envelope, validating console
reach and height, and confirming egress clearance before proceeding to
detailed design.

## Domain quick reference

- §4.7.5 requires each crew station to be categorized by function before
  dimensional requirements are applied. The recognized station types are:
  piloting (primary vehicle control), mission (experiment or payload
  operations), payload (dedicated payload handling), and maintenance
  (system servicing). Each type carries the same geometric and structural
  requirements; the categorization is used to trace requirements to the
  correct system interface.
- Seat geometry is governed by the combined crew anthropometric envelope
  spanning the 5th-to-95th percentile range for the crew population. The
  seat pan must be wide enough and deep enough to accommodate the full
  range. A seat that meets the numeric thresholds is in conformance;
  a seat that falls below either threshold on either axis is a finding
  regardless of margin on the other axis.
- Restraint systems must demonstrate adequate load capacity for the
  three structural attachment points: shoulder harness, lap belt, and
  footrest. Each attachment is assessed independently; a failure on
  one does not relax the requirement on the others.
- Console layout is bounded by a combined reach-and-height envelope
  derived from seated crew reach studies. The lower and upper control
  surface heights are bounded relative to the deck reference plane;
  the maximum reach distance is measured from the torso reference
  point in the nominal seated posture. Controls outside the envelope
  are unreachable under loading conditions.
- Egress clearance is the minimum unobstructed width of the path
  through which crew must pass to exit the station. The requirement
  applies at all points along the egress path; a single narrow point
  governs.

## Workflow

1. Receive the station manifest listing every crew station with its
   assigned station type. Reject any station whose type is not one of
   the four recognized types before proceeding; an unrecognized type
   means a requirements gap that must be resolved upstream.
2. For each station, check seat geometry: confirm the seat pan width
   meets the minimum width threshold and the seat pan depth meets the
   minimum depth threshold. Record a finding for any dimension below
   threshold; a finding on one dimension does not exempt the other
   from being checked.
3. For each station, check restraint load capacity: confirm the
   shoulder harness, lap belt, and footrest each meet their
   respective minimum load ratings. Record a separate finding for
   each attachment point that falls below its minimum.
4. For each station, check console geometry: confirm the lower control
   surface height is at or above the minimum height above deck, the
   upper surface is at or below the maximum height above deck, and
   the maximum control reach distance is within the crew reach
   envelope. Record a finding for each parameter that is out of range.
5. For each station, check egress clearance: confirm the minimum
   unobstructed egress path width meets the required threshold.
   Record a finding if the clearance is below threshold.
6. Aggregate all findings per station. A station is conformant only
   when it has zero findings across all five checks. Present a
   per-station compliance summary and a fleet-level count of
   conformant and non-conformant stations.

## Pitfalls

- Categorizing a station by its primary function and then omitting
  dimensional checks on secondary controls in the same volume — all
  controls that crew must reach from a station are subject to the
  reach and height envelope, not only the primary interface.
- Treating the anthropometric envelope as a single average-user value
  and checking only the 50th-percentile seat — the requirement spans
  the full 5th-to-95th range; a seat sized for the average user fails
  the tails.
- Accepting a restraint system that passes shoulder-harness and
  lap-belt checks but has an undersized footrest — each attachment
  point is independently required; a partial pass is a fail.
- Reading an unconstrained egress path (no furniture in the nominal
  CAD model) as meeting the clearance requirement — the check must
  reflect the as-stowed configuration including crew equipment,
  portable items, and EVA suit stowage when applicable.
- Skipping the station-type validation step and applying a generic
  dimensional matrix — an unrecognized type may map to a different
  human factors standard or a more stringent requirement, and the
  mismatch will not surface until design review.

## Behavior contract (gate 3)

The station-type validation, seat geometry, restraint load, console
envelope, egress clearance, and aggregate assessment logic is exercised
by the gate 3 contract test:
scripts/test_e1011_crew_provisions.py against
scripts/e1011_crew_provisions_logic.py (stdlib unittest, offline). Run:
python3 scripts/test_e1011_crew_provisions.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 →