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

E2008 Reverse Bias Burn In

ASecurity

Use when planning or reviewing a diode reverse bias soak before the lot is accepted. Assess whether a reverse bias burn-in under ECSS-E-ST-20-08C clause 12.6.7.3.1 is the high temperature blocking soak the clause describes or a differently stressed run wearing its name: confirm the cathode is held positive with respect to the anode, size the applied blocking voltage against the rating, derive the junction temperature the leakage self-heating produces, hold the soak inside its window up to the...

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

Works with

claude codeterminal

Security Analysis

A100/100

Scanned 9/27/2026

Install to Claude Code

$npx -y skills add ashfordeOU/aero-agent-skills --skill e2008-reverse-bias-burn-in --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of E2008 Reverse Bias Burn In?

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

Security grade badge for E2008 Reverse Bias Burn In
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ashfordeou-e2008-reverse-bias-burn-in/badge)](https://www.skillsdirectory.com/skills/ashfordeou-e2008-reverse-bias-burn-in)

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

Download with Pro
Files
SKILL.md
---
name: e2008-reverse-bias-burn-in
description: "Use when planning or reviewing a diode reverse bias soak before the lot is accepted. Assess whether a reverse bias burn-in under ECSS-E-ST-20-08C clause 12.6.7.3.1 is the high temperature blocking soak the clause describes or a differently stressed run wearing its name: confirm the cathode is held positive with respect to the anode, size the applied blocking voltage against the rating, derive the junction temperature the leakage self-heating produces, hold the soak inside its window up to the forty-eight hour ceiling, and separate devices whose leakage drifted past the drift limit from a lot whose drift share condemns the build. Trigger: ecss, e-st-20-08c-clause-12-6-7-3-1, reverse-bias-burn-in-cathode-positive, reverse-bias-burn-in-forty-eight-hour-ceiling, reverse-bias-burn-in-voltage-ratio, reverse-bias-burn-in-leakage-drift, reverse-bias-burn-in-junction-temperature."
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-08-photovoltaic-assembly-scope, e2008-reverse-bias-burn-in, reverse-bias-burn-in-cathode-positive, reverse-bias-burn-in-forty-eight-hour-ceiling, reverse-bias-burn-in-voltage-ratio, reverse-bias-burn-in-leakage-drift, reverse-bias-burn-in-junction-temperature]
  version: 0.1.0
  author: Aero Agent Skills
---

# ECSS Photovoltaic Assemblies -- Reverse Bias Burn-in (space-systems/ecss/e2008-reverse-bias-burn-in)

Use when the task is to plan or defend a reverse bias soak on a diode lot
under ECSS-E-ST-20-08C clause 12.6.7.3.1 -- held which way round, how
hard, how hot, for how long, and what the leakage afterwards says.

## Domain quick reference

- The soak holds the junction blocking, not conducting: the cathode is
  positive with respect to the anode for the whole run. Reverse that
  connection and the devices get a forward soak with a reverse bias
  label on it, stressing a different mechanism entirely.
- This screen is bounded above, and that is what separates it from a
  forward burn-in. A forward soak is sized by a floor -- run it long
  enough. A reverse bias soak carries a ceiling: no more than forty-eight
  hours.
- The ceiling is not administrative. The stress is the blocking field
  across the junction plus the temperature, and nothing about the run
  self-limits, so a soak left going degrades the passivation it was
  meant to interrogate and the lot arrives worse than it started.
- The applied blocking voltage is judged as a share of the rating.
  Screening wants a high share; a share reaching the rating is a
  breakdown test, and the devices that fail it were not defective.
- A blocking junction is not a cold one. Reverse leakage across a large
  blocking voltage still dissipates power, and at a high case
  temperature that self-heating is what carries the junction past its
  limit.
- The soak has to be hot to work at all. Below the case temperature
  floor the leakage mechanisms the screen depends on are not activated
  and the run is a long wait.
- Leakage drift is the reading that matters. A junction with a
  passivation flaw or an ionic contaminant leaks further after the soak
  than before it, and the ratio of the two readings is the screen.
- Removing drifted devices is the exercise working. A lot that sheds
  more than a small share is a different finding: the build is in
  question, and the survivors do not inherit a clean sheet from it.

## Workflow

1. Validate the soak policy first: soak window, voltage-ratio limit,
   case temperature floor, junction ceiling, drift limit and lot reject
   limit. A ratio limit reaching the rating is refused rather than used,
   because it would make a breakdown test pass as a burn-in.
2. Take polarity before anything else and stop there if it is wrong. A
   forward or unbiased connection makes every later quantity a
   description of a run that was not this run.
3. Derive the blocking voltage from the terminal difference and size it
   against the rating.
4. Derive the leakage dissipation and the junction temperature it
   produces on top of the case temperature, and compare both the
   junction and the voltage share against their limits.
5. Check the case temperature against its floor separately: a soak can be
   correctly biased and simply too cool to screen anything.
6. Hold the duration inside the window, both ends. A run landing exactly
   on the forty-eight hour ceiling is accepted; the comparison tolerance
   absorbs representation error and the limit does not move.
7. Take the leakage readings last: name every device past the drift
   limit, then compare the removed share against the lot reject limit.
8. Close on one verdict -- soak not applied, polarity wrong,
   overstressed, temperature low, duration out of window, lot rejected,
   or soak complete -- reporting every inadequacy found, not only the
   first.

## Pitfalls

- Assuming the bench wired it the way the procedure says. Polarity is a
  measurement, not an assumption, and a swapped pair produces a
  plausible-looking log of the wrong test.
- Treating the forty-eight hours as a target to reach rather than a
  ceiling not to cross. Longer is not safer here; longer is damage.
- Turning the blocking voltage up towards the rating to buy margin. Past
  the share limit the run measures breakdown, and the devices it removes
  were not the defective ones.
- Calling a blocking junction thermally quiet. Leakage times a large
  blocking voltage is real dissipation, and it lands on a junction
  already sitting at a high case temperature.
- Reading a single post-soak leakage value. The screen is the ratio
  against that same device before the soak; an absolute reading alone
  cannot tell a leaky-by-design part from a part that moved.
- Letting the survivors inherit the lot conclusion. A lot beyond the
  reject limit is a lot finding, and screening the rest of it does not
  answer it.

## Behavior contract (gate 3)

The policy validation, the bias polarity and blocking voltage, the
voltage ratio against the rating, the leakage dissipation and junction
temperature, the soak window check at both ends, the per-device leakage
drift ratio, the drifted-device list and lot drift share, and the soak
verdict are exercised by the gate 3 contract test:
scripts/test_e2008_reverse_bias_burn_in.py against
scripts/e2008_reverse_bias_burn_in_logic.py (stdlib unittest, offline).
Run: python3 scripts/test_e2008_reverse_bias_burn_in.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 →