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 Reflectance Cut Off Requirement

ASecurity

Use when a measured coverglass cut-off has to become an acceptance verdict. Verify that the reflectance cut-off wavelength measured on a coverglass agrees with the figure fixed in the coverglass source control drawing per ECSS-E-ST-20-08C clause 8.7.5.3.3: refuse a requirement carrying no drawing reference, locate the reflecting plateau in each measured spectrum, interpolate the long-wavelength crossing that defines the cut-off, compare every article against the drawing value and its toleranc...

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

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-reflectance-cut-off-requirement --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of E2008 Reflectance Cut Off Requirement?

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

Security grade badge for E2008 Reflectance Cut Off Requirement
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ashfordeou-e2008-reflectance-cut-off-requirement/badge)](https://www.skillsdirectory.com/skills/ashfordeou-e2008-reflectance-cut-off-requirement)

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

Download with Pro
Files
SKILL.md
---
name: e2008-reflectance-cut-off-requirement
description: "Use when a measured coverglass cut-off has to become an acceptance verdict. Verify that the reflectance cut-off wavelength measured on a coverglass agrees with the figure fixed in the coverglass source control drawing per ECSS-E-ST-20-08C clause 8.7.5.3.3: refuse a requirement carrying no drawing reference, locate the reflecting plateau in each measured spectrum, interpolate the long-wavelength crossing that defines the cut-off, compare every article against the drawing value and its tolerance band with a tie admissible, report the deviation and the share of tolerance consumed, and raise spread and one-sided-bias advisories a pass would otherwise hide. Trigger: ecss, e-st-20-08c-clause-8-7-5-3-3, coverglass-reflectance-cut-off-wavelength, coverglass-source-control-drawing-value, cut-off-crossing-interpolation, coverglass-cut-off-tolerance-band, coverglass-cut-off-bias-advisory."
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-reflectance-cut-off-requirement, e-st-20-08c, coverglass-reflectance-cut-off-wavelength, coverglass-source-control-drawing-value, cut-off-crossing-interpolation, coverglass-cut-off-tolerance-band, coverglass-cut-off-bias-advisory]
  version: 0.1.0
  author: Aero Agent Skills
---

# ECSS Photovoltaic Assemblies -- Reflectance Cut-Off Requirement (space-systems/ecss/e2008-reflectance-cut-off-requirement)

Use when the task is the clause 8.7.5.3.3 acceptance decision of
ECSS-E-ST-20-08C: a filtered coverglass has been measured, and the
long-wavelength edge of its reflecting band is admissible only when it
agrees with the cut-off figure the coverglass source control drawing
fixes.

## Domain quick reference

- The figure comes from the source control drawing, not from the coating
  vendor's datasheet, not from house practice and not from the last
  build. A verdict quoted with no drawing reference behind it is not a
  verdict against this clause, so an unreferenced requirement closes the
  assessment instead of passing it.
- The cut-off is derived, not read. A reflectance scan is a sampled
  curve and the edge almost never lands on a sampled wavelength, so the
  edge is the interpolated wavelength at which the long-wavelength flank
  falls through a crossing level. Quoting the nearest sampled point
  instead quantises the answer to the step of the monochromator.
- The crossing level is formed from the band that was actually measured.
  Half of the reflecting plateau is the usual convention, and the
  plateau is the averaged run around the peak rather than the single
  highest sample, so one noisy point cannot set the level for the whole
  article.
- The convention has to travel with the number. A cut-off taken at half
  the plateau and a cut-off taken at a quarter of it are different
  wavelengths on the same coverglass, and a figure reported without its
  convention cannot be compared with the drawing at all.
- A scan that stops while the flank is still high has not measured a
  cut-off. Extrapolating past the last sample invents an edge, so the
  short scan is refused and sent back to the laboratory.
- The tolerance band is two-sided and often asymmetric. The share of the
  allowance a deviation consumed is reported against the side it landed
  on, because a two-nanometre excursion means something different on a
  plus-ten side than on a minus-two side.
- A lot verdict is not a lot description. Articles that all pass can
  still sit several nanometres apart, or all sit on the same side of the
  drawing value, and the second is a coating run bias rather than
  scatter. Both are advisories beside the verdict, not inside it.

## Workflow

1. Validate the evaluation policy: the crossing convention and its
   fraction, the plateau inclusion fraction, the minimum scan length and
   the advisory thresholds. An unrecognised convention is refused rather
   than defaulted.
2. Resolve the drawing requirement. An absent requirement, or one whose
   drawing reference is blank, closes immediately on requirement not
   established; a tolerance that is zero on both sides, or one that
   reaches zero wavelength, is a malformed requirement and is refused.
3. Normalise each measured scan: strictly increasing wavelengths, every
   reflectance a fraction of unity, and enough points to show a plateau
   and a flank.
4. Take the plateau as the averaged contiguous run around the peak, form
   the crossing level from it under the declared convention, and refuse a
   level that is not below the plateau.
5. Walk the flank from the end of the plateau to the first sample at or
   below the level, and interpolate the crossing linearly between that
   sample and the one before it.
6. Compare each article against the drawing value and its two-sided
   tolerance, admitting a tie, and report the signed deviation with the
   share of the side-specific allowance it consumed.
7. Close on one verdict -- requirement not established, cut-off outside
   the drawing tolerance, or cut-off meets the drawing -- and report the
   lot mean, the spread, the worst article and the spread and run-bias
   advisories alongside it.

## Pitfalls

- Comparing against a remembered wavelength. The drawing is the only
  source of the required cut-off, and a criterion applied from memory is
  a criterion nobody can audit.
- Reporting the nearest sampled wavelength as the cut-off. That makes
  the answer a property of the scan step, and two laboratories with
  different steps will disagree about identical hardware.
- Setting the crossing level from the single peak sample. One noisy
  point then moves the edge on an article whose band is perfectly
  ordinary.
- Extrapolating an edge out of a scan that ended while the flank was
  still high. The measurement simply did not reach the cut-off, and an
  invented edge is worse than a rerun.
- Folding an asymmetric tolerance into one number. The consumed share is
  only meaningful against the side the deviation actually landed on.
- Reporting a pass with no deviation figure. The verdict alone hides the
  difference between an article that grazed the band and one sitting on
  the drawing value, and the next build has nothing to compare with.
- Treating a one-sided offset as scatter. Every article high by the same
  couple of nanometres is a deposition run that drifted, and it belongs
  with the process, not silently inside a pass.
- Comparing a measurement with a band edge by bare arithmetic. The edge
  is a drawing figure combined with a tolerance, so a measurement
  exactly on it can evaluate a few units in the last place outside; the
  comparison absorbs that representation error while the tolerance stays
  untouched.

## Behavior contract (gate 3)

The policy validation, drawing requirement resolution, scan
normalisation, plateau and crossing-level derivation, flank
interpolation, the two-sided tolerance comparison with an admissible
tie, the consumed-allowance share, the lot mean, spread and worst
article, and the spread and run-bias advisories are exercised by the
gate 3 contract test:
scripts/test_e2008_reflectance_cut_off_requirement.py against
scripts/e2008_reflectance_cut_off_requirement_logic.py (stdlib
unittest, offline, deterministic). Run:
python3 scripts/test_e2008_reflectance_cut_off_requirement.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 →