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

Q7001 Verification By Inspection

ASecurity

Determine what a visual or black-light cleanliness observation can actually substantiate. Use when a surface is being verified by eye under ECSS-Q-ST-70-01C and the question is whether the conditions support the size the requirement needs seen: compute the resolvable particle diameter from viewing distance and assumed acuity, grow it for illuminance below the reference level and for foreshortening away from normal, confirm the lamp sits in the long-wave ultraviolet band with enough irradiance...

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

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 q7001-verification-by-inspection --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Q7001 Verification By Inspection?

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

Security grade badge for Q7001 Verification By Inspection
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ashfordeou-q7001-verification-by-inspection/badge)](https://www.skillsdirectory.com/skills/ashfordeou-q7001-verification-by-inspection)

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

Download with Pro
Files
SKILL.md
---
name: q7001-verification-by-inspection
description: "Determine what a visual or black-light cleanliness observation can actually substantiate. Use when a surface is being verified by eye under ECSS-Q-ST-70-01C and the question is whether the conditions support the size the requirement needs seen: compute the resolvable particle diameter from viewing distance and assumed acuity, grow it for illuminance below the reference level and for foreshortening away from normal, confirm the lamp sits in the long-wave ultraviolet band with enough irradiance and a dark-adapted observer, reduce the fraction of surface covered, and return accept, re-clean or escalation to an instrumented method. Trigger: ecss, q-st-70-01c, cleanliness-visual-detectable-size, black-light-fluorescence-observation, uv-a-surface-irradiance, observer-dark-adaptation, cleanliness-inspection-coverage-fraction, visual-acuity-viewing-distance."
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, q-st-70-01-cleanliness-scope, q7001-verification-by-inspection, cleanliness-visual-detectable-size, black-light-fluorescence-observation, uv-a-surface-irradiance, observer-dark-adaptation, cleanliness-inspection-coverage-fraction]
  version: 0.1.0
  author: Aero Agent Skills
---

# ECSS Cleanliness -- Verification by Inspection (space-systems/ecss/q7001-verification-by-inspection)

Use when the task is the inspection route of cleanliness verification
under ECSS-Q-ST-70-01C: a surface is being looked at under white light
or a long-wave ultraviolet lamp, and the question is what that
observation is entitled to conclude about the cleanliness requirement
placed on it.

## Domain quick reference

- What the eye can resolve is geometry before it is anything else. The
  angular acuity assumed for the inspection, subtended at the viewing
  distance, fixes a chord; that chord is the smallest particle the
  observation can be about.
- Light removes acuity gradually. Below the illuminance the acuity
  assumption was stated at, the detectable size grows; above it the gain
  flattens and is not credited, so a brighter lamp does not buy a
  smaller detectable size.
- A surface seen at an angle is foreshortened. Viewing away from normal
  scales the detectable size by the reciprocal cosine, and a near
  grazing look is not an inspection geometry at all.
- Ultraviolet inspection has three separate conditions. The lamp has to
  sit in the long-wave band, the irradiance has to arrive at the
  surface rather than at the lamp housing, and the observer has to be
  dark adapted; any one of them failing invalidates the observation
  while the other two look fine.
- Coverage is part of the result. An observation over a third of a
  surface substantiates a third of it, and the fraction belongs in the
  record next to what was seen.
- An observation is not a measurement. When the conditions cannot reach
  the size the requirement needs seen, the honest outcome is escalation
  to an instrumented method, not a pass recorded under protest.

## Workflow

1. Compute the resolvable particle diameter from the viewing distance
   and the angular acuity assumed for the inspection, refusing an
   acuity beyond a degree as not an inspection assumption.
2. Grow that diameter by the illuminance derating and the viewing-angle
   derating to get the detectable size the conditions actually achieved.
3. Compare it with the size the requirement needs observed, absorbing
   representation error at the boundary with a named relative tolerance.
4. When the observation is under ultraviolet, grade the lamp wavelength
   against the long-wave band, the surface irradiance against its
   minimum and the observer dark adaptation against its minimum,
   raising a separate finding for each.
5. Reduce the inspected fraction of the surface and compare it with the
   coverage the verification claimed.
6. Grade the outcome: accept a substantiated clean observation,
   re-clean and re-observe a recleanable surface where contamination
   was seen, and escalate everything else to an instrumented method.
7. Report the detectable size, the coverage, the disposition and the
   findings raised.

## Pitfalls

- Recording a pass from an inspection that cannot resolve the size the
  requirement is written at. The observation is true and irrelevant,
  and the requirement stays unverified.
- Turning up the lamp to compensate for a long viewing distance.
  Distance enters the geometry and illuminance only the derating, so
  brightness cannot recover a detectable size the standoff has lost.
- Measuring ultraviolet irradiance at the lamp rather than at the
  surface. The inverse-square fall-off over a working standoff is the
  whole difference between a valid observation and a dark one.
- Starting a black-light observation straight out of a lit bay. The
  first minutes report the observer's adaptation state, not the
  surface.
- Reporting an observation without the fraction of surface it covered.
  A spot look and a full sweep enter the record identically and are not
  the same evidence.
- Treating fluorescence as a quantity. It shows that something is
  present and where; how much is there is a question only a measurement
  answers.

## Behavior contract (gate 3)

The resolvable-size geometry, illuminance and viewing-angle deratings,
ultraviolet band, irradiance and dark-adaptation conditions, coverage
fraction, substantiation comparison and disposition grading are
exercised by the gate 3 contract test:
scripts/test_q7001_verification_by_inspection.py against
scripts/q7001_verification_by_inspection_logic.py (stdlib unittest,
offline). Run:
python3 scripts/test_q7001_verification_by_inspection.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 →