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 Workstations

ASecurity

Use when assess workstation layout and human-factors design for a crewed spacecraft under ECSS-E-ST-10-11C §4.7.6: verify display placement within acceptable viewing angles from the crew Eye Reference Point, verify controls fall within the reach envelope for their access-frequency zone (primary, secondary, or tertiary), and verify ingress/egress clearance dimensions meet minimum crew-access requirements. Categorize each workstation element by access-frequency zone, flag any element outside it...

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-workstations --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of E1011 Workstations?

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

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

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

Download with Pro
Files
SKILL.md
---
name: e1011-workstations
description: "Use when assess workstation layout and human-factors design for a crewed spacecraft under ECSS-E-ST-10-11C §4.7.6: verify display placement within acceptable viewing angles from the crew Eye Reference Point, verify controls fall within the reach envelope for their access-frequency zone (primary, secondary, or tertiary), and verify ingress/egress clearance dimensions meet minimum crew-access requirements. Categorize each workstation element by access-frequency zone, flag any element outside its zone's viewing or reach limits, and confirm every access path meets clearance minimums. Trigger: ecss, e-st-10-system-scope, e-st-10-11c, workstation, human-factors, viewing-angle, reach-envelope, ingress-egress, layout."
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, e-st-10-11c, workstation, human-factors, viewing-angle, reach-envelope, ingress-egress, layout]
  version: 0.1.0
  author: Aero Agent Skills
---

# ECSS Human Factors — Workstation Design (space-systems/ecss/e1011-workstations)

Use when the task is verifying that a crewed spacecraft workstation meets
the layout, viewing, reach, and ingress/egress requirements of
ECSS-E-ST-10-11C §4.7.6. Each workstation element (display, control, access
path) is categorized by its access-frequency zone and checked against the
dimensional limits for that zone.

## Domain quick reference

- §4.7.6 requires that every display and control be categorized into an
  access-frequency zone before its placement is assessed. A **primary zone**
  element is accessed frequently during normal operations and must lie within
  the preferred field of view and functional reach. A **secondary zone**
  element is accessed occasionally and may extend to the acceptable field of
  view and maximum reach. A **tertiary zone** element is for reference or
  emergency use only and is expected to require crew repositioning to access.
- **Viewing** is assessed from the crew Eye Reference Point (ERP) — the
  design eye position at the 95th-percentile seated or restraint eye height.
  Both horizontal and vertical angles from the ERP to each display centre are
  checked independently against the zone limits. Viewing distance is also
  bounded: too short causes eye strain, too long degrades readability. Primary
  zone limits are tighter than secondary zone limits to ensure critical
  displays are readable without head rotation.
- **Reach** is assessed from the Shoulder Reference Point (SRP). Each zone
  has a maximum reach radius: primary zone controls must lie within functional
  reach (achievable without body lean), secondary zone controls within maximum
  reach (allowing a lean but not repositioning). Tertiary zone elements carry
  no fixed radius because repositioning is already expected and accepted for
  that zone.
- **Ingress/egress** clearances (clear width and clear height of the access
  path to the workstation) are checked against three access modes: normal
  operational, maintenance, and emergency egress. Emergency egress has the
  smallest minimum width to accommodate suited crew in a time-critical
  scenario; normal operational has the tallest minimum height for unrestricted
  upright passage.

## Workflow

1. Record the workstation identifier and the design-anthropometry Eye
   Reference Point (ERP) and Shoulder Reference Point (SRP) positions.
2. Categorize each display and control by access-frequency zone: primary,
   secondary, or tertiary. Reject any element with an unrecognized zone label
   before proceeding to placement assessment.
3. For each display, compute the horizontal angle (deviation from the
   straight-ahead sightline) and the vertical angle (deviation from
   horizontal, negative = below) from the ERP to the display centre, and
   measure the viewing distance from ERP to display surface. Compare each
   value against the zone's viewing limits; record a finding for every
   exceedance.
4. For each control, compute the reach distance from the SRP to the control
   actuation point. Compare it against the zone's maximum reach radius; record
   a finding if the control exceeds its zone's limit. Tertiary zone controls
   require no reach check — they are already accepted as needing repositioning.
5. For each ingress/egress access path to the workstation, record the clear
   width, clear height, and access mode (normal operational, maintenance, or
   emergency egress). Compare width and height against the minimums for that
   mode; record a finding for each shortfall.
6. Aggregate display, reach, and access-path findings for the workstation; the
   workstation design satisfies §4.7.6 only when all three finding lists are
   empty.

## Pitfalls

- Skipping the zone categorization step and applying primary zone limits
  uniformly overstates non-compliance for secondary elements placed at the
  wider secondary limits and may miss primary elements placed too far away.
- Using the 50th-percentile body dimensions instead of the anthropometric
  design drivers: 5th-percentile female drives reach limits (smallest reach
  must still reach the control), 95th-percentile male drives clearance limits
  (largest body must still clear the passage).
- Checking only horizontal viewing angle and ignoring vertical angle — a
  display located far below the ERP sightline can pass the horizontal check
  but require excessive neck flexion, which §4.7.6 prevents via the vertical
  limit.
- Applying the emergency-egress minimum width to all access-path checks — the
  normal-operational minimum is wider and applies to all non-emergency checks.
  Using the smaller emergency figure as a universal baseline allows
  non-compliant designs to pass.

## Behavior contract (gate 3)

The zone-categorization, viewing-angle, reach-envelope, and access-path logic
is exercised by the gate 3 contract test:
scripts/test_e1011_workstations.py against scripts/e1011_workstations_logic.py
(stdlib unittest, offline). Run:
python3 scripts/test_e1011_workstations.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 →