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 Low Frequency Conducted Emission Equipment

ASecurity

Assess the instrument set a low-frequency conducted-emission run is built from under ECSS-E-ST-20-07C clause 5.4.2.2: confirm a measurement receiver, a current probe and a calibration signal source are all present and in date, intersect their frequency coverage with the required measurement band, report every uncovered sub-band, name the instrument that limits the chain, check the probe transfer-impedance and current rating against the harness it must clamp, and derive the source drive level ...

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

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-low-frequency-conducted-emission-equipment --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of E2007 Low Frequency Conducted Emission Equipment?

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

Security grade badge for E2007 Low Frequency Conducted Emission Equipment
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ashfordeou-e2007-low-frequency-conducted-emission-equipment/badge)](https://www.skillsdirectory.com/skills/ashfordeou-e2007-low-frequency-conducted-emission-equipment)

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

Download with Pro
Files
SKILL.md
---
name: e2007-low-frequency-conducted-emission-equipment
description: "Assess the instrument set a low-frequency conducted-emission run is built from under ECSS-E-ST-20-07C clause 5.4.2.2: confirm a measurement receiver, a current probe and a calibration signal source are all present and in date, intersect their frequency coverage with the required measurement band, report every uncovered sub-band, name the instrument that limits the chain, check the probe transfer-impedance and current rating against the harness it must clamp, and derive the source drive level the system check will need. Use when assembling or auditing a low-frequency conducted-emission bench before the setup is built. Trigger: ecss, e-st-20-07c, lf-conducted-emission-equipment, emi-measurement-receiver, current-probe-transfer-impedance, conducted-emission-calibration-source, conducted-emission-band-coverage, instrument-calibration-currency."
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-low-frequency-conducted-emission-equipment, lf-conducted-emission-equipment, emi-measurement-receiver, current-probe-transfer-impedance, conducted-emission-calibration-source, conducted-emission-band-coverage, instrument-calibration-currency]
  version: 0.1.0
  author: Aero Agent Skills
---

# ECSS EMC — Low-Frequency Conducted-Emission Equipment (space-systems/ecss/e2007-low-frequency-conducted-emission-equipment)

Use when the task is the instrumentation list of ECSS-E-ST-20-07C clause
5.4.2.2 -- deciding whether the measurement receiver, the current probe
and the calibration signal source on hand can actually carry a
low-frequency conducted-emission run across the whole required band, and
naming what is missing when they cannot.

## Domain quick reference

- The clause names three roles, not three boxes. One instrument may fill
  only one role in a given run; a set carrying two receivers and no probe
  is not a set, and a set whose source is missing cannot be system
  checked at all. Readiness is decided per role, and an absent role is a
  finding rather than a detail to be worked around on the day.
- Coverage is an intersection, never a union. The measurable band is the
  overlap of the receiver, the probe and the source coverages with the
  required band. A receiver reaching far above the band buys nothing once
  the probe stops early; the chain is exactly as wide as its narrowest
  member.
- Report the gap as a frequency interval, not as a percentage. A set that
  covers ninety-five percent of a decade-wide band can still be blind
  across the sub-band the unit's switching fundamental sits in, and only
  the interval says so.
- The current probe is characterised by its transfer impedance, the ratio
  between the voltage it presents to the receiver and the current flowing
  in the harness. Too low a transfer impedance sinks the wanted signal
  into the receiver noise floor at the low end of the band, where the
  emission limits are tightest.
- The probe also has a current rating. Clamping a probe on a harness
  carrying more current than the core can take saturates the core, and
  the recorded level is then a property of the saturated probe.
- The signal source exists to inject a known current during the system
  check. The level it must reach follows from the wanted check current
  and the probe transfer impedance through the port impedance; a source
  that cannot reach it makes the system check unperformable.
- Calibration currency is part of the equipment list. A lapsed
  calibration is a finding; one about to lapse before the campaign ends
  is a limitation to be carried, not silently ignored.

## Workflow

1. Normalize every instrument record to one of the three recognized
   roles and reject an unrecognized role or a role appearing twice.
2. Validate each record: positive, ordered frequency edges, a calibration
   figure, plus transfer impedance and current rating on the probe and an
   output ceiling on the source.
3. List the absent roles. Without all three, stop at incomplete rather
   than grading a coverage that cannot be measured.
4. Intersect the three coverages with the required measurement band,
   express the result in decades, and reduce the leftovers to explicit
   uncovered sub-bands.
5. Attribute the loss: the instrument removing the most decades from the
   required band is the limiting one, with ties resolved in the clause's
   own role order so the answer is stable.
6. Compare the probe transfer impedance against the sensitivity floor and
   its rating against the harness current, then derive the source drive
   level the system check needs and compare it with the source ceiling.
7. Aggregate the findings and the limitations. The set is ready only when
   no finding stands.

## Pitfalls

- Adding the coverages together instead of intersecting them, so a wide
  receiver hides a probe that stops two decades short.
- Treating a missing role as recoverable and grading the coverage of the
  two instruments that did turn up.
- Quoting coverage as a percentage of the band. The uncovered interval is
  what a reviewer needs; the percentage hides where the blindness sits.
- Picking a probe on its current rating alone and discovering at the low
  end that its transfer impedance leaves no signal above the noise floor.
- Assuming any laboratory source can drive the system check. The level
  needed scales with the wanted check current and the transfer impedance,
  and a low-output generator falls short of it.
- Carrying an instrument whose calibration lapses mid-campaign without
  recording it, then having the whole data set questioned afterwards.

## Behavior contract (gate 3)

The role normalization, instrument validation, band-intersection
coverage, limiting-instrument attribution, drive-level derivation and
readiness aggregation logic is exercised by the gate 3 contract test:
scripts/test_e2007_low_frequency_conducted_emission_equipment.py against
scripts/e2007_low_frequency_conducted_emission_equipment_logic.py
(stdlib unittest, offline). Run:
python3 scripts/test_e2007_low_frequency_conducted_emission_equipment.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 →