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

E2007 Emc Test Safety Provisions

ASecurity

Use when assess the radiation-hazard provisions required by ECSS-E-ST-20-07C clause 5.2.5.1 for an electromagnetic run that energizes high-drive radiating or high-voltage equipment: categorize each energized asset by its radiated-field and stored-energy hazard, compute the far-field-power-density reaching the operator position from the drive level and the antenna-gain, weigh it against the permissible-exposure-limit of the emitting band, derive the minimum standoff when that limit is exceeded...

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 e2007-emc-test-safety-provisions --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of E2007 Emc Test Safety Provisions?

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

Security grade badge for E2007 Emc Test Safety Provisions
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ashfordeou-e2007-emc-test-safety-provisions/badge)](https://www.skillsdirectory.com/skills/ashfordeou-e2007-emc-test-safety-provisions)

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

Download with Pro
Files
SKILL.md
---
name: e2007-emc-test-safety-provisions
description: "Use when assess the radiation-hazard provisions required by ECSS-E-ST-20-07C clause 5.2.5.1 for an electromagnetic run that energizes high-drive radiating or high-voltage equipment: categorize each energized asset by its radiated-field and stored-energy hazard, compute the far-field-power-density reaching the operator position from the drive level and the antenna-gain, weigh it against the permissible-exposure-limit of the emitting band, derive the minimum standoff when that limit is exceeded, check the position sits beyond the far-field boundary, and confirm every safeguard the hazard category demands is declared present before the run starts. Trigger: ecss, e-st-20-electrical-scope, e-st-20-07c-clause-5-2-5-1, radiation-hazard-provisions, radhaz-standoff-distance, permissible-exposure-limit, far-field-power-density, high-voltage-safety-provisions, hazard-zone-demarcation, access-interlock-verification."
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, e2007-emc-test-safety-provisions, radiation-hazard-provisions, radhaz-standoff-distance, permissible-exposure-limit, far-field-power-density, high-voltage-safety-provisions, hazard-zone-demarcation]
  version: 0.1.0
  author: Aero Agent Skills
---

# ECSS Electromagnetic Compatibility — Radiation-Hazard Provisions (space-systems/ecss/e2007-emc-test-safety-provisions)

Use when the task is the personnel-safety obligation of ECSS-E-ST-20-07C
clause 5.2.5.1 -- deciding which safeguards a run has to have in place
because it energizes high-drive radiating equipment or high-voltage
equipment, and proving the operator position is far enough back from the
radiating asset to stay inside the permitted exposure.

## Domain quick reference

- Clause 5.2.5.1 is an entry condition, not a blanket rule. The
  radiation-hazard provisions attach to an asset once it crosses a hazard
  threshold: a radiating chain driven at or above the high-drive level, or
  a source whose open-circuit voltage or stored energy reaches the
  electrical-hazard level. An asset below every threshold is uncategorized
  for this clause and carries no safeguard obligation, which is a finding
  about scope rather than a pass.
- The two hazard families demand different safeguards and an asset can
  carry both. A radiated-field hazard needs hazard-zone-demarcation, an
  access-interlock, a warning-indicator and a reachable emission-cutoff
  control. An electrical hazard needs discharge-and-ground tooling, an
  access-interlock, a warning-indicator and an insulated barrier. Where
  both apply the safeguard set is the union, never the larger of the two.
- Exposure at the operator position is an inverse-square estimate:
  the drive level multiplied by the antenna-gain, spread over the sphere
  of the standoff radius. The permissible-exposure-limit it is weighed
  against is frequency-dependent -- flat in the low bands, at its most
  restrictive across the very-high-frequency band where whole-body
  absorption peaks, rising again with frequency through the microwave
  band, then flat once more.
- When the position exceeds the limit, the actionable output is the
  minimum standoff -- the radius at which the same drive and antenna-gain
  land exactly on the limit -- not a bare fail. It is what the hazard-zone
  demarcation is drawn from.
- The inverse-square estimate is only valid beyond the far-field boundary
  of the radiating aperture, roughly twice the squared aperture over the
  wavelength. A position inside that boundary needs a measured survey, so
  it is reported as its own finding rather than quietly computed.
- A power-density assembled from a product and a square can land a few
  units in the last place above a limit it is physically equal to. The
  comparison absorbs that representation error; the exposure limit itself
  is never relaxed.

## Workflow

1. Inventory every asset that will be energized during the run with its
   kind, its drive level, its open-circuit voltage and its stored energy.
   Reject an unrecognized asset kind or a negative level before anything
   else runs.
2. Categorize each asset: radiated-field hazard, electrical hazard, both,
   or uncategorized. A receiver or a support instrument is never a
   radiated-field hazard however large the level recorded against it.
3. Take the union of the safeguards its categories demand, compare that
   against the safeguards declared present, and raise one finding per
   absent safeguard so the reviewer sees which one is missing.
4. For each radiated-field hazard, compute the power-density at the
   operator standoff, look up the permissible-exposure-limit for the
   emitting frequency, and raise a finding with the minimum standoff
   attached whenever the position is inside the hazard zone.
5. Where the radiating aperture is declared, compute the far-field
   boundary and raise a separate finding when the operator position sits
   inside it, because there the computed estimate does not apply.
6. Permit the run only when every asset comes back with an empty finding
   list; report the hazardous assets separately so the safety brief can
   name them.

## Pitfalls

- Treating the clause as covering only radiated hazards and letting a
  high-voltage supply through with warning signage alone -- the discharge
  and grounding tooling is what makes the rack safe to approach after the
  run, and no amount of demarcation substitutes for it.
- Applying one exposure limit across the whole sweep. The limit moves by
  more than a factor of five between the low bands and the most
  restrictive band, so a standoff that is generous at one frequency can be
  well inside the hazard zone at another.
- Computing a standoff inside the far-field boundary of a large aperture
  and acting on the number; the field there is still forming and the
  inverse-square estimate can understate the exposure badly.
- Reporting a bare fail without the minimum standoff, which leaves the
  facility with nothing to draw the hazard zone from and invites an
  arbitrary guess.
- Relaxing the exposure limit to clear a position that fails by a few
  units in the last place. The representation error belongs in the
  comparison, not in the safety limit.

## Behavior contract (gate 3)

The hazard-categorization, safeguard-set, power-density, exposure-limit,
minimum-standoff and far-field-boundary logic is exercised by the gate 3
contract test: scripts/test_e2007_emc_test_safety_provisions.py against
scripts/e2007_emc_test_safety_provisions_logic.py (stdlib unittest,
offline). Run:
python3 scripts/test_e2007_emc_test_safety_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 →