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 Charging Computer Model Content

ASecurity

Use when verify that a spacecraft-charging computer model offered as design-acceptance evidence carries the physical content required by ECSS-E-ST-20-06C clause 6.8.4: confirm the simulation represents ambient-electron-collection and ambient-ion-collection, photoemission on sunlit-surfaces, secondary-electron-emission by electrons and by ions, electron-backscatter, surface-conduction and bulk-conduction in dielectrics, radiation-induced-conductivity under penetrating-radiation, illumination-g...

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

Works with

claude codecli

Security Analysis

A100/100

Scanned 9/27/2026

Install to Claude Code

$npx -y skills add ashfordeOU/aero-agent-skills --skill e2006-charging-computer-model-content --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of E2006 Charging Computer Model Content?

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

Security grade badge for E2006 Charging Computer Model Content
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ashfordeou-e2006-charging-computer-model-content/badge)](https://www.skillsdirectory.com/skills/ashfordeou-e2006-charging-computer-model-content)

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

Download with Pro
Files
SKILL.md
---
name: e2006-charging-computer-model-content
description: "Use when verify that a spacecraft-charging computer model offered as design-acceptance evidence carries the physical content required by ECSS-E-ST-20-06C clause 6.8.4: confirm the simulation represents ambient-electron-collection and ambient-ion-collection, photoemission on sunlit-surfaces, secondary-electron-emission by electrons and by ions, electron-backscatter, surface-conduction and bulk-conduction in dielectrics, radiation-induced-conductivity under penetrating-radiation, illumination-geometry and wake-shadowing geometry, and any active-plasma-source current; confirm each represented effect carries its material-parameter set, that the current-balance solution closes on the floating-potential, and that the integration-step resolves the charging-time-constant. Trigger: ecss, e-st-20-electrical-scope, e2006-charging-computer-model-content, spacecraft-charging-model, charging-simulation-content, secondary-electron-emission, photoemission-current, radiation-induced-conductivity, current-balance-closure."
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-charging-computer-model-content, spacecraft-charging-model, charging-simulation-content, secondary-electron-emission, photoemission-current, radiation-induced-conductivity, current-balance-closure]
  version: 0.1.0
  author: Aero Agent Skills
---

# ECSS Spacecraft Charging — Computer Model Content (space-systems/ecss/e2006-charging-computer-model-content)

Use when the task is judging whether a spacecraft-charging simulation is
complete enough to carry design acceptance under ECSS-E-ST-20-06C clause
6.8.4 -- which physical effects the model represents, whether each one is
backed by a material-parameter set, and whether the numerical solution
actually closes.

## Domain quick reference

- Clause 6.8.4 governs model CONTENT, not model accuracy. A charging
  simulation used as acceptance evidence must represent every current
  that can reach or leave a surface in the declared environment. A model
  that omits an applicable effect is incomplete evidence regardless of
  how well it reproduces one test point.
- The current families are: environment-current (ambient-electron and
  ambient-ion collection from the plasma spectrum), emission-current
  (photoemission on illuminated surfaces, secondary-electron-emission
  driven by impacting electrons, secondary-electron-emission driven by
  impacting ions, electron-backscatter), charge-transport (surface-
  conduction, bulk-conduction and radiation-induced-conductivity inside
  dielectrics), geometry (illumination-geometry, and wake-shadowing
  geometry where a ram/wake structure exists), external-current (an
  active-plasma-source such as an electric-propulsion neutraliser or a
  plasma-contactor), and numerical (the current-balance solution for
  the floating-potential, and time-dependent integration where the
  analysis covers an eclipse-entry or substorm-onset transient).
- Applicability is configuration-driven. Photoemission and
  illumination-geometry are mandatory only for a configuration that
  sees sunlight; the conduction effects only where a dielectric is
  present; radiation-induced-conductivity only where that dielectric
  also sees penetrating-radiation; wake-shadowing geometry and
  ion-driven secondary-electron-emission only in a flowing-plasma
  regime such as a low-altitude orbit; time-dependent integration only
  for a transient analysis.
- Every represented emission or transport effect needs its own measured
  or referenced parameter set (photoelectron saturation current density,
  secondary-emission peak yield and peak energy, backscatter yield,
  surface and bulk resistivity, relative permittivity, the
  radiation-induced-conductivity coefficient and exponent). A named
  effect with no parameters behind it is a declaration, not model
  content.
- The current-balance residual must vanish at the converged
  floating-potential. The residual is a signed sum of collected and
  emitted currents, so it is compared against a tolerance scaled to the
  largest individual current, absorbed with a relative tolerance rather
  than an exact zero test.
- The integration-step of a transient run must be a small fraction of
  the charging-time-constant (surface capacitance times potential
  divided by net current density); a step that equals or exceeds that
  constant cannot resolve the charging transient it claims to predict.

## Workflow

1. Read the configuration: orbital regime, sunlit or eclipsed, presence
   of dielectric surfaces, presence of penetrating-radiation, presence
   of an active-plasma-source, and whether the analysis is transient.
   Reject an unrecognized regime or a non-boolean flag before the
   assessment starts.
2. Derive the required effect set from that configuration, then compare
   it against the effects the model declares. Anything required and
   absent is a content finding; anything declared but not required is
   recorded as extra scope, not as a fault.
3. For each declared effect that carries a parameter contract, check
   the parameter set exists and every value sits inside its physical
   range. A missing parameter and an out-of-range parameter are both
   findings.
4. Sum the converged current set and test the residual against a
   tolerance scaled to the largest contributing current; a residual
   outside that tolerance means the floating-potential solution did not
   close and the predicted potential is not evidence.
5. For a transient analysis, compute the charging-time-constant from
   surface capacitance, predicted potential and net current density,
   and confirm the integration-step is at or below the permitted
   fraction of it.
6. Aggregate: the model supports design acceptance only when the
   required-effect list, the parameter list, the balance check and the
   step check are all clear.

## Pitfalls

- Treating the effect list as fixed. A model that carries photoemission
  in a permanently-eclipsed configuration is not wrong, but a model
  without wake-shadowing geometry in a flowing-plasma regime is
  incomplete -- the required set follows the configuration.
- Accepting a named effect with an empty parameter set. Clause 6.8.4
  evidence needs the emission and transport coefficients behind each
  effect; a secondary-emission model with no peak yield and no peak
  energy computes nothing.
- Testing the current-balance residual against exact zero. The residual
  is a sum of signed currents spanning several decades, so a physically
  closed solution can land a few units in the last place away from
  zero; scale the tolerance to the largest current instead of widening
  the engineering criterion.
- Reading a converged potential as validated physics. Convergence says
  the solver closed on the currents it was given; if an applicable
  current family was never represented, the solution converges on the
  wrong problem.
- Choosing an integration-step from run-time convenience. A step above
  the charging-time-constant smears the eclipse-entry transient that
  the differential-charging conclusion rests on.

## Behavior contract (gate 3)

The configuration validation, required-effect derivation, parameter
range checking, current-balance closure and integration-step logic are
exercised by the gate 3 contract test:
scripts/test_e2006_charging_computer_model_content.py against
scripts/e2006_charging_computer_model_content_logic.py (stdlib
unittest, offline). Run:
python3 scripts/test_e2006_charging_computer_model_content.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 →