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 Esd Related Emi Control

ASecurity

Use when verify the interference-control provisions required for a space system or equipment exposed to electrostatic-discharge events under ECSS-E-ST-20-07C clause 4.2.4.2: categorize each event as a surface-charging-arc, an internal-charging-arc, a triboelectric-separation event or a ground-handling-event, size the arc-discharge pulse from the stored capacitance, the breakdown-voltage and the arc resistance, couple that pulse onto a victim-harness through its transfer-impedance and shield-e...

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

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-esd-related-emi-control --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of E2007 Esd Related Emi Control?

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

Security grade badge for E2007 Esd Related Emi Control
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ashfordeou-e2007-esd-related-emi-control/badge)](https://www.skillsdirectory.com/skills/ashfordeou-e2007-esd-related-emi-control)

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

Download with Pro
Files
SKILL.md
---
name: e2007-esd-related-emi-control
description: "Use when verify the interference-control provisions required for a space system or equipment exposed to electrostatic-discharge events under ECSS-E-ST-20-07C clause 4.2.4.2: categorize each event as a surface-charging-arc, an internal-charging-arc, a triboelectric-separation event or a ground-handling-event, size the arc-discharge pulse from the stored capacitance, the breakdown-voltage and the arc resistance, couple that pulse onto a victim-harness through its transfer-impedance and shield-effectiveness, compare the coupled transient against the victim transient-susceptibility threshold with the declared emi-margin, and confirm the chassis-bonding, surface-conductivity, shield-termination and transient-filtering provisions for that event family are on record. Trigger: ecss, e-st-20-electrical-scope, esd-related-emi-control, electrostatic-discharge, arc-transient-coupling, transfer-impedance, surface-charging-arc, internal-charging-arc, shield-termination, transient-susceptibility."
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-esd-related-emi-control, electrostatic-discharge, arc-transient-coupling, transfer-impedance, surface-charging-arc, internal-charging-arc, transient-susceptibility]
  version: 0.1.0
  author: Aero Agent Skills
---

# ECSS Electromagnetic Compatibility — ESD-Related EMI Control (space-systems/ecss/e2007-esd-related-emi-control)

Use when the task is the electrostatic-discharge interference-control
assessment of ECSS-E-ST-20-07C clause 4.2.4.2 — categorizing each
discharge event a system or equipment is exposed to, sizing the
arc-discharge pulse it delivers, coupling that pulse onto the victim
harness, and checking the coupled transient against the victim
transient-susceptibility threshold with a declared emi-margin.

## Domain quick reference

- Clause 4.2.4.2 treats an electrostatic-discharge event as an
  interference source, not only as a damage mechanism: the arc is a
  fast, broadband current pulse that couples into harnesses and
  equipment ports, so the provision set is an interference-control
  set (bonding, surface conductivity, shield termination, transient
  filtering) rather than a single component-level protection device.
- Four event families cover the in-scope exposures. A
  surface-charging-arc comes from differential charging of an external
  dielectric relative to the conductive structure. An
  internal-charging-arc comes from energetic electrons buried inside a
  dielectric until the internal field exceeds breakdown. A
  triboelectric-separation event comes from contact and separation of
  dissimilar materials during deployment or release. A
  ground-handling-event is the pre-launch human-body or charged-device
  exposure. Each event is categorized into exactly one family before
  its provisions are checked, and an unrecognized event kind is
  rejected rather than assumed benign.
- The arc is modelled as a capacitive discharge through the arc
  resistance: peak current is the breakdown-voltage divided by the arc
  resistance, transferred charge is capacitance times breakdown-voltage,
  stored energy is half the capacitance times the breakdown-voltage
  squared, and the decay time constant is the product of arc resistance
  and capacitance. The spectral corner frequency derived from that time
  constant is what makes a small-energy arc an EMI source: a short
  time constant pushes significant content into the band where harness
  coupling is efficient.
- Coupling onto a victim-harness uses the surface transfer-impedance of
  its shield: the open-circuit transient is peak current times the
  transfer-impedance per metre times the exposed run length, reduced by
  the shield-effectiveness expressed in decibels. The result is
  compared with the victim transient-susceptibility threshold, and the
  ratio in decibels is the emi-margin. A design is acceptable only when
  that emi-margin meets or exceeds the declared requirement.
- The provision set is family-specific. A surface-charging-arc needs
  surface-conductivity control and a bonded conductive path plus
  terminated shields; an internal-charging-arc needs dielectric
  thickness or shielding control plus bonding and transient filtering;
  a triboelectric-separation event needs static-dissipative materials
  and bonding; a ground-handling-event needs a controlled handling area,
  operator bonding and transient filtering. A missing provision is a
  finding even when the computed emi-margin passes.

## Workflow

1. Inventory every electrostatic-discharge exposure of the system and
   its equipment, and categorize each one into its event family.
   Reject an unrecognized event kind before it enters the assessment.
2. Size the arc-discharge pulse for each event from the stored
   capacitance, the breakdown-voltage and the arc resistance; record
   peak current, transferred charge, stored energy, decay time constant,
   pulse duration and spectral corner frequency.
3. For each event and the victim it can reach, compute the coupled
   transient from the harness transfer-impedance, the exposed run
   length and the shield-effectiveness.
4. Compute the emi-margin as the decibel ratio of the victim
   transient-susceptibility threshold to the coupled transient, and
   compare it against the declared requirement. Treat an exactly
   on-limit result as compliant by absorbing the floating-point
   representation error, never by widening the requirement.
5. Check the family-specific provision set for each event and list the
   provisions that are not on record.
6. Aggregate the coupling findings and the provision findings; the
   system is not interference-controlled for electrostatic discharge
   until both lists are empty. Report the worst emi-margin as the
   driving case.

## Pitfalls

- Treating an arc as an energy problem only: a milli-joule arc that is
  harmless thermally still radiates a broadband pulse, and clause
  4.2.4.2 is about that interference path, not about the energy.
- Collapsing the four event families into one generic exposure — the
  provision sets differ, and a surface-conductivity coating does
  nothing for an internal-charging-arc driven by buried charge.
- Applying the open-circuit transient without the shield-effectiveness
  term, or applying the shield-effectiveness twice by also reducing the
  transfer-impedance; each is a large error in opposite directions.
- Reading a passing emi-margin as compliance while a required provision
  is unrecorded — the computed coupling covers one victim and one path,
  while the provision set covers the exposures that were never modelled.
- Widening the declared emi-margin requirement to make an exactly
  on-limit case pass; absorb the representation error in the comparison
  instead and leave the engineering requirement untouched.
- Assuming a ground-handling-event is out of scope because it happens
  before launch; the latent damage and the provisions that prevent it
  are part of the same interference-control set.

## Behavior contract (gate 3)

The event categorization, arc-pulse sizing, transfer-impedance
coupling, emi-margin and provision-set logic is exercised by the gate 3
contract test: scripts/test_e2007_esd_related_emi_control.py against
scripts/e2007_esd_related_emi_control_logic.py (stdlib unittest,
offline). Run: python3 scripts/test_e2007_esd_related_emi_control.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 →