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 Interface Loads And Terminations

ASecurity

Verify that every interface of a tested unit is terminated in real hardware or a representative equivalent load before an ECSS-E-ST-20-07C clause 5.2.6.7 electromagnetic run: categorize each termination, compare equivalent-load impedance magnitude and phase against the hardware it stands in for, check that a simulated power load draws the flight load current and is rated above its dissipation, and hold the run while any interface is open or out of tolerance. Use when a bench substitutes load ...

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

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-interface-loads-and-terminations --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of E2007 Interface Loads And Terminations?

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

Security grade badge for E2007 Interface Loads And Terminations
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ashfordeou-e2007-interface-loads-and-terminations/badge)](https://www.skillsdirectory.com/skills/ashfordeou-e2007-interface-loads-and-terminations)

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

Download with Pro
Files
SKILL.md
---
name: e2007-interface-loads-and-terminations
description: "Verify that every interface of a tested unit is terminated in real hardware or a representative equivalent load before an ECSS-E-ST-20-07C clause 5.2.6.7 electromagnetic run: categorize each termination, compare equivalent-load impedance magnitude and phase against the hardware it stands in for, check that a simulated power load draws the flight load current and is rated above its dissipation, and hold the run while any interface is open or out of tolerance. Use when a bench substitutes load simulators, dummy loads or bus terminators for flight items. Trigger: ecss, e-st-20-electrical-scope, interface-termination-load, equivalent-load-impedance-match, flight-hardware-termination, open-interface-detection, power-interface-load-current, emc-bench-termination-gate."
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-interface-loads-and-terminations, interface-termination-load, equivalent-load-impedance-match, flight-hardware-termination, open-interface-detection, power-interface-load-current]
  version: 0.1.0
  author: Aero Agent Skills
---

# ECSS Electrical Test Setup — Interface Loads and Terminations (space-systems/ecss/e2007-interface-loads-and-terminations)

Use when the task is the ECSS-E-ST-20-07C clause 5.2.6.7 obligation that the
interfaces of a tested unit be terminated during an electromagnetic
measurement -- in the real hardware they drive in flight, or in an equivalent
load that presents the same termination -- and the bench record has to be
reviewed before the first sweep.

## Domain quick reference

- An interface left open is not a simplification of the flight
  configuration, it is a different configuration. The open changes the
  current distribution on the harness, and the harness is the dominant
  radiator, so the measured emission belongs to a unit that will never fly.
- Every termination is categorized before the run: real hardware, equivalent
  load, or unterminated. A termination kind outside that set has no defined
  standing on the bench and is rejected rather than assumed benign.
- An equivalent load is equivalent only inside a declared tolerance, and the
  tolerance has two independent parts. The impedance magnitude is compared
  as a relative deviation from the hardware it replaces; the reactive
  character is compared as a phase deviation. A resistor that matches in
  magnitude but not in phase is a different termination at every frequency
  where the reactance matters.
- A power interface carries one obligation more than a signal interface. The
  simulated load must draw the flight load current within tolerance, because
  the conducted emission spectrum rides on that current, and the load bank
  must be rated above the power it dissipates by a stated margin, or it
  drifts thermally through the sweep and the measurement drifts with it.
- Impedance and phase deviations are unsigned. A load 10 % low is as wrong as
  a load 10 % high, and treating one as conservative hides the case where the
  stand-in loads the interface harder than flight ever will.
- A phase outside a quarter turn is a data error rather than a poor load; a
  passive termination does not present it, and accepting the value would put
  a transcription mistake into the configuration record.

## Workflow

1. Categorize every interface: map each declared termination kind to real
   hardware, equivalent load or unterminated. Reject an unrecognized kind, a
   duplicate interface name, or an empty interface list.
2. Raise a finding for each unterminated interface and stop checking it; an
   open interface has no impedance to compare.
3. For each equivalent load, compute the impedance deviation from the
   hardware it stands in for and compare it with the tolerance, then compare
   the phase deviation with its own tolerance.
4. For each power interface fed by an equivalent load, compare the simulated
   load current with the flight load current, then compute the dissipated
   power and the rating margin of the load bank.
5. Report the share of interfaces terminated in real hardware, and check it
   against any floor the test configuration declares.
6. Aggregate the findings and emit the gate token. Only an empty finding list
   releases the unit for measurement; anything else holds the terminations.

## Pitfalls

- Leaving a spare or unused connector open because nothing is connected to it
  in the test. The flight configuration terminates it, so the bench does too.
- Matching the impedance magnitude and declaring the load equivalent. Phase
  is a separate requirement, and a reactive flight load replaced by a pure
  resistor changes the conducted spectrum.
- Sizing the load bank to the dissipated power. The margin exists so the load
  does not drift as it heats, so the rating is compared against dissipation
  times the required factor, not against dissipation.
- Treating a simulated current below the flight value as conservative. It
  lowers the conducted emission and the unit passes on a current it will
  never draw in orbit.
- Checking the power interface and skipping the data-bus terminator. An
  unterminated bus reflects, and the reflection is a radiator.
- Letting a percentage that lands a few units in the last place outside a
  tolerance read as a non-conformance. The logic absorbs representation error
  with a named tolerance far below any engineering value; the tolerance
  itself is never widened.

## Behavior contract (gate 3)

The termination categorization, impedance and phase comparison, power-load
current and rating checks, real-hardware share and readiness-gate logic is
exercised by the gate 3 contract test:
`scripts/test_e2007_interface_loads_and_terminations.py` against
`scripts/e2007_interface_loads_and_terminations_logic.py` (stdlib unittest,
offline).
Run: python3 scripts/test_e2007_interface_loads_and_terminations.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 →