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

E2006 Self Sustained Discharge Prevention

ASecurity

Use when verify that on-board equipment cannot feed a self-sustained-discharge after an electrostatic-discharge is triggered, under ECSS-E-ST-20-06C clause 8.2: categorize each adjacent-conductor pair by gap, barrier material, steady potential-difference and the fault-current its source can deliver; derive the secondary-arc sustaining-voltage and sustaining-current thresholds for that gap; decide whether the pair quenches, flickers as a temporary-sustained-arc, or latches as a permanent-susta...

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 e2006-self-sustained-discharge-prevention --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of E2006 Self Sustained Discharge Prevention?

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

Security grade badge for E2006 Self Sustained Discharge Prevention
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ashfordeou-e2006-self-sustained-discharge-prevention/badge)](https://www.skillsdirectory.com/skills/ashfordeou-e2006-self-sustained-discharge-prevention)

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

Download with Pro
Files
SKILL.md
---
name: e2006-self-sustained-discharge-prevention
description: "Use when verify that on-board equipment cannot feed a self-sustained-discharge after an electrostatic-discharge is triggered, under ECSS-E-ST-20-06C clause 8.2: categorize each adjacent-conductor pair by gap, barrier material, steady potential-difference and the fault-current its source can deliver; derive the secondary-arc sustaining-voltage and sustaining-current thresholds for that gap; decide whether the pair quenches, flickers as a temporary-sustained-arc, or latches as a permanent-sustained-arc; credit only mitigations physically present such as current-limiting, string-segmentation or a series-blocking-diode; and confirm the closure evidence matches the regime. Trigger: ecss, e-st-20-electrical-scope, e-st-20-06c-clause-8-2, self-sustained-discharge, secondary-arc-sustaining-threshold, permanent-sustained-arc, temporary-sustained-arc, adjacent-conductor-gap, arc-current-limiting, sustained-discharge-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, e2006-self-sustained-discharge-prevention, self-sustained-discharge, secondary-arc-sustaining-threshold, permanent-sustained-arc, temporary-sustained-arc, arc-current-limiting]
  version: 0.1.0
  author: Aero Agent Skills
---

# ECSS Spacecraft Charging — Self-Sustained-Discharge Prevention (space-systems/ecss/e2006-self-sustained-discharge-prevention)

Use when the task is the ECSS-E-ST-20-06C clause 8.2 demonstration that no
on-board equipment can keep a discharge alive out of its own generated or
stored energy once a primary electrostatic-discharge has fired somewhere on
the vehicle.

## Domain quick reference

- Clause 8.2 is about what happens *after* the trigger, not about the
  trigger itself. A primary electrostatic-discharge lasts microseconds and
  is a survivable transient; the hazard the clause closes is the secondary
  arc that the equipment's own source then feeds across the same ionized
  gap, indefinitely, until the string or the harness is destroyed.
- The unit of assessment is the adjacent-conductor pair: two conductors
  facing each other across a gap, holding a steady potential-difference,
  backed by a source able to deliver some fault-current into a short. A
  pair is categorized by its barrier — a bare gap, a conformal coat, a
  polyimide tape, a silicone encapsulant, a ceramic standoff — because the
  barrier sets how hard the gap is to keep ionized.
- Two independent sustaining thresholds govern the outcome and both scale
  with the gap. The sustaining-voltage threshold is the potential-difference
  below which the column cannot re-ionize; the sustaining-current threshold
  is the current below which the electrode spots cool and the column
  collapses. The voltage condition is necessary: a pair below the
  sustaining-voltage threshold quenches no matter how much fault-current
  stands behind it.
- Three regimes follow. Below the sustaining-voltage threshold the pair is
  quenched. Above it but below the sustaining-current threshold the pair
  shows a temporary-sustained-arc, which self-extinguishes but still
  deposits energy in the gap. Above both, the pair latches a
  permanent-sustained-arc and clause 8.2 is not met by any amount of
  paperwork — the design has to change.
- Mitigations act on one variable each: current-limiting caps the deliverable
  fault-current, string-segmentation divides the potential-difference across
  the gap, a series-blocking-diode removes a share of the bypass path. Only
  a mitigation physically present in the flight build may be credited.

## Workflow

1. Inventory every adjacent-conductor pair on the equipment — interconnect
   to interconnect, harness to harness, connector pin to pin — with its
   gap, barrier, steady potential-difference and the fault-current its
   source can deliver. Reject an uncategorized barrier before it enters
   the assessment.
2. Apply the mitigations that exist in the flight build, in the order they
   act, to obtain the effective potential-difference and effective
   fault-current at the gap. Reject a mitigation whose parameter is absent
   or non-physical (a single-segment segmentation, a zero limiter rating,
   a full bypass fraction).
3. Derive both sustaining thresholds from the gap and barrier, then
   determine the regime: quenched, temporary-sustained-arc, or
   permanent-sustained-arc. Record both margins, not just the verdict.
4. For a temporary-sustained-arc, compute the energy deposited per event
   from the effective drive and the transient duration, and compare it
   against the benign-transient energy limit. A self-extinguishing arc that
   dumps enough energy to erode an interconnect is still a finding.
5. Check the closure evidence against the regime. A quenched pair may be
   closed by analysis; a temporary-sustained-arc pair needs empirical
   evidence — an arc test or similarity to an already-qualified design.
   Evidence with no report reference is a finding.
6. Roll the per-pair outcomes up per equipment and then per vehicle. The
   clause is met only when no equipment latches and no finding is open.

## Pitfalls

- Reading a large fault-current as sufficient on its own. Without the
  sustaining-voltage threshold being exceeded, the column cannot re-ionize
  and the pair quenches; sizing the whole demonstration around current
  alone flags safe pairs and misses the real ones.
- Crediting a mitigation that lives only in the design note. Current-limiting
  that is not in the flight build, or segmentation that was deleted during
  the harness re-route, turns a compliant record into an unprotected pair
  on orbit.
- Treating a temporary-sustained-arc as a pass because it self-extinguishes.
  It self-extinguishes *each time*, and each time it deposits energy into
  the same gap; the energy per event has to be checked against a limit.
- Letting a floating-point boundary decide a physically compliant pair.
  A potential-difference divided by a segment count can land a few units in
  the last place above a threshold it mathematically equals; the comparison
  absorbs that representation error rather than the engineering limit being
  widened.
- Closing an escalating pair with analysis alone. Secondary-arc onset is
  strongly geometry- and contamination-dependent, which is exactly what a
  model smooths away.

## Behavior contract (gate 3)

The pair categorization, mitigation crediting, sustaining-threshold,
regime-decision, transient-energy and evidence logic is exercised by the
gate 3 contract test:
scripts/test_e2006_self_sustained_discharge_prevention.py against
scripts/e2006_self_sustained_discharge_prevention_logic.py
(stdlib unittest, offline). Run:
python3 scripts/test_e2006_self_sustained_discharge_prevention.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 →