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

E2008 Dimensions And Stay Out Zones

ASecurity

Use when a coupon layout has to be judged against the drawing rather than against a defect list. Compute the dimensional, keep-out and standoff checks that ECSS-E-ST-20-08C clause 5.5.3.2.4 folds into the visual inspection of a photovoltaic assembly coupon: place every measured dimension inside its plus and minus drawing band and name the one that governs, build the border bands a reserved edge margin creates, test each placed feature against every stay-out zone for shared area, intrusion dep...

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

Works with

claude codecli

Security Analysis

A100/100

Scanned 9/27/2026

Install to Claude Code

$npx -y skills add ashfordeOU/aero-agent-skills --skill e2008-dimensions-and-stay-out-zones --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of E2008 Dimensions And Stay Out Zones?

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

Security grade badge for E2008 Dimensions And Stay Out Zones
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ashfordeou-e2008-dimensions-and-stay-out-zones/badge)](https://www.skillsdirectory.com/skills/ashfordeou-e2008-dimensions-and-stay-out-zones)

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

Download with Pro
Files
SKILL.md
---
name: e2008-dimensions-and-stay-out-zones
description: "Use when a coupon layout has to be judged against the drawing rather than against a defect list. Compute the dimensional, keep-out and standoff checks that ECSS-E-ST-20-08C clause 5.5.3.2.4 folds into the visual inspection of a photovoltaic assembly coupon: place every measured dimension inside its plus and minus drawing band and name the one that governs, build the border bands a reserved edge margin creates, test each placed feature against every stay-out zone for shared area, intrusion depth and shortest clearance, then check each standoff feature reaches its called-out height and keeps its footprint clear of the zones. Trigger: ecss, e-st-20-08c, coupon-dimensional-tolerance-check, solar-array-stay-out-zone, keep-out-area-intrusion, standoff-feature-height-check, coupon-edge-margin-band, feature-zone-clearance."
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-20-electrical-scope, e-st-20-08c, e2008-dimensions-and-stay-out-zones, coupon-dimensional-tolerance-check, solar-array-stay-out-zone, keep-out-area-intrusion, standoff-feature-height-check, coupon-edge-margin-band]
  version: 0.1.0
  author: Aero Agent Skills
---

# ECSS Photovoltaic — Dimensions and Stay-Out Zones (space-systems/ecss/e2008-dimensions-and-stay-out-zones)

Use when the task is the geometric part of ECSS-E-ST-20-08C clause
5.5.3.2.4 -- the coupon dimensions, the keep-out areas and the standoff
features that a visual inspection of a photovoltaic assembly has to
check alongside the defect examination.

## Domain quick reference

- This part of the inspection is not about defects. It asks whether the
  coupon is the size the drawing calls out, whether the reserved areas
  are still empty, and whether the standoff features stand where and how
  high they were meant to.
- A dimension is a band, not a target. Each one carries its own plus and
  minus allowance, and the useful output is not a pass mark but the
  fraction of the allowance each measurement consumed, because the
  dimension that consumed the most is the one that will fail first on
  the next unit.
- Keep-out areas are ordinary rectangles in the coupon frame: harness
  routing corridors, hold-down footprints, connector swing volumes, and
  the border band a reserved edge margin creates on all four sides. An
  edge margin is one number on the drawing and four zones in the check.
- A feature and a zone stand in one of three relations, and they are
  measured differently. They overlap, and the answer is a shared area
  and the shortest distance that would move the feature out. They touch,
  and the shared area is zero while the clearance is also zero. They are
  apart, and the answer is the shortest distance between them, which on
  a diagonal offset is a corner-to-corner distance and not an axis gap.
- Zero clearance is not automatically a failure. It fails when the
  layout declares a minimum clearance above zero, which is the usual
  case once thermal cycling and harness movement are allowed for.
- A standoff carries two independent checks. Its height sits in a
  tolerance band exactly like a coupon dimension, and its footprint is a
  placed feature that the stay-out zones apply to like any other.

## Workflow

1. Validate the drawing spec and the measurement set against each other:
   every called-out dimension measured, no measurement without a drawing
   entry, positive nominals, non-negative allowances with at least one
   side open, and a lower limit that is still a physical dimension.
2. For each dimension compute the deviation, the fraction of the
   allowance on the side the deviation falls on, and the verdict.
   Absorb representation error exactly on a limit with a named tolerance
   rather than by widening the band.
3. Roll the dimensions up: which are out of tolerance, and which
   consumed the most allowance. Break a tie on the dimension name so the
   governing dimension is reproducible.
4. Assemble the stay-out zones: those declared explicitly, plus the four
   border bands from any reserved edge margin. Refuse a margin that
   leaves no usable area, and refuse duplicate zone identifiers.
5. Test every placed feature against every zone for shared area,
   intrusion depth and shortest clearance, and compare the clearance
   with the declared minimum.
6. Check each standoff height against its band, then feed the standoff
   footprints back through the same zone test.
7. Return the coupon verdict with the dimension, zone and standoff
   findings kept separate, so a rejection names what actually failed.

## Pitfalls

- Judging a dimension by its deviation alone. A deviation of a tenth of
  a millimetre is comfortable on one dimension and the whole allowance
  on another; only the consumed fraction compares across a coupon.
- Treating a reserved edge margin as a single zone. It is four bands,
  and a feature that hangs over one corner sits in two of them; building
  only one band leaves three edges unchecked.
- Measuring clearance as an axis gap. Two rectangles offset on both axes
  are separated by the corner-to-corner distance, and quoting the larger
  axis gap overstates the clearance on exactly the diagonal case that
  matters.
- Reading a touching feature as an intrusion. Shared area is zero when
  edges coincide; what makes it a finding is a declared minimum
  clearance above zero, not the contact itself.
- Checking a standoff height and forgetting its footprint. The height is
  a dimension and the footprint is a placed feature, and a standoff at
  exactly the right height planted in a harness corridor is still a
  reject.
- Asserting a strict inequality on a clearance that is meant to sit
  exactly on the declared minimum. Coordinates are built by addition and
  the clearance can land a few units in the last place either side of
  the bound; compare with a tolerance and assert the verdict instead.

## Behavior contract (gate 3)

The tolerance banding, governing-dimension roll-up, rectangle overlap,
intrusion depth, clearance distance, edge-margin band construction,
standoff height check and coupon verdict are exercised by the gate 3
contract test: scripts/test_e2008_dimensions_and_stay_out_zones.py
against scripts/e2008_dimensions_and_stay_out_zones_logic.py (stdlib
unittest, offline). Run:
python3 scripts/test_e2008_dimensions_and_stay_out_zones.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 →