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 Visual Inspection Process

ASecurity

Use when an inspection setup must be shown adequate before its defect calls are trusted. Evaluate whether the equipment and the viewing approach used to examine solar cell assemblies can resolve the defects the criteria name, under ECSS-E-ST-20-08C clause 6.4.3.1.2: derive the resolved feature from acuity and working distance for a visual station or from field of view and sensor sampling for an imaging one, grow it by the foreshortening an off-normal viewing angle imposes, compare that agains...

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

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-visual-inspection-process --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of E2008 Sca Visual Inspection Process?

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

Security grade badge for E2008 Sca Visual Inspection Process
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ashfordeou-e2008-sca-visual-inspection-process/badge)](https://www.skillsdirectory.com/skills/ashfordeou-e2008-sca-visual-inspection-process)

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

Download with Pro
Files
SKILL.md
---
name: e2008-sca-visual-inspection-process
description: "Use when an inspection setup must be shown adequate before its defect calls are trusted. Evaluate whether the equipment and the viewing approach used to examine solar cell assemblies can resolve the defects the criteria name, under ECSS-E-ST-20-08C clause 6.4.3.1.2: derive the resolved feature from acuity and working distance for a visual station or from field of view and sensor sampling for an imaging one, grow it by the foreshortening an off-normal viewing angle imposes, compare that against the smallest criterion dimension with a detection margin, check illumination and the faces the approach actually reaches, and report the size every later defect call is bounded at. Trigger: ecss, e-st-20-08c, clause-6-4-3-1-2, sca-inspection-resolution-adequacy, visual-station-magnification-check, imaging-sensor-sampling-limit, sca-viewing-angle-foreshortening, inspection-face-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-08-photovoltaic-assembly-scope, e2008-sca-visual-inspection-process, sca-inspection-resolution-adequacy, visual-station-magnification-check, imaging-sensor-sampling-limit, sca-viewing-angle-foreshortening, inspection-face-coverage, sca-defect-detection-margin]
  version: 0.1.0
  author: Aero Agent Skills
---

# ECSS Photovoltaic -- Cell Assembly Visual Inspection Process (space-systems/ecss/e2008-sca-visual-inspection-process)

Use when the task is the inspection method of ECSS-E-ST-20-08C clause
6.4.3.1.2 -- the resolution the equipment provides and the way the assembly is
looked at, turned into a statement about what the examination can and cannot
support.

## Domain quick reference

- This clause governs the instrument, not the verdict. Everything it settles is
  a bound on the defect calls that come later: an examination cannot report a
  feature it could not resolve, and a face nobody viewed contributes nothing
  however good the optics were.
- The three station kinds reach their resolution by different arithmetic. An
  unaided station is limited by the eye -- roughly one arc minute of acuity
  converted to a length at the working distance, which is about a tenth of a
  millimetre at arm's length and coarsens in direct proportion as the inspector
  stands back.
- A magnified station divides that length by its power. A station calling
  itself magnified and running at unity is an unaided station with a lens in
  front of it, and crediting it with a magnification it does not have is how a
  setup passes on paper and misses defects in the shop.
- An imaging station is limited by sampling rather than by acuity. The field of
  view spread over the sensor gives the pitch at the article, and a feature
  needs more than one sample to exist in the image, so the resolved feature is
  the pitch times the samples a feature must span. Doubling the field of view
  at a fixed sensor halves the resolution.
- The viewing approach then degrades whatever the station produced. A surface
  looked at off its normal is foreshortened, so a feature presents a shorter
  extent by the cosine of the incidence angle and the effective resolved
  feature grows as the reciprocal of that cosine. Sixty degrees off normal
  costs a factor of two, which is enough to move a comfortable station to the
  edge of its criterion without anything on the bench changing.
- Illumination is the other half of the optics. Below an illuminance floor a
  look stops being a detection activity whatever the instrument in front of it
  is capable of, so an under-lit station is not credited even when its
  resolution is ample.
- Adequacy is a margin question, not an equality. Resolving a feature at
  exactly its own size is a coincidence rather than a detection, so a station
  is credited only when it resolves the smallest criterion feature several
  times over; a station between those two points is marginal and does not carry
  a face on its own.
- Coverage closes the assessment. Every declared face needs at least one
  credited station, and the coarsest face bound is the size the whole
  inspection statement is worth.

## Workflow

1. Validate the policy: acuity, samples per feature, the detection margin, the
   illuminance floor, the incidence limit and the working distance limit.
2. Per station, take the resolved feature from the arithmetic its kind uses,
   rejecting a kind and a magnification that contradict each other.
3. Apply the foreshortening factor for the incidence angle to get the effective
   resolved feature -- the number every later comparison uses.
4. Compare it against the smallest criterion dimension divided by the detection
   margin. Inside it the station is capable; between there and the bare
   criterion it is marginal; beyond the criterion it is not capable at all.
5. Check the viewing conditions separately -- illuminance, incidence, working
   distance -- and send a station that fails one to review rather than letting
   its resolution alone carry it.
6. Map credited stations onto declared faces, keeping the finest bound per face
   and naming any face no credited station reaches.
7. Close with the process verdict, the stations that were not credited, and the
   coarsest face bound, which is what every defect call from this setup is
   worth.

## Pitfalls

- Quoting a datasheet resolution and stopping. The number on the instrument is
  the normal-incidence figure; what governs is the effective one after the
  viewing angle has had its say.
- Treating the incidence angle as a tick-box limit. It is a multiplier on the
  resolved feature, and a station inside the angle limit can still have lost
  its detection margin to it.
- Crediting a magnified station running at unity. It resolves exactly what the
  unaided eye does, and recording a magnification it does not have inflates
  the whole setup.
- Sizing an imaging station by pixel count alone. What matters is the pitch at
  the article, so the same sensor over a wider field resolves proportionally
  less.
- Letting one sample per feature count as resolving it. A feature landing on a
  single pixel is not distinguishable from noise.
- Accepting a station because it resolves the criterion exactly. That is a
  coincidence, not detection, and it leaves nothing for the variation in a real
  article.
- Reporting an adequate setup with a face nobody reached. The stations can all
  be excellent and the assembly still unexamined on one side.
- Comparing an effective resolved feature with a required one by bare
  arithmetic. The first comes from a trigonometric conversion and a cosine
  division and the second from a criterion divided by a margin, so a station
  sitting exactly on the bound can evaluate a few units in the last place above
  it; the comparison absorbs that representation error while the bound stays
  untouched.

## Behavior contract (gate 3)

The per-kind resolution derivations, the unity-magnification rejection, the
sampling limit, the incidence foreshortening factor, the capable/marginal/not
capable margin split, the viewing condition checks and the per-face coverage
rollup are exercised by the gate 3 contract test:
scripts/test_e2008_sca_visual_inspection_process.py against
scripts/e2008_sca_visual_inspection_process_logic.py (stdlib unittest,
offline). Run:
python3 scripts/test_e2008_sca_visual_inspection_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 →