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 Primary Standard Cells

ASecurity

Use when a simulator level is being set from primary standards, or an as-run setting has to be defended. Verify that the calibrated reference cells setting a simulator's illumination level satisfy ECSS-E-ST-20-08C clause 10.2.1: confirm each primary standard cites a recognised traceable calibration route and a certificate still valid on the test day, match the single-junction or component standard to the junction it sets, cover every junction of a multijunction article, carry the certificate ...

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

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-primary-standard-cells --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of E2008 Primary Standard Cells?

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

Security grade badge for E2008 Primary Standard Cells
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ashfordeou-e2008-primary-standard-cells/badge)](https://www.skillsdirectory.com/skills/ashfordeou-e2008-primary-standard-cells)

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

Download with Pro
Files
SKILL.md
---
name: e2008-primary-standard-cells
description: "Use when a simulator level is being set from primary standards, or an as-run setting has to be defended. Verify that the calibrated reference cells setting a simulator's illumination level satisfy ECSS-E-ST-20-08C clause 10.2.1: confirm each primary standard cites a recognised traceable calibration route and a certificate still valid on the test day, match the single-junction or component standard to the junction it sets, cover every junction of a multijunction article, carry the certificate current across to the temperature the standard is actually at, and hold the residual level error inside tolerance with its sign. Trigger: ecss, e-st-20-08c-clause-10-2-1, primary-standard-reference-cell, component-cell-junction-coverage, reference-cell-calibration-validity, simulator-illumination-level-setting, reference-cell-temperature-correction."
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-primary-standard-cells, primary-standard-reference-cell, component-cell-junction-coverage, reference-cell-calibration-validity, simulator-illumination-level-setting, reference-cell-temperature-correction]
  version: 0.1.0
  author: Aero Agent Skills
---

# ECSS Photovoltaic Assemblies -- Primary Standard Cells (space-systems/ecss/e2008-primary-standard-cells)

Use when the task is clause 10.2.1 of ECSS-E-ST-20-08C -- the calibrated
single junction or component reference cells a simulator's illumination
level is set against, and whether a level set from them can be defended.

## Domain quick reference

- A primary standard is a calibration, not a cell. What makes it primary
  is the route the certificate names -- a space-flown, high-altitude
  aircraft, balloon or world-radiometric-reference calibration -- so a
  reference cell citing a vendor datasheet, or carrying no certificate
  reference at all, has a number written on it and nothing behind it.
- The certificate has a life. A standard in date on the day of the test
  is what matters, not one that was in date when the campaign was
  planned, so the validity is judged against the test date and a
  certificate close to lapsing is said aloud while it still passes.
- The junction has to match. A multijunction article is current limited
  by whichever junction sees least of its own part of the spectrum, so a
  single-junction standard sets one lamp channel and leaves the others
  where they happened to be. Every required junction gets a standard
  representing it, and a junction with none is named.
- Temperature moves the target, not the reading. The certificate fixes
  the short-circuit current at a reference temperature, so the value the
  standard should read while it sits warmer or colder is the certificate
  value carried across by its own coefficient. Set the lamp to the bare
  certificate value at the wrong temperature and the whole coefficient
  times the offset lands in the illumination level.
- The residual error is a deliverable, not a leftover. Every performance
  measurement taken afterwards inherits it, and it carries a sign: a
  level set two per cent high and one set two per cent low bias every
  later result in opposite directions.
- A standard offered for a junction nobody asked about is reported as
  unused rather than silently counted, because it usually means the
  article's junction list and the standards drawer disagree.

## Workflow

1. Validate the standard cell policy first: the level error tolerance,
   the certificate validity in days, the window inside which a validity
   counts as marginal and the residual error band. A marginal window
   wider than the validity itself, or a marginal band wider than the
   tolerance, is refused rather than used.
2. Read every offered standard: non-blank identifier, no duplicate
   identifier, a named junction, a certificate reference, a calibration
   route, an ISO calibration date, a positive calibrated current and a
   finite temperature coefficient.
3. Judge traceability before anything else. A standard whose route is
   not a recognised primary one, or whose certificate reference is
   blank, closes the assessment -- name every such standard, not the
   first found.
4. Judge the certificate validity against the test date. A calibration
   dated after the test is a record defect and is refused outright; a
   lapsed one closes the assessment; one inside the marginal window
   passes with an advisory.
5. Match the standards to the junctions the article needs set. A missing
   junction closes the assessment; a standard for no required junction
   is reported as unused.
6. For each as-set record, carry the certificate current across to the
   temperature the standard was at, take the signed level error against
   that corrected target, and hold every one inside tolerance.
7. Close on one verdict: traceability not established, calibration
   expired, junction coverage incomplete, level out of tolerance, or
   level set -- reporting the worst residual error and its sign beside
   it.

## Pitfalls

- Setting the lamp so the standard reads its certificate current while
  the cell sits well off the reference temperature. It is the single
  most common way a correctly calibrated standard produces a wrong
  illumination level.
- Setting a multijunction article from one standard. The junctions that
  were never set are exactly the ones that can limit the article, and
  the setting looks clean because nothing measured them.
- Reading a certificate number as traceability. The route is what makes
  the standard primary; the number only identifies the paperwork.
- Judging validity against the planning date. Campaigns slip, and a
  certificate that was in date in the schedule is regularly out of date
  on the bench.
- Collapsing the residual error into a pass. It has a sign and it biases
  every measurement taken afterwards in one direction.
- Comparing a derived error fraction against its tolerance by bare
  arithmetic. Both sides are floats that can land a unit in the last
  place either side of the bound, so the comparison absorbs that while
  the tolerance itself is never relaxed.

## Behavior contract (gate 3)

The policy validation, standard cell record validation with duplicate
rejection, the traceable-route test, the certificate age and validity
against the test date, the marginal validity advisory, the junction
coverage with missing and unused standards, the temperature-corrected
target current, the signed level error, the worst setting and the
illumination verdict are exercised by the gate 3 contract test:
scripts/test_e2008_primary_standard_cells.py against
scripts/e2008_primary_standard_cells_logic.py (stdlib unittest,
offline). Run:
python3 scripts/test_e2008_primary_standard_cells.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 →