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 Power Measurement Process

ASecurity

Use when reviewing a solar-array string current-voltage measurement record. Verify that a string-level electrical performance measurement on a photovoltaic assembly was taken where ECSS-E-ST-20-08C clause 5.5.3.4.2 puts it: at the interface connector and referred to a declared reference temperature. Confirm the probing plane keeps the harness the string delivers through inside the loop, quantify the power a shorter plane overstates, refer the measured open-circuit voltage, short-circuit curre...

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

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-power-measurement-process --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of E2008 Power Measurement Process?

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

Security grade badge for E2008 Power Measurement Process
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ashfordeou-e2008-power-measurement-process/badge)](https://www.skillsdirectory.com/skills/ashfordeou-e2008-power-measurement-process)

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

Download with Pro
Files
SKILL.md
---
name: e2008-power-measurement-process
description: "Use when reviewing a solar-array string current-voltage measurement record. Verify that a string-level electrical performance measurement on a photovoltaic assembly was taken where ECSS-E-ST-20-08C clause 5.5.3.4.2 puts it: at the interface connector and referred to a declared reference temperature. Confirm the probing plane keeps the harness the string delivers through inside the loop, quantify the power a shorter plane overstates, refer the measured open-circuit voltage, short-circuit current and maximum power to the reference with the declared coefficients, and reject a correction reaching too far from it to be credible. Trigger: ecss, e-st-20-08c, clause-5-5-3-4-2, solar-array-string-iv-measurement, interface-connector-measurement-plane, string-reference-temperature-correction, harness-voltage-drop-allocation, string-maximum-power-referral."
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-power-measurement-process, solar-array-string-iv-measurement, interface-connector-measurement-plane, string-reference-temperature-correction, harness-voltage-drop-allocation, string-maximum-power-referral]
  version: 0.1.0
  author: Aero Agent Skills
---

# ECSS Photovoltaic Assemblies -- Power Measurement Process (space-systems/ecss/e2008-power-measurement-process)

Use when the task is the clause 5.5.3.4.2 measurement process of
ECSS-E-ST-20-08C -- judging whether a string-level electrical
performance measurement was taken the way the clause requires: at the
interface connector the assembly actually delivers through, swept by
instrumentation that brackets the string's own curve, and referred to a
declared reference temperature by a correction that stays inside the
window its coefficients were fitted in.

## Domain quick reference

- The interface connector is the plane the rest of the spacecraft sees.
  Power measured anywhere upstream of it is power the string generates,
  not power it delivers, and the difference is the resistive loss of
  everything in between.
- Which plane was probed decides which segments sit outside the
  measurement loop. A bus-bar probe leaves the connector harness out; a
  cell-level probe leaves the string interconnect out as well. Each
  omitted segment takes a share of the delivered power that the record
  then never charges to the string.
- The uncharged loss goes as the square of the working current, so it
  grows far faster than the voltage drop the same segment shows. A
  harness that looks negligible on a voltmeter can still be a
  significant fraction of the delivered power on a high-current string.
- A measurement carries the temperature it was taken at. Open-circuit
  voltage falls as the article warms, short-circuit current rises
  slightly, and maximum power falls, so three different coefficients
  refer three different quantities back to the same reference point.
- Correcting is not extrapolating. The coefficients are linear fits
  valid near the reference; a measurement far enough away is corrected
  by a term large enough that the fit itself dominates the uncertainty,
  and that is a finding rather than a number to publish.
- A sweep that does not reach past the open-circuit voltage and the
  short-circuit current never brackets the maximum-power knee, and one
  with too few points cannot locate it. Both leave the reported maximum
  power unsupported whatever plane it was measured at.

## Workflow

1. Validate the policy and the string definition: reference temperature,
   extrapolation limit, sweep density, cell and string counts, and the
   identifier of the connector the string delivers through. A string
   with no named interface connector cannot be measured at one.
2. Validate the declared measurement plane against the recognised set,
   rejecting an unrecognised one rather than treating it as the
   connector.
3. Refer the measured open-circuit voltage, short-circuit current and
   maximum power to the reference temperature with their own declared
   coefficients, and refuse a correction that drives the power
   non-physical.
4. Resolve the series resistance the plane left outside the loop from
   the declared harness segments, and require a resistance for every
   segment the plane omits rather than silently treating it as zero.
5. Charge that resistance at the corrected working current to get the
   power the record overstates and the voltage drop it hides, then
   subtract it to give the power actually available at the connector.
6. Check the sweep spans both ends of the string curve and carries
   enough points, and check the correction span against the
   extrapolation limit. A span landing exactly on the limit is credible;
   the comparison tolerance absorbs representation error.
7. Close on one verdict in order of precedence: instrumentation
   inadequate, plane short of the interface connector, extrapolation
   excessive, or measured at the interface connector -- with every
   finding reported, not only the one that set the verdict.

## Pitfalls

- Publishing the measured maximum power as the string's performance. It
  is the performance of the article at the laboratory temperature at the
  plane the probe happened to sit on, and neither of those is what the
  clause asks to be reported.
- Treating an undeclared harness segment as zero resistance. It makes a
  cell-level probe look identical to a connector measurement, which is
  precisely the error the plane check exists to catch.
- Judging a harness by its voltage drop. The drop is linear in current
  and the loss is quadratic, so a segment that drops a tolerable
  fraction of a volt can still remove a real share of the power.
- Correcting a badly off-reference measurement and reporting the result
  without the span. A large correction is not wrong by itself, but it
  carries an uncertainty the corrected number no longer shows.
- Accepting a maximum power from a sweep that stopped short of
  open circuit. The knee was never bracketed, so the reported maximum is
  the largest point the sweep happened to reach.

## Behavior contract (gate 3)

The policy and string validation, plane resolution and unmeasured
resistance, harness loss and drop, the three temperature corrections,
extrapolation span, sweep span and density checks, and the ordered
process verdict are exercised by the gate 3 contract test:
scripts/test_e2008_power_measurement_process.py against
scripts/e2008_power_measurement_process_logic.py (stdlib unittest,
offline). Run:
python3 scripts/test_e2008_power_measurement_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 →