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 Standard Test Environment Conditions

ASecurity

Use when handling, test or storage conditions for an array must be shown to have stayed in band. Audit the ambient pressure, temperature and relative humidity a room held while solar-array hardware was inspected, tested or stored briefly under ECSS-E-ST-20-08C clause 4.3.1: take the band the declared activity owes, size every reading that leaves it per parameter and per bound, weight the out-of-band dwell by logged time instead of reading count, compute the room dew point and the margin the c...

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

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 e2008-standard-test-environment-conditions --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of E2008 Standard Test Environment Conditions?

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

Security grade badge for E2008 Standard Test Environment Conditions
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ashfordeou-e2008-standard-test-environment-conditions/badge)](https://www.skillsdirectory.com/skills/ashfordeou-e2008-standard-test-environment-conditions)

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

Download with Pro
Files
SKILL.md
---
name: e2008-standard-test-environment-conditions
description: "Use when handling, test or storage conditions for an array must be shown to have stayed in band. Audit the ambient pressure, temperature and relative humidity a room held while solar-array hardware was inspected, tested or stored briefly under ECSS-E-ST-20-08C clause 4.3.1: take the band the declared activity owes, size every reading that leaves it per parameter and per bound, weight the out-of-band dwell by logged time instead of reading count, compute the room dew point and the margin the coldest hardware surface keeps above it, and settle on one of four verdicts - inside the band, accepted against a recorded excursion, rejected, or rejected for condensation risk, which outranks every excursion because a record does not dry a bond line. Trigger: ecss, e-st-20-electrical-scope, e-st-20-08c, solar-array-ambient-test-environment, solar-array-cleanroom-humidity-band, solar-array-handling-dew-point-margin, solar-array-short-term-storage-conditions, solar-array-environment-excursion-record."
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-standard-test-environment-conditions, solar-array-ambient-test-environment, solar-array-cleanroom-humidity-band, solar-array-handling-dew-point-margin, solar-array-short-term-storage-conditions, solar-array-environment-excursion-record]
  version: 0.1.0
  author: Aero Agent Skills
---

# ECSS Solar Array — Standard Test Environment Conditions (space-systems/ecss/e2008-standard-test-environment-conditions)

Use when the task is clause 4.3.1 of ECSS-E-ST-20-08C -- the ambient
pressure, temperature and relative-humidity band a room holds while
solar-array hardware is inspected, tested or kept for a short period,
in every case where the test itself does not call for its own
environment. The hardware that this band protects is the part of an
array that shows no mark when it is damaged: bare cell edges,
interconnect welds and adhesive bond lines.

## Domain quick reference

- Three parameters define the band: ambient pressure, room temperature
  and relative humidity. Inspection and testing hold the same band;
  short-term storage is allowed a cooler and drier room, because
  nobody is working in it and dryness is the cheaper risk.
- A reading sitting exactly on a bound is inside the band. Bounds are
  written as decimal literals and readings arrive from instruments
  that may have been converted between units, so the comparison
  absorbs the last-place difference rather than failing a compliant
  room on representation error.
- An excursion is sized per parameter and per bound, not counted. A
  room three points over the humidity ceiling and a room twenty points
  over are the same count and entirely different findings, and the
  bound that was crossed says which direction the facility has to
  move.
- Time matters as much as magnitude. Two readings out of four is not
  half the run if one lasted ten minutes and the other ninety, so the
  dwell outside the band is weighted by logged duration.
- Relative humidity alone does not decide condensation. What decides
  it is the dew point of the room against the coldest hardware
  surface, so a cold panel carried in from a thermal chamber can wet
  in a room whose humidity never left the band.
- A condensation risk is not an excursion to record. An excursion
  record closes a departure that did no harm; moisture that has
  already reached a bond line is not undone by documenting it, so that
  verdict outranks every other outcome.
- The recordable exceedance sizes and the allowed dwell are declared
  project policy rather than physical constants, so they are stated
  with the verdict and a project may substitute its own.

## Workflow

1. Name the activity -- inspection, testing or short-term storage --
   and take the band from it, or declare an explicit envelope where a
   test calls for its own. Reject an uncategorized activity instead of
   defaulting it to the strictest band.
2. Normalise the log. Each reading carries pressure, temperature,
   humidity and the duration it stood for; refuse a humidity above
   saturation or at zero, a temperature at absolute zero and a
   non-positive duration, since each of these silently distorts the
   dwell or the dew point.
3. Size every excursion by parameter and bound, and keep the largest
   seen on each parameter across the log rather than the last one.
4. Weight the time spent outside the band against the total logged
   time to get the dwell fraction.
5. Where a coldest hardware surface is known, compute the dew point at
   every reading and take the smallest margin the surface kept above
   it. Compare that against the declared condensation margin.
6. Settle the verdict in priority order: condensation risk first, then
   a clean run, then an excursion small enough and short enough to be
   closed by a record, then rejection -- and say which of the two
   limits, size or dwell, the rejection turned on.

## Pitfalls

- Judging condensation from relative humidity alone. The band can be
  held all day and a panel at fourteen degrees will still wet in a
  room at twenty-two and sixty percent; the comparison that matters is
  surface temperature against dew point.
- Averaging the log before testing it against the band. A mean
  humidity inside the band hides the hour that was not, and the mean
  of a compliant and a non-compliant hour is always compliant.
- Counting out-of-band readings instead of weighting their duration.
  An instrument that logs every minute during an excursion and every
  hour otherwise reports a dwell that is an artefact of the sampling
  rate.
- Recording an excursion that should have been a rejection. The record
  is only admissible while both limits hold -- the exceedance small
  enough and the dwell short enough -- and a record written over a
  large exceedance transfers the risk to the flight hardware without
  telling anyone.
- Failing a reading that sits exactly on a bound. The band is
  inclusive and a bound compared by bare arithmetic against a
  converted reading rejects a compliant room, which trains the
  facility to stop logging the marginal hours.
- Treating short-term storage as the handling band. The storage band
  is drier and cooler on purpose, and applying it to an inspection
  bench passes rooms that were never fit to work in.

## Behavior contract (gate 3)

The activity band selection, envelope and policy validation, reading
normalisation, per-parameter excursion sizing, time-weighted dwell,
Magnus dew point, condensation margin and the four-way verdict are
exercised by the gate 3 contract test:
scripts/test_e2008_standard_test_environment_conditions.py against
scripts/e2008_standard_test_environment_conditions_logic.py (stdlib
unittest, offline). Run:
python3 scripts/test_e2008_standard_test_environment_conditions.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 →