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 Tether Insulation Continuity

ASecurity

Use when verify that the insulation jacket of a tether stays unbroken across its service life under ECSS-E-ST-20-06C clause 10.2.4: categorize each observed defect as through-thickness (pinhole, crack, cut-through) or partial-thickness (abrasion-scuff, delamination, thermal-blister), subtract atomic-oxygen erosion and the abrasion allowance from the as-built wall to obtain the end-of-life remaining-thickness, compute the dielectric-withstand of that wall against the applied tether voltage and...

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

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-tether-insulation-continuity --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of E2006 Tether Insulation Continuity?

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

Security grade badge for E2006 Tether Insulation Continuity
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ashfordeou-e2006-tether-insulation-continuity/badge)](https://www.skillsdirectory.com/skills/ashfordeou-e2006-tether-insulation-continuity)

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

Download with Pro
Files
SKILL.md
---
name: e2006-tether-insulation-continuity
description: "Use when verify that the insulation jacket of a tether stays unbroken across its service life under ECSS-E-ST-20-06C clause 10.2.4: categorize each observed defect as through-thickness (pinhole, crack, cut-through) or partial-thickness (abrasion-scuff, delamination, thermal-blister), subtract atomic-oxygen erosion and the abrasion allowance from the as-built wall to obtain the end-of-life remaining-thickness, compute the dielectric-withstand of that wall against the applied tether voltage and its required factor, and check insulation-resistance, defect-density and pinhole leakage-current against their acceptance limits. Trigger: ecss, e-st-20-06c, tether-insulation-continuity, dielectric-withstand, pinhole-defect, atomic-oxygen-erosion, insulation-resistance, remaining-thickness, service-life-degradation."
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-tether-insulation-continuity, tether-insulation-continuity, dielectric-withstand, pinhole-defect, atomic-oxygen-erosion, insulation-resistance, remaining-thickness]
  version: 0.1.0
  author: Aero Agent Skills
---

# ECSS Electrical Tether — Insulation Continuity (space-systems/ecss/e2006-tether-insulation-continuity)

Use when the task is the insulation-continuity verification of
ECSS-E-ST-20-06C clause 10.2.4 -- showing that the dielectric jacket
over a tether conductor has no hole, crack or thinned region that
breaks its continuity, and that it still holds off the applied tether
voltage at the end of the declared service life, not only at delivery.

## Domain quick reference

- A defect is categorized by how far it goes through the wall, because
  the two families are graded by different rules. A through-thickness
  defect (pinhole, crack, cut-through) exposes bare conductor to the
  ambient plasma: it is a continuity break on sight, and no remaining
  wall arithmetic rescues it. A partial-thickness defect
  (abrasion-scuff, delamination, thermal-blister) leaves a reduced but
  intact wall, and is graded on the depth fraction it consumes against
  the allowance for that segment. An unrecognized defect type is
  rejected rather than assumed benign.
- Continuity is a service-life property, not a delivery property. The
  as-built wall loses thickness to atomic-oxygen erosion over the
  mission fluence -- eroded depth is fluence x erosion-yield of the
  jacket material -- and to the abrasion allowance booked for
  deployment, reeling and micrometeoroid scuffing. The wall that must
  hold off voltage is what remains after both are subtracted, and a
  remaining-thickness of zero or less is a breach, reported as such
  rather than as a very small number.
- The dielectric-withstand of the remaining wall is its thickness
  times the material dielectric strength. It is compared against the
  applied tether voltage multiplied by the required factor for the
  design; the ratio of withstand to required voltage is the margin,
  and a margin below one is a finding. An exactly-at-unity margin is
  compliant -- the comparison absorbs the representation error of a
  difference of floats rather than the limit being relaxed.
- Two acceptance measurements close the loop. Insulation-resistance
  measured over the segment must meet the minimum on record; a segment
  with no minimum on record is an open finding, not a pass. The
  leakage-current collected through the exposed area of
  through-thickness defects, taken as the ambient plasma
  current-density over that area, must stay within the leakage budget,
  and the defect-density per metre must stay within its acceptance
  limit.

## Workflow

1. Inventory every defect found on the segment by inspection or
   proof-testing and categorize each as through-thickness or
   partial-thickness. Reject an unrecognized defect type before it
   enters the assessment.
2. Flag every through-thickness defect as a continuity break, and
   accumulate its exposed area for the leakage-current calculation.
   Grade each partial-thickness defect on the fraction of wall it
   consumes against the allowed depth fraction for that segment.
3. Compute the eroded depth over the mission from the atomic-oxygen
   fluence and the jacket material erosion-yield, subtract it and the
   booked abrasion allowance from the as-built thickness, and report
   the end-of-life remaining-thickness; zero or less is a breach.
4. Compute the dielectric-withstand of the remaining wall and divide
   by the applied tether voltage times the required factor. A margin
   below one is a finding; an exactly-at-unity margin passes.
5. Compare the measured insulation-resistance against the minimum on
   record, the defect-density per metre against its limit, and the
   summed pinhole leakage-current against the leakage budget. A
   missing minimum or a missing measurement is itself a finding.
6. Aggregate the defect, wall, withstand and acceptance findings per
   segment; the segment is continuity-compliant only when every list
   is empty.

## Pitfalls

- Grading insulation on the as-built wall and never subtracting
  service-life erosion. The jacket that passes proof-testing at
  delivery can be a third thinner after the mission fluence, and the
  withstand scales directly with what is left.
- Treating a pinhole as a small partial-thickness defect because its
  area is small. Area sets the collected leakage-current; depth sets
  continuity, and a through-thickness defect of any area is a break.
- Reporting a negative remaining-thickness as a number and continuing
  the arithmetic. Once the wall is consumed the dielectric model no
  longer applies, and the correct output is a breach finding.
- Accepting a segment because no defect was recorded while the
  insulation-resistance minimum was never captured. An unset
  acceptance limit means the requirement is missing, which is a
  finding in its own right.
- Relaxing the required voltage factor so a marginal wall passes. The
  factor stays; only the floating-point comparison at the exact
  boundary is made tolerant.

## Behavior contract (gate 3)

The defect-categorization, erosion, remaining-thickness,
dielectric-withstand, insulation-resistance, defect-density and
leakage-current logic is exercised by the gate 3 contract test:
scripts/test_e2006_tether_insulation_continuity.py against
scripts/e2006_tether_insulation_continuity_logic.py (stdlib unittest,
offline). Run:
python3 scripts/test_e2006_tether_insulation_continuity.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 →