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 Sca Spectral Response Process

ASecurity

Use when a pre-irradiation data sheet, reference cell comparison record or irradiation campaign baseline has to be assessed. Evaluate the pre-irradiation short circuit current baseline that clause 6.4.3.5.2 of ECSS-E-ST-20-08C asks for on solar cell assemblies: confirm the reference device is traceable and inside its calibration interval, hold the bench irradiance and temperature to the window a correction stays valid in, translate every sample reading back to reference conditions, express it...

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 e2008-sca-spectral-response-process --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of E2008 Sca Spectral Response Process?

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

Security grade badge for E2008 Sca Spectral Response Process
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ashfordeou-e2008-sca-spectral-response-process/badge)](https://www.skillsdirectory.com/skills/ashfordeou-e2008-sca-spectral-response-process)

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

Download with Pro
Files
SKILL.md
---
name: e2008-sca-spectral-response-process
description: "Use when a pre-irradiation data sheet, reference cell comparison record or irradiation campaign baseline has to be assessed. Evaluate the pre-irradiation short circuit current baseline that clause 6.4.3.5.2 of ECSS-E-ST-20-08C asks for on solar cell assemblies: confirm the reference device is traceable and inside its calibration interval, hold the bench irradiance and temperature to the window a correction stays valid in, translate every sample reading back to reference conditions, express it as a ratio against the corrected reference reading, and hold that ratio inside the declared band before any exposure starts. Trigger: ecss, e-st-20-08c, sca-spectral-response-process, sca-pre-irradiation-short-circuit-current-baseline, solar-cell-assembly-reference-cell-comparison, sca-reference-condition-current-correction, sca-irradiation-baseline-coverage."
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, e2008-sca-spectral-response-process, e-st-20-08c, sca-spectral-response-process, sca-pre-irradiation-short-circuit-current-baseline, solar-cell-assembly-reference-cell-comparison, sca-reference-condition-current-correction, sca-irradiation-baseline-coverage]
  version: 0.1.0
  author: Aero Agent Skills
---

# ECSS Solar Cell Assemblies — Pre-Irradiation Current Baseline (space-systems/ecss/e2008-sca-spectral-response-process)

Use when the task is clause 6.4.3.5.2 of ECSS-E-ST-20-08C: the short circuit
current of the test samples measured and held against a reference device
before an irradiation campaign begins. This leaf decides whether the
reference can be leaned on at all, translates every reading to reference
conditions, expresses each sample against the reference, and names the
sample that is about to be exposed with no baseline behind it.

## Domain quick reference

- The baseline is the whole point. Post-irradiation data means nothing on
  its own; the campaign reports degradation, which is a ratio against a
  reading taken before exposure. A sample irradiated without that reading
  is unusable for the rest of the campaign no matter how it later behaves.
- A reference device out of calibration does not produce a slightly wrong
  answer, it produces an unsupported one. Every sample ratio shares the
  same reference reading, so one lapsed calibration moves the whole
  sample set together and no amount of scatter analysis reveals it.
- The reading belongs to the bench, not to the sample. Short circuit
  current tracks irradiance almost linearly and drifts with temperature,
  so two samples read on different days are only comparable after both are
  translated back to reference irradiance and reference temperature.
- The translation is an interpolation inside a window. Far off reference
  irradiance or far off reference temperature it becomes an extrapolation
  of the declared coefficients, and the corrected value then carries an
  error nobody quantified; the reading is refused as a condition failure
  rather than corrected and reported.
- The comparison is a ratio, not a difference. Sample and reference are
  different devices with different areas, so only the ratio against the
  corrected reference reading carries meaning, and only inside the band
  the campaign declared for it.

## Workflow

1. Validate the reference device: a traceable identifier, a calibration
   still inside its declared interval, and a reading taken inside the
   correction window. Each failure is a finding against the whole set.
2. Translate the reference reading to reference irradiance and reference
   temperature, and keep that one corrected current as the denominator for
   every sample in the set.
3. For each sample, decide first whether its bench conditions are
   correctable at all, then translate its reading back to reference
   conditions.
4. Express the corrected sample current as a ratio against the corrected
   reference current and hold that ratio inside the declared band,
   absorbing floating-point representation error at the band edges with a
   named tolerance rather than by widening the band.
5. Flag any sample read after exposure started; it is a post-irradiation
   number sitting in a pre-irradiation column.
6. Reject a sample identifier that appears twice; two readings under one
   name make the set ambiguous rather than redundant.
7. Reconcile the samples read against the samples the campaign plans to
   expose, and report every identifier planned for exposure that never
   got a baseline.

## Pitfalls

- Comparing raw bench currents. A sample read on a brighter day outreads a
  better sample read on a dimmer one, and the band then rejects the wrong
  article.
- Treating the reference reading as a constant of the laboratory. It is a
  measurement like any other, taken at a particular irradiance and
  temperature, and it needs the same translation the samples get before it
  can serve as a denominator.
- Reading the ratio band as the only verdict. A set where every ratio sits
  inside the band but one planned sample was never read is not a clean
  baseline; it is a campaign about to lose a sample.
- Judging a ratio that lands exactly on a band edge by bare arithmetic.
  The ratio is computed from corrected currents, so an assembly built to
  the edge can land a few units in the last place outside it; the
  comparison absorbs that while the declared band stays as declared.
- Carrying on after a lapsed reference calibration because the scatter
  looks tight. Tight scatter around a wrong denominator is exactly what a
  common-mode reference error produces.

## Behavior contract (gate 3)

The reference device validation, the correction window, the translation to
reference conditions, the response ratio and its band, the post-exposure
and duplicate-identifier rejections and the planned-versus-read
reconciliation are exercised by the gate 3 contract test:
scripts/test_e2008_sca_spectral_response_process.py against
scripts/e2008_sca_spectral_response_process_logic.py (stdlib unittest,
offline). Run:
python3 scripts/test_e2008_sca_spectral_response_process.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 →