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 Radiated Electric Susceptibility Overview

ASecurity

Verify that a radiated electric field susceptibility run demonstrates the aim ECSS-E-ST-20-07C clause 5.4.11.1 introduces: the unit and its interconnecting cabling both keep working under a strong field across a wide band. Use when the method is introduced, planned or its record reviewed: confirm both exposure objects are swept, check each sweep reaches both edges of the declared band, compute the margin between the field applied and the field required at every frequency, group each point as ...

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

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-radiated-electric-susceptibility-overview --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of E2007 Radiated Electric Susceptibility Overview?

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

Security grade badge for E2007 Radiated Electric Susceptibility Overview
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ashfordeou-e2007-radiated-electric-susceptibility-overview/badge)](https://www.skillsdirectory.com/skills/ashfordeou-e2007-radiated-electric-susceptibility-overview)

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

Download with Pro
Files
SKILL.md
---
name: e2007-radiated-electric-susceptibility-overview
description: "Verify that a radiated electric field susceptibility run demonstrates the aim ECSS-E-ST-20-07C clause 5.4.11.1 introduces: the unit and its interconnecting cabling both keep working under a strong field across a wide band. Use when the method is introduced, planned or its record reviewed: confirm both exposure objects are swept, check each sweep reaches both edges of the declared band, compute the margin between the field applied and the field required at every frequency, group each point as at level, under level or overtested, mark a monitored degradation with the frequency it begins at, and name the governing object. Trigger: ecss, e-st-20-07c, radiated-electric-susceptibility-overview, electric-field-exposure-band-coverage, harness-field-exposure, applied-field-margin, susceptibility-degradation-threshold, radiated-electric-aim-demonstration."
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-radiated-electric-susceptibility-overview, electric-field-exposure-band-coverage, harness-field-exposure, applied-field-margin, susceptibility-degradation-threshold, radiated-electric-aim-demonstration]
  version: 0.1.0
  author: Aero Agent Skills
---

# ECSS EMC — Radiated Electric Susceptibility, Method Overview (space-systems/ecss/e2007-radiated-electric-susceptibility-overview)

Use when the task is the introductory clause of ECSS-E-ST-20-07C
clause 5.4.11.1 -- establishing what the radiated electric
susceptibility method is run to show, namely that the unit and the
cabling running into it both go on performing while an electric field
of the required strength is applied to them over a wide band.

## Domain quick reference

- The aim names two exposure objects, not one. The enclosure of the
  unit and the interconnecting cabling are separate objects with their
  own sweeps, because they couple the field in different ways: the
  enclosure through apertures and seams, the harness as a wire picking
  up a field along its length. A run that exposes only the box has not
  demonstrated the aim, and no amount of level on the box makes up for
  it.
- The graded quantity per frequency is a margin between the field
  applied and the field required, taken in decibels. Applying exactly
  the required strength is compliance. Applying less means that
  frequency was never taken to the requirement, which is a finding
  about the run rather than a result about the unit. Applying more is
  an overtest: compliant, carried as a limitation, and worth naming
  because it can stress hardware past what qualification intended.
- A field margin is a ratio taken to decibels, so an applied field
  sitting exactly on the requirement can land a few units in the last
  place either side of zero. That is absorbed with a named tolerance
  inside the comparison, never by moving the required strength.
- The aim is stated across a wide band, so both edges are checked in
  their own right. A sweep that starts above the lower edge or stops
  below the upper edge has not shown the aim over the band it claims,
  and the gap is a finding rather than a silent pass.
- A degradation seen while the field is applied is the result the
  method exists to find. What matters is not only that it happened but
  the lowest frequency it happened at, because that threshold is what
  a fix or a waiver is written against.
- The introductory clause fixes the objective. The instruments that
  raise the field, the bench layout and the way performance is watched
  belong to the equipment, setup and monitoring clauses of the same
  method and are graded there.

## Workflow

1. Validate the declared method band: a positive lower edge and an
   upper edge strictly above it. An inverted or collapsed band is an
   input error, not a degenerate case to clamp.
2. Normalize the exposure object of each record, reject a duplicate
   declaration, and name any of the two objects that never appears.
3. Validate each sweep: at least one point, strictly increasing
   positive frequencies, a positive applied and required field at
   every point, and a boolean monitored response.
4. Check band coverage per object against both edges, allowing only a
   named relative slack at an edge.
5. Compute the field margin at every frequency and group it as at
   level, under level or above level, absorbing representation error
   at zero with the named decibel tolerance.
6. Reduce each object to its worst point, breaking an exact tie on the
   lower frequency so the selection is reproducible, and take the
   lowest degraded frequency as the susceptibility threshold.
7. Aggregate: an absent object, a band shortfall, an under-level
   frequency or a monitored degradation are findings; an overtested
   frequency is a limitation. The aim is demonstrated only when no
   finding stands.

## Pitfalls

- Exposing the unit and leaving the harness in the shadow of the
  turntable. The cabling is an exposure object in its own right, and a
  field that never reaches it demonstrates nothing about it.
- Reading the forward power and assuming the field. The graded
  quantity is field strength at the unit, and the two part company as
  soon as the amplifier compresses or the antenna is mismatched.
- Averaging the margin over the band. The method exists to find the
  one frequency where the unit stops performing, and an average is the
  most reliable way to hide it.
- Recording that a degradation occurred without the frequency it
  started at. A susceptibility with no threshold cannot be fixed,
  waived or retested against.
- Accepting a sweep that stops short of the upper edge because the
  amplifier ran out there. That is exactly the finding the coverage
  check exists to raise; a formally accepted reduced span belongs on
  the record as a limitation instead.

## Behavior contract (gate 3)

The band validation, exposure-object normalization and completeness
check, sweep validation, per-frequency field margin and grouping, band
coverage, degradation threshold, governing-point selection and the
aggregate verdict are exercised by the gate 3 contract test:
scripts/test_e2007_radiated_electric_susceptibility_overview.py
against
scripts/e2007_radiated_electric_susceptibility_overview_logic.py
(stdlib unittest, offline). Run:
python3 scripts/test_e2007_radiated_electric_susceptibility_overview.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 →