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 Solar Cell Attachment Property

ASecurity

Use when an attachment qualification record has to be sentenced. Verify that bonded cell assemblies stay attached to the panel through the whole test sequence and on to mission life under ECSS-E-ST-20-08C clause 5.3.3.11.2: anchor every later measurement to the as-bonded reference, walk the humidity, solar-array-thermal-cycling, vibration, acoustic and thermal-vacuum stages in order, hold both an overall retention floor and a per-stage drop allowance so one punishing environment cannot hide i...

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

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 e2008-solar-cell-attachment-property --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of E2008 Solar Cell Attachment Property?

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

Security grade badge for E2008 Solar Cell Attachment Property
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ashfordeou-e2008-solar-cell-attachment-property/badge)](https://www.skillsdirectory.com/skills/ashfordeou-e2008-solar-cell-attachment-property)

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

Download with Pro
Files
SKILL.md
---
name: e2008-solar-cell-attachment-property
description: "Use when an attachment qualification record has to be sentenced. Verify that bonded cell assemblies stay attached to the panel through the whole test sequence and on to mission life under ECSS-E-ST-20-08C clause 5.3.3.11.2: anchor every later measurement to the as-bonded reference, walk the humidity, solar-array-thermal-cycling, vibration, acoustic and thermal-vacuum stages in order, hold both an overall retention floor and a per-stage drop allowance so one punishing environment cannot hide inside a gentle average, take any detached cell assembly as an outright failure of the property, then check the cycles actually run against the factored mission cycles and extrapolate the surviving strength to end of life. Trigger: ecss, e-st-20-electrical-scope, solar-cell-attachment-property, cell-attachment-retention, solar-array-thermal-cycling, panel-detachment-screening, attachment-life-extrapolation, mission-cycle-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-solar-cell-attachment-property, solar-cell-attachment-property, cell-attachment-retention, solar-array-thermal-cycling, panel-detachment-screening, attachment-life-extrapolation, mission-cycle-coverage]
  version: 0.1.0
  author: Aero Agent Skills
---

# ECSS Photovoltaic — Solar Cell Attachment Property (space-systems/ecss/e2008-solar-cell-attachment-property)

Use when the task is the attachment property of ECSS-E-ST-20-08C clause
5.3.3.11.2 -- showing that the cell assemblies stay bonded to the panel
for the whole test sequence and for the mission after it, not merely
that they were bonded on the day they were laid up.

## Domain quick reference

- One as-bonded number does not answer this clause. The property is
  retention: the panel has still to face humidity storage, a vibration
  and acoustic run, a thermal-vacuum soak and years of
  solar-array-thermal-cycling, and the attachment has to survive all of
  it.
- The evidence is a stage-by-stage record anchored to the as-bonded
  reference. Each later stage carries the adherence measured on its own
  coupons and the number of cell assemblies that came off during it.
- Two retention checks run together and catch different failures. The
  overall check compares each stage against the as-bonded reference and
  catches slow cumulative loss. The per-stage check compares a stage
  against the one before it and catches a single punishing environment
  that a gentle average would otherwise absorb.
- A detached cell assembly is not a low data point, it is the failure
  itself. Any detachment at any stage breaks the property whatever the
  surviving coupons measured, so it is counted separately from the
  strength numbers.
- A strength gain between stages is recorded as no drop rather than as
  a negative one. Coupon scatter routinely produces a higher reading
  later in the sequence, and crediting it would let a genuine loss in
  the next stage net out to nothing.
- Mission life is a cycle count, not a date. The cycles actually run
  have to cover the mission cycles multiplied by the declared test
  factor; where they fall short, the surviving strength is extrapolated
  across the missing decades of cycles and compared against the minimum
  attachment strength.
- The retention floor, the per-stage allowance, the test factor and the
  per-decade degradation are a declared project policy rather than
  physical constants, so they are stated with the result.

## Workflow

1. Take the as-bonded reference as the first stage and reject a record
   that starts anywhere else. Without that anchor, retention has no
   denominator and the later stages measure nothing.
2. Walk the remaining stages in the order they were run. Compute each
   stage's retention against the reference and its drop against the
   preceding stage, and carry the detached-cell count.
3. Sentence each stage on its own: detachments within the allowance,
   retention above the floor, drop within the per-stage allowance.
   Report the stage that failed by name so the retest is scoped to it.
4. Aggregate the detachments across the whole sequence. A single
   detachment anywhere is enough to withhold the property.
5. Compare the cycles run against the mission cycles times the test
   factor. Where the test reached or passed the mission, the measured
   strength stands; where it stopped short, degrade it across the
   missing decades and never credit a recovery.
6. Close with a verdict: attachment retained, not retained with the
   reasons listed, or not evaluated when only the reference was ever
   measured.

## Pitfalls

- Reporting the mean retention over the sequence. It hides the one
  environment that did the damage, which is the only stage a corrective
  action can be aimed at.
- Treating a detachment as a low coupon result. The property is that the
  assemblies stay on; a cell assembly that came off has already failed
  it, and averaging it away with the survivors converts a failure into a
  data point.
- Stopping at the last test measurement. A test that ran fewer cycles
  than the mission has demonstrated only the cycles it ran, and the
  remaining decades are exactly where a bondline creeps.
- Crediting a strength gain between stages. Coupon scatter produces
  them, and letting one offset a later drop lets a real loss disappear
  in the arithmetic.
- Comparing retention or an end-of-life strength against its floor by
  bare arithmetic. Retention is a quotient and the extrapolation is a
  power, so a case meant to sit exactly on the floor can land a few
  units in the last place below it; the comparison absorbs that
  representation error while the floor stays untouched.

## Behavior contract (gate 3)

The reference anchoring, per-stage retention and drop checks,
detachment aggregation, mission-cycle coverage, end-of-life
extrapolation and the retention verdict are exercised by the gate 3
contract test:
scripts/test_e2008_solar_cell_attachment_property.py against
scripts/e2008_solar_cell_attachment_property_logic.py (stdlib unittest,
offline). Run:
python3 scripts/test_e2008_solar_cell_attachment_property.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 →